IETF Meeting Network Information

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 (eduroam uses 802.1X). 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].

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:

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.

By default, Windows clients on the ietf SSID will get an RFC1918 IPv4 address and a global unicast IPv6 address.

However, recently Microsoft has enabled support for RFC8925 and Customer-side Address Translation (CLAT) to provide an "IPv6 Mostly" experience. If you wish to enable this, see the following. This is not required to have working network connectivity on the ietf SSID.

Prerequisites - Windows 11 update 25H2 build 26200.9550 (minimum), Windows 11 26H2 (preferred)

CLAT operation is enabled with the netsh command. In a command.exe or Powershell window. Run the following command:

netsh.exe interface clat set global permit=enabled

This command returns no out, but the change can be confirmed with:

netsh.exe interface clat show global

C:\Users\IETF01>netsh.exe interface clat show global
permit                 : enabled
pref64fromdns          : enabled
pref64fromra           : enabled
autoenable             : enabled
store                  : active

If pref64fromra output shows as disabled, you should enable it with:

netsh.exe interface clat set global pref64fromra=enabled

Reboot your machine and confirm CLAT is functioning. You should see an IPv4 address of 192.0.0.1 and a valid IPv6 address. If you need to disable CLAT, you can execute the following command, and then reboot:

netsh.exe interface clat set global permit=disabled

Linux can't connect to SSID ietf Wi-Fi 7 is enabled in San Francisco. Like at IETF 126, Linux clients may have issues connecting to the ietf SSID.

Description: Linux laptops with Wi-Fi 7 capable wlan cards cannot join ietf (Wi-Fi 7 enabled SSIDs). This issue was caused by the NetworkManager package not being able to appropriately handle the key management type of SAE-EXT-KEY.

Workaround: Linux users with a wpa_supplicant version 2.11 or greater can use the following command to stop NetworkManager, and configure and directly use wpa-supplicant with a suitable wpa.conf instead;

sudo systemctl stop NetworkManager

cat <<EOF > wpa-ietf.conf
network={
    ssid="ietf"
    key_mgmt=SAE-EXT-KEY FT-SAE-EXT-KEY
    sae_password="ietfietf"
    ieee80211w=2
}
EOF
sudo wpa_supplicant -i <wlan interface num> -c wpa-ietf.conf -d

To connect to the ietf-hotel, personal hot-spots or other wifi networks, users will need to cancel the above wpa_supplicant command and restart the NetworkManager service ;

sudo systemctl restart NetworkManager

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.

Guest rooms and public space Wi-Fi

The IETF NOC team works with IETF meeting hotels to provide guest room access to the IETF meeting network using the hotels' existing Wi-Fi networks. Onsite meeting participants can connect to this by choosing:

SSID: ietf-hotel
Password: ietfietf

It's important to note that 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 [email protected].

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 [email protected] 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:

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.

Statistics

Dashboards are available for overall traffic statistics and WiFi client counts throughout the meeting week.

Dashboard

Thanks to IETF 127 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!

• Bill Jensen (University of Wisconsin–Madison)
• Clemens Schrimpe
• Hans Kuhn (NSRC)
• Hirochika Asai (Preferred Networks/WIDE)
• Joe Clarke (Cisco)
• Karen O'Donoghue (Meinberg)
• Rob Austein (Arrcus)
• Steve Walsh

Staff

• Con Reilly
• Daniel Branik
• Thomas Eichinger
• Nick Kukich

Connectivity sponsors for IETF 127

• Comcast
• SFMIX
• Hurricane Electric
• CoreSite

Contributors

• Juniper Networks
• Cisco