2025-10-30 07:29 | -- (permalink)
The IETF 125 network connects to the Internet with 2x10Gb/s donated by China Mobile and 2x1GB/s donated by China Unicom for Transit.
The IETF uses the following network prefixes:
The IETF NOC supplies connectivity for the conference space and the venue hotel.
Notice for IETF 125
The IETF agreed prior to booking to issue random network access credentials (RADIUS accounts) to onsite participants. Just prior to the meeting, we were told that Chinese law now requires that credentials be linked to individuals and that the IETF must also provide RADIUS accounting logs, including account name, IP address, the last 24 bits of the device MAC address, RADIUS accounting message types (start session, stop session, and interim-update), and timestamps.
After the meeting, the IETF must provide the network operators (China Mobile and China Unicom) with a list mapping participant names to the usernames of the credentials issued to them. The operators are required to retain this information for six months and then destroy it.
Each registrant may be issued up to two sets of RADIUS credentials.
If credentials are lost, replacements may be issued only after the original credentials have been deactivated.
The IETF is required to investigate situations where a single set of credentials is simultaneously used by more than five MAC addresses to ensure the credentials have not been shared or compromised.
Chinese participants are required to follow local laws that require real identity registration before using the network.
Due to regulatory requirements, we are unable to use our donated Cisco Wireless hardware. For 125, we are using wireless hardware donated by Huawei and have members from China Mobile as part of our NOC team.
WiFi (802.11 a/g/n/ac/ax/), on the SSID ietf-125, is provided throughout the Meetings Room on 5GHz, with IPv4 and IPv6.
The network is encrypted and provides layer 2 security via WPA2 Enterprise with 802.1X (PEAP or TTLS) authentication and AES encryption. Use your registration number for the username and password; each user gets unique session encryption keys. The certificate for services.meeting.ietf.org is signed by Lets Encrypt, with the following fingerprint.
| SHA1 | CC 69 FF 45 E5 03 D1 38 FB 7B 34 CC 4E 21 A7 42 B9 A0 F3 7D |
| SHA256 | 26 FC 47 7C 62 71 E0 97 13 CD 51 25 A0 C9 EF 9B 74 39 1A F5 4F 4D 8B 19 AF E9 EE B8 8B EC 87 B6 |
Users should choose the 'ietf-125' SSID:
User: Registration Code Pass: Registration Code
Here are the relevant settings for connecting Android devices to the secure ietf networks.
We have found that on some devices, entering your confirmation number in the Anonymous identity field can resolve connection issues.
Here’s a quick summary of the available WiFi network:
| SSID | Description | Frequencies | IP Versions | WPA |
|---|---|---|---|---|
| ietf-125 | Dual-stack provides both globally routable IPv4 and IPv6 addresses | 5Ghz only | v4 - v6 | WPA2 Enterprise |
The IETF network covers the guest rooms and the public spaces throughout the Shangri-La using the 'ietf-hotel-125' and you must use your Registration Number for User Name and Password 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-125' SSID, you can contact our Help Desk or email support@ietf.org, and we will be happy to assist you.
The Shared Workspace is located in The Chairman Room. The Shared Workspace is open 8:00-19:00 beginning Sunday at 16:00 and ending on Friday, at 15:00. The room consists of table seats, wired access, and 220V power ports.
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.
IT support is being provided next to the Registration Desk and will be staffed during the following hours:
| Day | Hours |
|---|---|
| Monday | 8:30 - 17:00 |
| Tuesday | 8:30 - 17:00 |
| Wednesday | 8:30 - 17:00 |
| Thursday | 8:30 - 17:00 |
| Friday | 8:30 - 13:00 |
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:
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:
The following network services are provided:
| Service | Address | Notes |
|---|---|---|
| DNS | 31.130.228.6 31.130.228.7 | Validating recursive resolvers. The local domain is meeting.ietf.org. |
On the 'ietf-125' SSID, these services are provided by the following servers:
| Name | IPv4 | IPv6 |
|---|---|---|
| services-3.meeting.ietf.org | 31.130.228.6 | 2001:67c:1230:85::6 |
| services-4.meeting.ietf.org | 31.130.228.7 | 2001:67c:1230:85::7 |
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 on the IETF network need to be approved by the IETF Chair.
For IETF 125, no network experiments were requested.
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!
Volunteers:
Staff:
Connectivity: