2022-03-17 16:45 | -- (permalink)

IETF 113 Network Information – Vienna, Austria

External Connectivity

The IETF 113 network connects to the Internet via 10Gb/s uplinks donated by Next Layer Communications. The IETF uses 2001:67c:370::/48 and 2001:67c:1230::/46 for IPv6 and 31.133.128.0/18 and 31.130.224.0/20 for IPv4. We supply bandwidth for the conference space and venue hotel guest rooms.

Guest Room and Public Space WiFi

The IETF network covers the guest rooms and public spaces throughout the venue hotel using the 'ietf-hotel' SSID. If you have performance issues with this network, please let us know.

While we are using the IETF meeting network for Internet connectivity, we are using the hotel's access points to cover the guest rooms and public spaces, so there are limits to the improvements we can make.

If you have trouble with the 'ietf-hotel' SSID, please contact the Network Help Desk or send email to support @ ietf.org and we are glad to help!

Meeting Room Wireless

WiFi (802.11 a/g/n/ac) is provided throughout the venue on 2.4 and 5 GHz bands with IPv4 and IPv6.

Most users should choose the 'ietf' SSID:

Here’s a quick summary of the available WiFi networks:

*Unfortunately due to certificate issues eduroam is not available for 113.

All networks marked as encrypted provide layer 2 security. They use WPA2 Enterprise with 802.1X (PEAP or TTLS) authentication and AES encryption. Although all users are using the same credentials (user 'ietf', password 'ietf'), each user gets unique session encryption keys. The certificate for services.meeting.ietf.org is signed by Starfield Technologies, Inc., with the following fingerprint.

The WiFi network implements two BCP38-like filters:

• Packets from manually configured IPv4 addresses that are not assigned by DHCP are dropped. DHCP packets are snooped by our wireless LAN controllers to perform this filtering.
• Packets from IPv4 and IPv6 addresses that cannot be resolved via ARP/NS are filtered out. Proxy ARP/ND is performed by our wireless LAN controllers for this filtering.

A Note For Android Users

Here are the relevant settings for connecting Android devices to the secure ietf networks.

• Network name (e.g. ietf): ietf
• Security: WPA/WPA2-Enterprise
• EAP Method: PEAP
• Phase 2 authentication: MSCHAPv2
• CA Certificate: Use system certificates
• Do not verify
• Domain: services.meeting.ietf.org
• Identity: ietf
• Password: ietf

A Note For Windows Users

Connecting to the 'ietf' SSID on Windows 7 requires a few extra steps. If you're struggling to get connected to an encrypted SSID on your Windows laptop, please come by the Network Help Desk. Alternatively, you can try yourself; instructions are here

Network Help Desk

IT support is being provided next to the Registration Desk on the M1 level, and will be staffed the following hours:

Terminal Room

The Terminal Room is located in Park Suite 7. The Terminal Room is open 24 hours each day beginning Sunday, March 19th, 2022 at 16:00 and ending on Friday, 18th March, 2022 at 15:00. The room itself consists tables seats, providing some wired access and 230 V 50 Hz power ports with type C (Euro) and F (Schuko) connections.

The terminal room has no terminals, PCs, or other user-accessible machines. It is simply a place to get power, wired and wifi Internet access, and/or work quietly.

When using the Ethernet connections in the Terminal Room, IPv4 addresses are provided by DHCP. Please use Stateless Auto-configuration for IPv6 (SLAAC). A DHCPv6 server or RDNSS will provide network information.

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

NOC and Ticketing

To communicate with the NOC staff. Send an email to support @ ietf.org with as much detail regarding your issue and configuration as possible.

Please provide the following information:

• MAC Address
• Current Location
• Device type and OS
• Description of the issue

This will expedite ticket processing. If you're on site and need direct network assistance (i.e - you have no network) please go to the Network Help Desk.

The Secretariat has a ticket system to report problems with the meetings. Please send mail to: support @ ietf.org to report a problem. The Secretariat is responsible for addressing issues with:

• A/V in meeting rooms
• Beverage and food
• Jabber
• Projectors
• Room temperature (too hot/cold)

Printing

There is a printer at the Network Help Desk and is available to all IETF users. The printer is an Epson WF 3825 and is accessible via LPD, Bonjour, standard TCP/IP on port 9100. The hostname for it is ietf113-printer.meeting.ietf.org.

Instructions for MacOS using Bonjour auto-setup (DNS-Based Service Discovery)

(Note that this method is not available if you have configured an explicit DNS search list. Please see below for the manual configuration instructions.

1. Open System Preferences -> Printers & Scanners -> "+" below printer list
2. Select the "Printer" icon at the top of window
3. You should see the printers discovered by Bonjour. Pick the right one.
4. Enjoy hassle-free printing.

Instructions for MacOS using manual configuration

1. Open System Preferences -> Printers & Scanners -> "+" below printer list
2. Select the "Globe" icon at the top of window
3. Enter "ietf113-printer.meeting.ietf.org" in the Address field.
4. Select "Airprint" from the Protocol field drop down menu
5. Leave the Queue field blank.
6. Click Add

Instructions for Windows

1. Download and install the appropriate driver from: https://epson.com/Support/Printers/All-In-Ones/WorkForce-Series/Epson-WorkForce-Pro-WF-3820/s/SPT_C11CJ07201
2. If you have difficulty installing the printer for ietf113 please visit the Network Help Desk adjacent to the IETF Registration Desk on the Lobby Level.

EPSON Connect

1. Email the document or file you wish to print as an attachment to ietf113@print.epsonconnect.com
2. Retrieve your printout from the printer located near the Network Help Desk located in the Registration Area.

Services

The following network services are provided:

These services are being provided from both of the following servers:

Geolocation

There is a geolocation feed published here: https://noc.ietf.org/geo/google.csv

Geolocation service for event networks is hit or miss. Suggestions/assistance is welcomed. You can also try searching via https://www.google.com/ncr (no country re-direct).

Experiments

Experiments on the IETF network need to be approved by the IETF Chair. For IETF 113, the whole meeting is an experiment, with no network experiments requested:

Thanks

The terminal room and IETF network are made possible by contributions from our sponsors and the efforts of our volunteer team. If you see them in the halls, be sure to thank them for their work!

Contributors:

• Juniper Networks
• Cisco
• Open Systems Consultants

Connectivity:

• Next Layer

Volunteers:

• Hirochika Asai (Preferred Networks/WIDE)
• Rob Austein (Arrcus)
• Joe Clarke (Cisco)
• Hans Kuhn (NSRC)
• Warren Kumari (Google)
• Lucy Lynch
• Bill Fenner (Arista)
• Bill Jensen (University of Wisconsin–Madison)
• Karen O'Donoghue (ISOC)
• Clemens Schrimpe

Staff:

• Con Reilly
• Nick Kukich
• Rick Alfvin
• Sean Croghan
• Stetson Alfvin