IETF 106 Network Information – Singapore, Singapore
Terminal Room
The Terminal Room is located in Ord and Blundell which is adjacent to the South Atrium on the 4th Level of the Raffles City Convention Center. The Terminal Room is open 24 hours each day beginning Sunday, November 17th, 2019 at 16:00 and ending on Friday, 22 November, 2019 at 15:00. The room itself consists of approximately 50 seats, providing some wired access and 220v power ports with type G (UK) connections.
Please note that this 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/or work quietly.
When using the Ethernet connections in the Terminal Room, IPv4 addressing is provided via 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.
Help Desk
A Help Desk is being provided next to the Registration Desk in the Raffles Convention Foyer, and will be staffed the following hours:
| Sunday | 16:00 to 19:00 |
| Monday | 8:00 to 17:00 |
| Tuesday | 8:00 to 17:00 |
| Wednesday | 8:00 to 17:00 |
| Thursday | 8:00 to 17:00 |
| Friday | 8:00 to 15:00 |
NOC and Ticketing
There are several ways to communicate with the NOC staff.
- Submit a new trouble ticket via the trac web interface. Filling in the following fields: "My MAC Address", "My Current Location", and "My OS" expedite ticket processing. If you have an existing account on https://tools.ietf.org you can use your established credentials (email address and tools password) to log in.
- Send an email to
tickets @ meeting.ietf.orgwith as much detail regarding your issue and configuration as possible. - If you're on site and need direct network assistance (i.e - you have no network) please go to the Help Desk, which is located in the Terminal Room.
You can also use trac to review outstanding tickets before reporting an issue or to update outstanding tickets.
The Secretariat also maintains a ticket system for the reporting of meeting issues. Please send
mail to: mtd @ietf.org to report a problem. The Secretariat is responsible for addressing issues with:
- A/V in meeting rooms
- Beverage and food
- Jabber
- Projectors
- Temperature fluctuation
External Connectivity
The IETF 106 network connects to the Internet via multiple 1Gb/s uplinks donated by Moratelindo and NTT Communications. The IETF uses 2001:67c:370::/48 and 2001:67c:1230::/46 for IPv6 and 31.133.128.0/18 and 31.130.224.0/20 for IPv4. We are supplying bandwidth for the conference space, as well as wireless connections in the guest rooms of the Swissotel and the Fairmont hotel.
Meeting Room Wireless
An 802.11 a/g/n/ac wireless network is provided throughout the venue on both the 2.4 and 5 GHz bands, in conjunction with IPv4 and IPv6 addressing options.
The main “ietf” wireless network is encrypted; make sure you enter ietf for both the username and password.
Here’s a quick summary of the network layout:
| SSID | Description | Encrypted | Frequencies | IP Versions |
| ietf | Our default network | yes | 5Ghz only | v4 and v6 |
| ietf-legacy106 | For legacy and unencrypted use | no | 2.4 and 5Ghz | v4 and v6 |
| ietf-2.4ONLY | An encrypted network for 2.4Ghz users | yes | 2.4Ghz only | v4 and v6 |
| ietf-v6ONLY | For users wanting pure IPv6 | yes | 5Ghz only | v6 only |
| ietf-nat64 | IPv6 stack with NAT64 to access IPv4 resources | yes | 5Ghz only | v6 with NAT64 & DNS64 |
| ietf-nat64-unencrypted | IPv6 stack with NAT64 to access IPv4 resources | no | 2.4 and 5Ghz | v6 with NAT64 & DNS64 |
| eduroam | educational users | yes | 2.4 and 5Ghz | v4 and v6 |
All networks marked as encrypted will offer layer 2 security. This is done using WPA2 enterprise with 802.1X (PEAP or TTLS) authentication and AES encryption. As usual, we are all using the same credentials (user “ietf”, password “ietf”), yet each user will get unique session encryption keys. The certificate is signed for services.meeting.ietf.org by Starfield Technologies, Inc., with the following fingerprint.
| SHA1 | 16:A9:13:FE:59:81:1E:FA:5F:2C:0D:34:A8:14:12:7C:99:FE:8F:34 |
| SHA256 | E0:A9:1D:E5:5D:6C:8D:C6:2E:78:B5:09:4F:B9:84:87:A8:D7:B4:CE:A6:C0:3F:EC:F0:21:C8:69:C3:D1:E1:81 |
Our wireless LAN infrastructure implements the following two BCP38-like filtering.
- 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/NS are filtered out. Proxy ARP/ND is performed by our wireless LAN controllers for this filtering.
Experiments
Experiments on the IETF network need to be approved by the IETF Chair. For IETF 106, the following Experiment has been approved and has been implemented:
- CAPPORT - this is an draft-ietf-capport-rfc7710bis style CAPPORT experiment. Note: this is no captive portal, this simply provides information for CAPPORT clients.
Guest Room and Public Space Access
The IETF Network is being extended to the guest rooms and public spaces throughout the Swissotel and the Fairmont. This is being delivered via the hotel's wireless infrastructure as an additional SSID, "ietf-hotel".
Note If you have performance issues with this network, please let us know. Please note though, that while we are using the IETF meeting network for Internet connectivity, we are using the hotel's infrastructure for delivery to the guest rooms and public space, so there are limits to the improvements we can effect.
Support
If you have trouble using the guest room and public space SSID "ietf-hotel", please contact at the Help Desk or via tickets @ meeting.ietf.org and we’ll be glad to help!
A Note For Windows Users
Connecting to the ietf SSID on Windows 7 requires a few extra, non-intuitive steps. If you're struggling to get connected to an encrypted SSID on your Windows laptop, please come by the Help Desk. Alternatively, you can try yourself; Instructions are here >> https://tickets.meeting.ietf.org/attachment/wiki/WindowsInformation/IETF%20Wifi%20Instructions%20Windows.pdf
Printing
There is a printer at the Help Desk and is available to all IETF users. The printer is an HP OfficeJet Pro 8720 and is accessible via LPD, Bonjour, standard TCP/IP on port 9100. The hostname for it is ietf-106-printer.meeting.ietf.org.
| Name | Model | Capabilities | IPv4 Address | IPv6 Address | Notes | Drivers |
| ietf-106-printer.meeting.ietf.org | HP Officejet Pro 8720 | Inkjet w/Duplexer | 31.133.160.18 | 2001:67c:370:160::18 | Bonjour name: ietf-106-printer | Printer Drivers |
Instructions for Mac OS X using Bonjour auto-setup (DNS-Based Service Discovery)
(Note that this method is not available if you have configured an explicit DNS search list. Please see below for the manual configuration instructions.
- Open System Preferences -> Print & Fax -> "+" below printer list
- Choose "Default" in the top-menu.
- You should see the printers discovered by Bonjour. Pick the right one.
- Enjoy hassle-free printing.
Instructions for Mac OS X using manual configuration
- Open System Preferences -> Print & Fax -> "+" below printer list
- Select the "IP" icon at the top of window
- Select the "HP JetDirect - Socket" from the drop down
- Enter "term-printer.meeting.ietf.org" in the Address field. Leave the Queue field blank.
- Use: should auto-populate with "Generic PostScript Printer". In the drop-down select "Choose Software" and use "HP OfficeJet Pro 8720 e-All-in-One"
- Click Add
Instructions for Windows 7
- If you haven't printed on the selected printer before, you may need to download and install the driver using one of the links above.
- When you come to the installer page asking you to choose the "Network Type" -- choose "Wired (Ethernet)."
- If you get the "Unable to Find the Printer" page, simply enter the IP address of the printer {31.133.128.18} in the box in the bottom-right corner and click "Search."
- Ignore the "The Printer and Computer are Connected to Different Routers" message and select "Next."
- The driver will finish it's installation and you *should* see a "Successful Network Installation" message.
- The fax feature is *NOT* enabled, so you may cancel the fax installation portion.
- Registering the printer is not necessary.
- You're printer is now ready to use, and you can find it by going to Start -> Devices and Printers. No need to print a test page.
Instructions for Windows using HP printing framework
- Download HP Universal Print Driver for Windows (see above)
- Select "Dynamic installation" and wait until all drivers are copied (takes about 5-10 minutes)
- Add printers by using their IP addresses in "control panel" appearing when select Start -> Settings -> Printers & faxes -> "HP Universal Printing PS" -> Properties
HP Eprint
- Find the printer's email address on a label pasted to the printer.
- Email the document to that address.
- Retrieve your print out from the Help Desk at in the Registration Area.
Services
The following network services are provided:
| Service | Address | Notes |
| SMTP | smtp.meeting.ietf.org | Will provide SMTP relay for anything within the IETF network |
| NTP | ntp.meeting.ietf.org | A stratum 2 time service is provided via IPv4 and IPv6 unicast |
| DNS | ns1.meeting.ietf.org ns2.meeting.ietf.org | Validating recursive resolvers. The domain name is meeting.ietf.org. |
These services are being provided from both of the following servers: 31.130.229.6 / [2001:67c:370:229::6] or 31.130.229.7 / [2001:67c:370:229::7]
Geolocation
There is a geolocation feed published here: https://noc.ietf.org/geo/google.csv Geolocation service for temporary networks is often hit or miss. Suggestions/assistance is welcomed. You can also try searching via www.google.com/ncr (no country re-direct).
Thanks
The terminal room and IETF network are made possible by the generous contributions by a number of companies and by the tireless efforts of our volunteer team. If you see any of these people in the halls, please be sure to thank them for all their work!
Contributors:
- Juniper Networks
- Cisco
- Netbeez
- Open Systems Consultants
Connectivity:
- Moratelino
- NTT Communications
Volunteers:
- Hirochika Asai (Preferred Networks/WIDE)
- Rob Austein (Arrcus/DRL)
- Joe Clarke (Cisco)
- Hans Kuhn (NSRC)
- Warren Kumari (Google)
- Chris Morrow (Google)
- Bill Fenner (Arista)
- Bill Jensen (University of Wisconsin–Madison)
- Karen O'Donoghue (ISOC)
- Clemens Schrimpe
Staff:
- Sean Croghan
- Con Reilly
- Ben Pedersen
- Bret Plumb
- Paul Smith
- Daniel Branik
