text conferencing at the 55th IETF meeting in Atlanta
Remote Access for the 55th IETF meeting in Atlanta: Text Conferencing At each IETF meeting, two of the working group meeting rooms are equipped for video multicast and remote participation. That is, for every IETF meeting slot, two of the working groups can see and hear the meeting. For the 55th IETF, in *addition* to the usual network A/V, text conferencing will be provided for every working group that meets. All of the conference rooms are hosted on conference.ietf.jabber.com and each is named using the official IETF abbreviation found in the agenda (e.g., "apparea", "dhc", "forces", and so on -- for all the examples that follow, we'll use "foobar" as the abbreviation). Each conference room also has a 'bot which records everything that gets sent: http://www.jabber.com/chatbot/logs/conference.ietf.jabber.com/foobar/ Enjoy! /mtr
Re: text conferencing at the 55th IETF meeting in Atlanta
Marshall Rose wrote: Each conference room also has a 'bot which records everything that gets sent: Very nice. Can these logs be included in the minutes, or alongside them? -- /===\ |John Stracke |[EMAIL PROTECTED] | |Principal Engineer|http://www.centivinc.com| |Centiv|My opinions are my own. | |===| |If you're going to walk on thin ice, you might as well *dance*!| \===/
WLAN at IETF55
We are seeing some of the usual problems with the wireless support at IETF55 in Atlanta. To help mitigate the problems: 1) Make sure you laptop is configured with SSID of IETF55 2) Do not allow your laptop to run in peer-to-peer mode. Set it to Access Point only mode. We are seeing many nodes running in peer-to-peer mode. It is essential that people not run in peer-to-peer mode. If you run in peer-to-peer mode (even unintentionally) it will disrupt other people and the overall wireless network operation. Many new OS's will fall back to peer-to-peer mode by default. Please make yours does not do this. See http://www.ietf55.ops.ietf.org/ietf55/NetworkTerminal for more detail on OS setup. Thanks, Bob (for the NOC team) p.s. Later today we will start confiscating the wireless cards of people running in peer-to-peer mode
Re: text conferencing at the 55th IETF meeting in Atlanta
In message <[EMAIL PROTECTED]>, Marsha
ll Rose writes:
>
>Each conference room also has a 'bot which records everything that gets
>sent:
>
>http://www.jabber.com/chatbot/logs/conference.ietf.jabber.com/foobar/
>
Will you keep those Web pages up for a while? Depending on what is
typed, they can be a useful supplement to the work of the scribe.
--Steve Bellovin, http://www.research.att.com/~smb (me)
http://www.wilyhacker.com ("Firewalls" book)
Re: text conferencing at the 55th IETF meeting in Atlanta
> In message <[EMAIL PROTECTED]>, > Marsha ll Rose writes: > > > > >Each conference room also has a 'bot which records everything that gets > >sent: > > > >http://www.jabber.com/chatbot/logs/conference.ietf.jabber.com/foobar/ > > > > Will you keep those Web pages up for a while? sure. > Depending on what is > typed, they can be a useful supplement to the work of the scribe. exactly! /mtr
Re: text conferencing at the 55th IETF meeting in Atlanta
> Marshall Rose wrote: > > >Each conference room also has a 'bot which records everything that gets > >sent: > > > > > Very nice. Can these logs be included in the minutes, or alongside them? that's up to the minute taker. remember that there isn't a moderator in the chatrooms, so it's not really a "record", per se. /mtr
ADHOC wireless users on ietf55 convention network (fix your darnconfigs folks)
the following mac addresses are configured for adhoc mode, fix your cards folks, you're messing it up for other people... MAC address ssidchannel 02022d433ebcwavelan network 3 02022d244ef1wavelan network 3 0205d1b561ccIETF55 11 02202102a966Home11 02233b4047b5IETF55 11 025026dc1d8bIETF55 11 0250c57e1d8bIETF55 11 360238012402IETF6 fa03ff024d03IETF6 -- -- Joel Jaeggli Academic User Services [EMAIL PROTECTED] --PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E -- In Dr. Johnson's famous dictionary patriotism is defined as the last resort of the scoundrel. With all due respect to an enlightened but inferior lexicographer I beg to submit that it is the first. -- Ambrose Bierce, "The Devil's Dictionary"
Re: text conferencing at the 55th IETF meeting in Atlanta
For those, who would like to use SIP for text conferencing, experimental operation of a SIP2Jabber gateway has been set up at iptel.org. See http://www.iptel.org/ietf55/ for guidelines how to join the IETF chat rooms. Better set your expectations low -- the gateway has not been tested with bigger user populations until now. -Jiri At 03:11 PM 11/18/2002, Marshall Rose wrote: > Remote Access for the 55th IETF meeting in Atlanta: > Text Conferencing > >At each IETF meeting, two of the working group meeting rooms are equipped >for video multicast and remote participation. That is, for every IETF >meeting slot, two of the working groups can see and hear the >meeting. For the 55th IETF, in *addition* to the usual network A/V, text >conferencing will be provided for every working group that meets. > >All of the conference rooms are hosted on > >conference.ietf.jabber.com > >and each is named using the official IETF abbreviation found in the >agenda (e.g., "apparea", "dhc", "forces", and so on -- for all the >examples that follow, we'll use "foobar" as the abbreviation). > >Each conference room also has a 'bot which records everything that gets >sent: > >http://www.jabber.com/chatbot/logs/conference.ietf.jabber.com/foobar/ > >Enjoy! > >/mtr -- Jiri Kuthanhttp://iptel.org/~jiri/
Re: text conferencing at the 55th IETF meeting in Atlanta
Marshall Rose wrote: Very nice. Can these logs be included in the minutes, or alongside them? that's up to the minute taker. remember that there isn't a moderator in the chatrooms, so it's not really a "record", per se. True; but it could still be a useful log, provided there's a scribe reporting what's going on in the room. It would be possible for the logs to be gathered up and included with the minutes, as a supplement; that wouldn't take extra effort from the minute takers. But maybe we should wait and see whether the logs are actually useful. (Personally, if I were going to the meeting, I'd volunteer to be both minute taker and scribe; then I'd take what I'd scribed to the chat room and turn it into minutes. No point having to find two volunteers.) -- /===\ |John Stracke |[EMAIL PROTECTED] | |Principal Engineer|http://www.centivinc.com| |Centiv|My opinions are my own. | |===| |If you're going to walk on thin ice, you might as well *dance*!| \===/
Re: text conferencing at the 55th IETF meeting in Atlanta
Can someone fix the X.509 certificate that is used to protect the TLS sessions with conference.ietf.jabber.org ? The hostname is wrong so verification fails.
port 80 of ipv6 on srv0.ietf55.ops.ietf.org
55th IETF network staffs, i have a trivial trouble about ipv6 accessing the page "Host Information" on 55th IETF web because IPv6 port 80 on www.ietf55.ops.ietf.org looks closed. i would be happy if you opened the port of IPv6 or removed record from the DNS. thank you. % telnet www.ietf55.ops.ietf.org 80 Trying 2001:240:5ff:1::2... telnet: connect to address 2001:240:5ff:1::2: Connection refused
IETF PGP Key Signing Party at IETF 55 Atlanta
Once again, we will be holding a PGP Key signing party at the IETF meeting in Atlanta. We have been scheduled to meet at 10:30pm on the evening of Wednesday, November 20, 2002. (Note that if the IAB Open Plenary runs over, we will start approximately 5 minutes *after* the IAB Open Plenary finishes.) The procedure we will use is the following: o People who wish to participate should email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, November 20, 2002. Please include a subject line of "IETF PGP KEY", and please avoid MIME-encrypting your e-mail. (I will be running the entire mail folder file through PGP, and PGP-keys that are base-64 encoded will get ignored unless I take manual action to fix things. I will try do the manual fixup, but I make no guarantees about catching all of them.) The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc(gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 9pm on Wednesday, you will be able to fetch complete key ring from the following URL with all of the keys that were submitted: http://web.mit.edu/tytso/www/ietf.pgp o At 10:30pm, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Submit the keys you have signed to the PGP keyservers. A good one to use is the one at MIT: simply send mail containing the ascii armored version of your PGP public key to <[EMAIL PROTECTED]>. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and then take the handout home and sign the keys later. - Ted
Re: text conferencing at the 55th IETF meeting in Atlanta
I have tried both JabberFox and TVJab on MacOSX and can just not get it to work. JabberFox just dies, and can not even connect to my jabber server for some weird reason. TVJab works fine with the jabber server I connect to (psg.com) including conferencing there, but I can not manage to connect to conference rooms organized for this meeting (i.e. I can only choose things at psg.com, not jabber.org). Other jabber clients for MacOSX (Fire!, Proteus) seem to not handle conferences. Anyone succeeded that can come close to my laptop during the meeting and try to see what's up? paf
Re: IETF#55-Atlanta - social event
> Sounds like we need a party to happen, eh? The question is what night,
> and
> where.
>
> S
Apparently there is a party scheduled for the garden terrace wednesday
night. I can provide music for the occasion, if necessary.
Scott
>
> >
> > Based upon the agenda, and lack of a button, it looks like there is
> > no social event. I don't have a problem with this at all, actually,
> > I just wanted to verify my belief.
> > (Does that mean there is no T-shirt? I depend upon conference T-shirts
> > to keep give me an excuse never to venture into a mall...)
> >
> > ] ON HUMILITY: to err is human. To moo, bovine. |
> > firewalls [
> > ] Michael Richardson, Sandelman Software Works, Ottawa, ON|net
> > architect[
> > ] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device
> > driver[
> > ] panic("Just another Debian GNU/Linux using, kernel hacking, security
> > guy"); [
> >
> >
> >
> >
> >
> >
>
> --
> Revolt now.
>
> +++ GMX - Mail, Messaging & more http://www.gmx.net +++
> NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
>
--
Revolt now.
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
Re: text conferencing at the 55th IETF meeting in Atlanta
Admittedly the Jabber clients for MacOS are sub-optimal. Hopefully that situation will be remedied in time for San Francisco. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Mon, 18 Nov 2002, Patrik Fältström wrote: > I have tried both JabberFox and TVJab on MacOSX and can just not get it > to work. > > JabberFox just dies, and can not even connect to my jabber server for > some weird reason. > > TVJab works fine with the jabber server I connect to (psg.com) > including conferencing there, but I can not manage to connect to > conference rooms organized for this meeting (i.e. I can only choose > things at psg.com, not jabber.org). > > Other jabber clients for MacOSX (Fire!, Proteus) seem to not handle > conferences. > > Anyone succeeded that can come close to my laptop during the meeting > and try to see what's up? > > paf >
