IETF 120 - Vancouver, BC, Canada

2024-05-15 10:29 | -- (permalink)

DRAFT (Remove before flight)

External Connectivity

The IETF 120 network connects to the Internet using one 10Gb/s donated by ProviderA and two 10Gb/s uplinks donated by ProviderB. The IETF uses the following network prefixes:

  • 2001:67c:370::/48
  • 2001:67c:1230::/46
  • 31.133.128.0/18
  • 31.130.224.0/20

The IETF NOC supplies connectivity for the conference space and the venue hotel.

Guest Room and Public Space WiFi

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

It's important to note that while the IETF meeting network provides internet connectivity, guest rooms and public spaces are covered by the hotel's access points. As such, there may be limitations to the extent of improvements we can make. If you experience any issues with the 'ietf-hotel' SSID, you can contact our Help Desk or email support @ ietf.org, and we will be happy to assist you.

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

Meeting Room Wireless at the Venue Hotel

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

New for IETF 120 the IETF meeting WiFi has moved from WPA2-Enterprise with RADIUS (802.1x) to WPA3 PSK with a fallback to WPA2. While we'd like to be able to only do WPA3, we've discovered that many devices don't yet support it, so we currently are using Transition mode (fallback to WPA2).

Most users should choose the 'ietf' SSID:

password: ietfietf

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

SSID Description Frequencies IP Versions
ietf The default network 5Ghz only v4 and v6
ietf-legacy120 For legacy and unencrypted use 2.4 and 5Ghz v4 and v6
ietf-v6ONLY IPv6 only 5Ghz only v6 only
ietf-nat64 IPv6 stack with NAT64 to access IPv4 resources 5Ghz only v6 with NAT64 & DNS64
ietf-nat64-unencrypted IPv6 stack with NAT64 to access IPv4 resources 2.4 and 5Ghz v6 with NAT64 & DNS64
eduroam Educational users 2.4 and 5Ghz v4 and v6

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/ND are filtered out. Proxy ARP/ND is performed by our wireless LAN controllers for this filtering.

Terminal Room

The Terminal Room is located in P4. The Terminal Room is open 8:30-19:00 beginning Sunday, March 17, 2023, at 16:00 and ending on Friday, March 22, 2023, at 15:00. The room consists of table seats, wired access, and 220V power ports.

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 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.

Help Desk

IT support is being provided next to the Registration Desk and will be staffed during the following hours:

Day Hours
Sunday 16:00 - 19:00
Monday 8:30 - 17:00
Tuesday 8:30 - 17:00
Wednesday 8:30 - 17:00
Thursday 8:30 - 17:00
Friday 8:30 - 15:00

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 operating system
  • Description of the issue

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

The Secretariat has a ticket system to report problems with the meetings. Please send mail to: support @ ietf.org to request help. The Secretariat is responsible for helping with the following:

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

Services

The following network services are provided:

Service Address Notes
NTP ntp.meeting.ietf.org A stratum 2 time service is provided via unicast IPv4 and IPv6
DNS ns1.meeting.ietf.org ns2.meeting.ietf.org Validating recursive resolvers. The local domain is meeting.ietf.org.

These services are provided by the following servers:

Name IPv4 IPv6
services-1.meeting.ietf.org 31.130.229.6 2001:67c:370:229::6
services-2.meeting.ietf.org 31.130.229.7 2001:67c:370:229::7

Geolocation

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

Geolocation service for event networks is often incorrect. Suggestions and assistance are 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 120, no network experiments were requested.

Thanks

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

Contributors:

  • Juniper Networks
  • Cisco

Connectivity:

  • ProviderA
  • ProviderB

Volunteers:

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

Staff:

  • Sean Croghan
  • Nick Kukich
  • Con Reilly