2024-03-12 14:46 | -- (permalink)
The IETF 119 network connects to the Internet using one 10Gb/s donated by AARNet and two 10Gb/s uplinks donated by Aussie Broadband. The IETF uses the following network prefixes:
The IETF NOC supplies connectivity for the conference space and Aussie Broadband provided Dark fiber to the Rydges and Novotel venue hotels allowing us to extend the network to both hotel for this meeting.
WiFi (802.11 a/g/n/ac/ax) is provided throughout the venue on 2.4 and 5GHz bands with IPv4 and IPv6.
At IETF 118 the IETF meeting WiFi was 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). This remains for IETF 119.
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 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.
Aussie Broadband installed new fiber to the BCEC the Rydges and Novotel hotels. Because of this work, for this meeting we are able to extend our network in both hotels. The IETF network covers the guest rooms and the public spaces throughout the hotels using the 'ietf-hotel' SSID. If you have performance issues, 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.
IT support is being provided next to the Registration Desk and will be staffed during the following hours:
| Day | Hours |
|---|---|
| Sunday | 16:00 - 17: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 |
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:
Use this link to pre populate an email to the NOC. Submit a request
We publish a csv file containing the BSSID of our access points, if you want to be able to report the name of the AP you're connected to.
https://files.meeting.ietf.org/annotations/ap7000-annotations.csv
This csv format can be consumed natively as "Annotations" by popular Mac applications such as WiFi Signal (a menubar status widget) and WiFi Explorer (a wi-fi scanner).
Suggested configuration for WiFi Signal: under Status:
Display Pattern Line 1: **%N** %TMbps **%A**
Display Pattern Line 2: Ch%C@%W %I
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 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 |
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 119, no network experiments were requested.
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:
Connectivity:
Volunteers:
Staff: