2024-05-15 10:29 | -- (permalink)
The IETF 121 network connects to the Internet using one 10Gb/s donated by Eir to INEX for transit and peering with Hurricane Electric, Eir, and Zayo. The TraveLodge is connected to the CCD 1Gbs Metro Ethernet connection provided by Eir. The IETF uses the following network prefixes:
The IETF NOC supplies connectivity for the conference space and the venue hotel.
The IETF network covers the guest rooms and the public spaces throughout the Travelodge 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.
WiFi (802.11 a/g/n/ac/ax) is provided throughout the CCD on 2.4 and 5GHz bands with IPv4 and IPv6.
The IETF meeting WiFi is 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-nat64 | IPv6 stack with NAT64 to access IPv4 resources | 5Ghz only | v6 with NAT64 & DNS64 |
| eduroam | Educational users | 2.4 and 5Ghz | v4 and v6 |
The WiFi network implements two BCP38-like filters:
The Shared Workspace is located in Liffey Meeting Room 1. 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 |
|---|---|
| Sunday | 16:00 - 17:30 |
| 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 |
|---|---|---|
| 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. |
On the 'ietf' 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 |
On the 'ietf-nat64' SSID, these services are provided by the following servers:
| Name | IPv6 |
|---|---|
| services-1.meeting.ietf.org | 2001:67c:370:229::9 |
| services-2.meeting.ietf.org | 2001:67c:370:229::10 |
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 approval from the IETF Chair. No network experiments were requested for IETF 121.
The NOC team is conducting an internal experiment with a NAT (Network Address Translation) network. This NAT network provides the same dual-stack configuration as the main IETF network, with IPv6 configured identically to the main network, and IPv4 addresses provided by DHCP and routed through NAT. The IP block for this network is 10.56.0.0/16. Connect to the 'ietf-nat' SSID to use this network. If you have comments please let us know by emailing support@ietf.org.
This setup allows you to use a network similar to those found in most organizations, helping us assess differences in performance and connectivity when using NAT.
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:
Contributors:
Connectivity: