Hi, I will like to ask the responsible/s of setting up the IETF network to make sure that we don't have again, a situation like we had this week, when the network was not working most of the time, and no IPv6 available. There was already some problems in the last IETF, and it seems to me that the reason may be the APs, as by chance, it seems to me that are the same, and that never had been used in previous IETFs. Of course, I may be wrong, but seems an interesting coincidence, and if that's the case, we should never use them. This week has been really painful in terms of network, spending extra time, and even some times being forced to "escape" from some meetings, because this situation of general malfunction of the network. Is also not acceptable, in my opinion, not being able to support IPv6, when today, we know, from experience of past IETFs, that it has never seen a problem. Again, the coincidence with the previous event and the same APs ? This doesn't facilitate our work, dismisses our attention and in general make IETF much less productive than it should be. Thanks for making sure that this will NEVER happen again, please. Regards, Jordi > De: Jim Martin <jim@xxxxxxxxxxxx> > Responder a: <ietf-bounces@xxxxxxxx> > Fecha: Mon, 7 Mar 2005 09:25:35 -0600 > Para: "ietf@xxxxxxxx" <ietf@xxxxxxxx> > Asunto: IETF62 Network and Terminal Room Information > > Network and Terminal Room Information > IETF 62 – Minneapolis, MN > > Terminal Room > ---------------------- > The Terminal Room is located in Marquette and Hennepin on the second > floor of the Minneapolis Hilton and is open 24 hours a day beginning at > 4pm on Sunday March 6th and ending at 12 noon on Friday March 11th. A > help desk is being provided and will be manned from 8:00 AM to 8:00 PM > every day. The room itself consists of approximately 120 seats > providing wired 10/100/1000 Ethernet access and 110v North American > power ports. There are also two duplex printers available. Please note > that this terminal room has, in fact, no terminals, PCs or other > user-accessible machines. It is simply a place to get power and wired > Internet access. > > When using the Ethernet connections in the Terminal Room, IPv4 > addressing is provided via DHCP. Please use Dynamic Autoconfiguration > for IPv6. Unlike the wireless networks, IP multicast is enabled for the > terminal room network. > > Network Basics > --------------------- > The IETF 62 network connects to the Internet via a metropolitan gigabit > Ethernet link with a backup 54-megabit wireless link. The entire event > is addressed out of the 130.129.0.0/16 block for IPv4 and > 2001:468:19ff::/48 for IPv6. IPv4 multicast and IPv6 are being provided > from Abilene/I2. > > Wireless > ------------ > An 802.11 a/b/g wireless network is being provided liberally in the > Minneapolis Hilton. The areas being specifically covered are the > meeting rooms and hallways in the conference area, the executive > lounge, the lobby, and the bar area. > > To use this network, associate with the beaconed SSID of “ietf62”. IPv4 > addressing is provided via DHCP. For IPv6 and IPv4 combined services, > associate with the open but un-beaconed SSID “ietf62-ipv6” . IPv6 > clients should use Dynamic Autoconfiguration. Due to bandwidth concerns > IP multicast is not available on this network. > > For those interested in a bit more link-layer security, a 128-bit WEP > enabled SSID is available. It must be manually configured, as there is > no beacon for this network, The SSID is “ietf62-wep” and the WEP key is > “wepisinsecure” (Hex: 7765706973696e736563757265) > > For substantially better link-layer security, we are providing dynamic > WEP keying using 802.1X. It also must be manually configured because > there is no beacon. Note that is dynamic WEP, not TKIP or WPA. > > To use 802.1X: > 1. Associate to SSID: ietf62-dot1x > 2. Use PEAP/MSCHAPv2, TTLS/PAP, TTLS/CHAP, TLS > 3. Do Not Verify Server Cert and we won’t verify yours :) > 4. UserName and/or Realm can be anything, as well as outer tunnel > identity for TTLS. > ex. joeblow@xxxxxxxxxxx > 5. Password must be “ietf62” > > The proper operation of the wireless network requires the assistance of > all users. One of the most significant issues with wireless > performance in past IETF meetings has been wireless clients > automatically, or accidentally initiating "ad-hoc" networks that act as > the official IETF wireless network, causing other users to associate > with false IETF wireless networks. Therefore, please disable your > client's ability to create an ad-hoc network and as well as the ability > to automatically join an ad-hoc network. If you are using Windows XP > or Mac OS X 10.3 to manage your wireless client, the instructions to > disable creation of ad-hoc networks are listed below. If you are using > other systems, please do what ever your particular wireless client > management system requires to turn off ad-hoc networks. > > > > Instructions for Mac OS X > ---------------------------------- > Open System Preferences -> Network -> Airport and un-check the box > for "Allow this computer to create networks". > > Instructions for Windows XP > ------------------------------------- > Open Properties -> wireless networks -> advanced and then select > "access point (infrastructure) networks only" and unselect > "automatically connect to non-preferred networks". > > Printing > ---------- > Two printers are located in the Terminal Room and are available to all > IETF users. The printers themselves are HP LaserJet 4200Ns which are > Postscript capable and have the duplex option installed. The printers > are accessible via IPP, LPD, and Windows Printing (via samba). > 〈 IPP - URI ipp://lpd.ietf62.ietf.org/printer > 〈 cups - browsing enabled and should be discovered automatically > 〈 Mac - under Printer Setup Utility use "IETF_62_Terminal_Room" under > shared printers > 〈 Windows users - In an IE window type in > ‘\\lpd\terminal_room_printers” A warning/error message may pop-up > saying the server does not have the correct printer driver installed, > just hit OK. Next an Add Printer Wizard dialogue box will appear, you > need to select two things: In the left window (Manufacturer) select > 'HP'. Then in the right hand window (Printers), scroll down and select > 'HP LaserJet 4200N', then hit 'Ok'. > o You may see the status of the printer say something like 'Access > denied, unable to connect' just ignore this, it should work fine. > o You may need to disable your VPN connection(s). > > Services > ------------ > The following network services are provided: > SMTP – {smtpp,smtp1,smtp2}.ietf62.ietf.org > SMTP relay services are provided for users on the IETF network. > NTP - ntp.ietf62.ietf.org > Stratum 2 time service is provided via IPv4 unicast. > Local IETF Website mirror – www.ietf.org > We have a local complete mirror of the IETF site. If you resolve > www.ietf.org using the onsite DNS servers, you will be directed to the > local mirrors. > > These services are being provided from both of the following servers: > 130.129.16.12 (IPv4) or 2001:468:19ff:16:230:1bff:fead:4e40 (IPv6) > 130.129.16.13 (IPv4) or 2001:468:19ff:16:260:97ff:fed1:a86c (IPv6) > > Additionally, full recursive DNS service is being provided from > 130.129.16.18 and 130.129.16.20. Our domain name is ietf62.ietf.org. > > Thanks > ---------- > The terminal room and IETF network are made possible by the generous > contributions by a number of companies and by the tireless efforts of > our volunteer team. If you see any of these people in the halls, please > be sure to thank them for all their work! > > Contributors: > Alcatel, Airespace, Cisco Systems, Juniper Systems, Onvoy, University > of Minnesota, Infoblox > > Volunteers: > Jim Martin, Karen O'Donoghue, Bill Jensen, David Farmer, Dan Westacott, > Chris Stradtman, Rob Nagy, > Geoff Horne, Ben Kochie, Terry Slattery, Jesse Lindeman, Terry Yackel, > George Perakis, Francois Bourdais, > Rafael Rizo, Dennis Fazio, Chris Liljenstolpe, Jerry Wilson, Dave > Ahlstrand, Frank Di Gravina, Steve Fletty > > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf