[87all] IETF87 Network Information

[Jim Martin <[e-mail]>]

IETF 87 Network Information - Berlin, Germany
---------------------------------------------

Terminal Room
-------------

The Terminal Room is located in Kopenick I/II and is open 24 hours a day beginning Sunday, 28 July, 2013 at 16:00 and ending on Friday, 02 August, 2013 at 15:00. A help desk is being provided, hours are listed below.  The room itself consists of approximately 100 seats providing some wired access and 220v EU power ports. There is also an HP Officejet Pro 8600 (HP994A15) printer 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, wired Internet access, help desk support, or print documents.

When using the Ethernet connections in the Terminal Room, IPv4 addressing is provided via DHCP. Please use Dynamic Auto-configuration for IPv6. A stateless DHCPv6 server will provide network information.  To cut down on the mess, ethernet cables have not been installed to every seat in the Terminal Room. If you need a cable, please ask at the Help Desk.

Please note that at the request of the IETF Chair, demonstrations are no longer permitted in the Terminal Room.

Help Desk
---------
A help desk is being provided and will be manned the following hours: 

 Sunday        || 16:00 to 19:00
 Monday        ||  8:00 to 20:00
 Tuesday       ||  8:00 to 18:00
 Wednesday     ||  8:00 to 20:00
 Thursday      ||  8:00 to 20:00
 Friday        ||  8:00 to 15:00

NOC and Ticketing
-----------------
There are several ways to communicate with the NOC staff. 
1. Submit a new trouble ticket via the trac web interface at http://tickets.meeting.ietf.org/newticket . Filling in the following fields: "My MAC Address", "My Current Location", and "My OS" may expedite ticket processing. If you have an existing account on http://tools.ietf.org you can use your established credentials (email address and tools password) log in.
2. Send an email to tickets @ meeting.ietf.org with as much detail regarding your issue and configuration as possible. 
3. If you're on site and need direct network assistance (i.e - you have no network) please go to the helpdesk, which is located in the Terminal Room.
4. Use the Jabber room at noc @ jabber.ietf.org to report issues or communicate with the NOC. 

You can also use trac to review outstanding tickets before reporting an issue or to update outstanding tickets.

Network Basics
--------------

External Connectivity
---------------------
The IETF 87 network connects to the Internet via two 1Gb/s links, provided by Deutsche Telekom. The entire event is addressed out of the 130.129.0.0/16 block for IPv4 and 2001:df8::/32 for IPv6. IPv6 is native and is supported. We are supplying bandwidth for the conference space, public spaces, in-room wireless and wired connections at the Intercontinental.
       
Meeting Room Wireless
---------------------

An 802.11 a/b/g/n wireless network is being provided liberally throughout the venue.  802.11n is available on the 5Ghz frequencies. 

To use the meeting room wireless network, associate with the beaconed SSID of "ietf" for 802.11a/b/g/n and "ietf-a" for 802.11a/n.  IPv4 addressing is provided via DHCP.  IPv6 clients should use Dynamic Auto-configuration, and may use DHCPv6 to retrieve name server information. 

For those interested in more link-layer security, WPA SSIDs with 802.1X is available.  The SSIDs are "ietf.1x" and "ietf-a.1x". Do not use WPA-PSK as that will not work.  Also, using TLS as an eap method is not advisable, please prefer TTLS or PEAP.

To use 802.1X:
 1. Associate to SSID: ietf.1x OR ietf-a.1x
 2. Use PEAP/MSCHAPv2
 3. Do Not Verify Server Cert and we won't verify yours :)
 4. Username (case sensitive): ietf
 5. Password (case sensitive): ietf

If you have an eduroam account, we support authenticating via eduroam.  Simply select the "eduroam" SSID.  Use your eduroam credentials.

For a pure-IPv6 environment, use the ietf-v6ONLY ssid.

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. 
 
Public spaces like the lobby and the bar that are covered by the hotel's wireless infrastructure require using the SSID "InterContinental". Their access points are on the IETF IP network, but won't be broadcasting our SSIDs.

Intercontinental Guest Room Access
----------------------------------

The IETF Network is being extended to the guest rooms in the Intercontinental.  Guest room network access is available via wired and wireless (SSID "InterContinental").  Both IPv4 and IPv6 are deployed. 

Note that while we are using the IETF meeting network for Internet connectivity, we are using the Hotel's wireless infrastructure for the delivery to the guest rooms and lobby, so there are limits to the improvements we can effect.  We recommend using the wired connection whenever possible in your guest room.

Pullman Guest Room Access
-------------------------

In preparation for the IETF meeting, the Pullman Hotel has set up a special wireless SSID ("event") for attendees in the IETF block, credentials for which are being handed out to guests in the block upon check-in.  Unfortunately, early arriving IETF attendees found its performance has ranged from passable to completely unusable. By comparison, reports were that the wired network has been performing well.

The wired network and the Pullman's normal wireless net (SSIDs "m3connect" and "pullman") use device-specific credentials, separate from the shared credential for the "event" network.  If you need one of these, they are available to IETF block guests for free by asking the hotel's front desk.

Hence, if you are staying at the Pullman Hotel, you may wish to prepare to use the wired network in your hotel room.  Specifically, you may wish to bring with you an access point and/or a long ethernet cable with an RJ45 coupler.  Note that the ethernet cables provided by the Pullman (in at least some rooms) are both quite short and non-standard (pins 1 and 2 are swapped with 4 and 5), so neither straight cables nor standard crossover cables will work on their own. Accordingly, if bringing a long network cable, it may also be wise to bring an RJ45 coupler, using the provided cable to normalize pins and your cable to add length.

As a reminder, the IETF Network team deploys a network for the meeting space and endeavors to augment the guest room and public space Internet in the headquarters hotel.  Overflow hotels such as the Pullman are un-augmented, using the hotel's normal network infrastructure.

Printing
--------
There is a printer in the Terminal Room and is available to all IETF users. The printer is an HP Officejet Pro 8600 Plus and is accessible via LPD, Bonjour, and standard TCP/IP on port 9100.  The hostname for it is term-printer.meeting.ietf.org.  It is possible to print from email.  For the email address, see the physical label on the printer.

Drivers can be found on the NOC wiki at https://tickets.meeting.ietf.org/wiki/IETF87network

=== Instructions for Mac OS X using Bonjour auto-setup (DNS-Based Service Discovery) ===
 1. Open System Preferences -> Print & Fax -> "+" below printer list
 2. Choose "Default" in the top-menu.
 3. You should see the printers discovered by Bonjour. Pick the right one.
 4. Enjoy hassle-free printing.

=== Instructions for Mac OS X using manual configuration ===
 1. Open System Preferences -> Print & Fax -> "+" below printer list
 2. Select the "IP" icon at the top of window
 3. Select the "HP Jetdirect - Socket" from the drop down
 4. Enter "term-printer.meeting.ietf.org" in the Address field.  Leave the Queue field blank.
 5. ''Print Using'' should auto-populate
 6. Click Add

=== Instructions for Windows using Windows printing system (in Vista layout)   ===
 1. If you haven't printed on selected printer before, download and install the driver (do not use any of "wizard" or "automated" packages).
 2. Start -> Settings -> Printers & Faxes -> Add Printer -> Add Networked printer (and click Next) - some waiting time
 3a. If you are hooked to wired network in terminal room, you are able to add all printers and you are done
 3b. If you aren't hooked to wired network in terminal room, click STOP in searching printers
 4. Click "desired printer isn't in the list"
 5. "Add printer using TCP/IP address ..."
 6. Select "Type" as "TCP/IP device" and IP address of desired printer 
 7. Select printer driver (you may need to choose it from package you installed in step 1) - Do NOT click "Windows Update"
 8. Click next (two or three times - depends on your windows version and drivers installed) and wait until the printer is added

=== Instructions for Windows using HP printing framework ===
 1. Download HP Universal Print Driver for Windows from http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=4323647&lang=en&cc=us&taskId=135&prodSeriesId=4322915&prodTypeId=18972
 2. Select "Dynamic installation" and wait until all drivers are copied (takes about 5-10 minutes)
 3. Add printers by using their IP addresses in "control panel" appearing when select Start -> Settings -> Printers & faxes -> "HP Universal Printing PS" -> Properties

=== HP Eprint for Android devices
 1. Find the printer's email address on a label pasted to the printer.
 2. Email the document to that address.
 3. Retrieve your print out from the Terminal Room.

Services
--------

The following network services are provided:

 Service|| Address                                                     || Notes
 SMTP   || smtp.meeting.ietf.org                                       || Will provide SMTP relay for anything within the IETF network.
 NTP    || ntp.meeting.ietf.org                                        || A stratum 2 time service is provided via IPv4 and IPv6 unicast.
 DNS    || 130.129.5.6/2001:df8:0:5::6 and 130.129.5.7/2001:df8:0:5::7 || Validating recursive resolvers. The domain name is meeting.ietf.org.

These services are being provided from both of the following servers:
 130.129.5.6 (IPv4) or 2001:df8:0:5::6/64 (IPv6)
 130.129.5.7 (IPv4) or 2001:df8:0:5::7/64 (IPv6)

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:
 Juniper Networks
 Cisco

Connectivity:
 Telekom

Volunteers:
 Bill Jensen (in absentia)
 Bill Fenner (in absentia)
 Bjoern A. Zeeb
 Chris Elliott
 Jim Martin
 Joel Jaeggli
 Karen O'Donoghue
 Lucy Lynch
 Warren Kumari
 Samuel Weiler

Staff:
 Rick Alfvin
 James Dishongh
 Colin Doyle
 Nick Kukich
 Brandon Height
 Hans Kuhn