IETF Meeting Network Information
The dedicated IETF Network Operations Center (NOC) team works with meeting venues before and during each meeting and hackathon to engineer and deploy a network free and unfiltered Wi-Fi in every IETF meeting venue.
External connectivity
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.
Meeting room wireless
Wi-Fi (802.11 a/g/n/ac/ax) depending on the SSID is provided throughout the Meetings Room on 5GHz and 6GHz bands, with IPv4 and IPv6.
The IETF meeting Wi-Fi is WPA3 or WPA2 PSK. We have been using WPA3 with a fallback to WPA2 for meetings prior to 124. The SSID ietf is now WPA3 only. If your devices can not support WPA3 please use ietf-dual-stack that is WPA2 only.
The default network (SSID “ietf”) will allow your device to signal a preference for IPv6-only operation while still supporting IPv4 if needed via translation mechanisms by implementing the “IPv6-Only Preferred Option” [RFC 8925]. This builds on the trials during IETF 122 Bangkok, and IETF 121 Dublin and put in place and put in to production at IETF 123 in Madrid.
Most users should choose the ietf SSID:
password: ietfietf
If you are not able to connect to ietf, use 'ietf-dual-stack'
password: ietfietf
Here’s a quick summary of the available Wi-Fi networks:
| SSID | Description | Frequencies | IP Versions | WPA |
|---|---|---|---|---|
| ietf | IPv6-Only Preferred with Option for DHCPv4 [RFC 8925]| 5Ghz only | 5Ghz and 6Ghz | v6 - NAT64 - v4 | WPA3 |
| ietf-dual-stack | Dual-stack provides both globally routable IPv4 and IPv6 addresses | 5Ghz only | v6 - v4 | WPA2 |
| eduroam | Educational users | 2.4Ghz and 5Ghz | v6 - v4 | WPA2 |
The Wi-Fi 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.
Shared workspace wired
When using the Ethernet connections in the Shared Workspace, IPv4 addresses are provided by DHCP. Please use Stateless Auto-configuration for IPv6 (SLAAC). A DHCPv6 server or RDNSS will provide network information.
Help desk
If you are onsite and need direct network assistance (i.e., you have no network), please go to the Help Desk next to the IETF Registration Desk. NOC support is provided during hours onsite IETF registration is open.
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.
Services
The following network services are provided on the IETF meeting network:
On the ietf SSID, these services are provided by the following servers:
| Name | IPv6 | IPv4 |
|---|---|---|
| services-1.meeting.ietf.org | 2001:67c:370:229::9 | 31.130.229.6 |
| services-2.meeting.ietf.org | 2001:67c:370:229::10 | 31.130.229.7 |
On the ietf-dual-stack SSID, 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 |
| 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. |
Geolocation
The IETF NOC publishes a geolocation feed for the IETF meeting network.
Geolocation service for event networks is often incorrect. Suggestions and assistance are welcomed.
Experiments
Experiments on the IETF network need to be approved by the IETF Chair.
Thanks to IETF 125 Volunteers
The IETF network is made possible by our dedicated volunteer team, some of whom have the support of their employers. If you see any of these amazing volunteers in the halls, please be sure to thank them for their hard work and commitment!
- Clemens Schrimpe
- Cong Xiao (China Mobile)
- Hongxian Zhang (China Mobile)
- Wanquing Wang (Huawei)
- Yongdong (Michael) Zhou 周永东 (Huawei)
Staff
- Con Reilly
- Daniel Branik
- Joe Clarke
- Nick Kukich
- Sean Croghan
Connectivity sponsors for IETF 125
- China Mobile
- China Unicom
Contributors
- Juniper Networks
- Cisco