[101all] IETF 101 London Network Information

Jim Martin <jim@daedelus.com> Sat, 17 March 2018 16:48 UTC

Return-Path: <jim@daedelus.com>
X-Original-To: 101all@ietfa.amsl.com
Delivered-To: 101all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2151271DF for <101all@ietfa.amsl.com>; Sat, 17 Mar 2018 09:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQEqE_75-Q9O for <101all@ietfa.amsl.com>; Sat, 17 Mar 2018 09:48:17 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60A0512711E for <101all@ietf.org>; Sat, 17 Mar 2018 09:48:17 -0700 (PDT)
Received: from imladris.daedelus.com (imladris.daedelus.com [206.197.161.143]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 4FB568810A for <101all@ietf.org>; Sat, 17 Mar 2018 09:48:17 -0700 (PDT)
Received: from dhcp-882a.meeting.ietf.org (dhcp-882a.meeting.ietf.org [31.133.136.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id 9BB9513083AB for <101all@ietf.org>; Sat, 17 Mar 2018 09:48:16 -0700 (PDT)
From: Jim Martin <jim@daedelus.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Reply-To: 101attendees@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Message-Id: <9FDC18B7-E057-4148-AAA8-23264A2EB0D7@daedelus.com>
Date: Sat, 17 Mar 2018 16:48:14 +0000
To: 101all@ietf.org
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/101all/R_OKx764sIEto9hcV5i-X2jyTCM>
Subject: [101all] IETF 101 London Network Information
X-BeenThere: 101all@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of all 101 attendees for official communication <101all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/101all>, <mailto:101all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/101all/>
List-Post: <mailto:101all@ietf.org>
List-Help: <mailto:101all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/101all>, <mailto:101all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2018 16:48:20 -0000

Gentlepeople,
	Welcome to London! Below you will find the usual Network Information documentation. As always, it’s a render of the wiki page the NOC keeps at https://tickets.meeting.ietf.org/wiki/IETF101network … please reference that as it’s MUCH more readable.

	PLEASE NOTE: The Metropole has renovated guest rooms in the entire West Wing and in the 16th floor and above in the Tower. As part of this renovation, they’ve improved the wireless infrastructure to be both more modern and higher density. We believe that these renovated areas will provide the best guest room wireless experience in the Metropole. The NOC and the secretariat have worked with the hotel to get as many as our attendees in this renovated space as possible, but if you’re having guest room network issues and aren’t in a renovated room, please contact the front desk to see if it’s possible to move into the renovated floors. 

	Again, welcome to London, and have a great week!

	- Jim and the NOC Team

= IETF 101 Network Information – London, United Kingdom =

== Terminal Room ==

The Terminal Room is located in Berkeley and Cadogan on the Mezzanine Level. The Terminal Room is open 24 hours each day beginning Sunday, March 18th, 2018 at 16:00 and ending on Friday, March 23rd, 2018 at 15:00. A help desk is provided and the hours are listed below.  The room itself consists of approximately 50 seats, providing some wired access and 220v power ports with type G (UK) connections. There is also an HP Officejet Pro 8710 printer available.

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, help desk support, print documents, 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. To cut down on the mess, ethernet cables have not been installed to every seat in the Terminal Room. If you need a cable, please ask at the Help Desk.

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 and will be staffed the following hours: 

|| Sunday || 16:00 to 18:00 ||
|| Monday ||   8:00 to 20:00 ||
|| Tuesday ||   8:00 to 17:00 ||
|| Wednesday ||   8:00 to 20:00 ||
|| Thursday ||   8:00 to 20: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 [https://tickets.meeting.ietf.org/newticket "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 [https://tickets.meeting.ietf.org/login "log in"].
* Send an email to '''`tickets @ meeting.ietf.org`''' with 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 101 network connects to the Internet via a pair of 1Gb/s uplinks graciously donated by British Telecom. 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 Hilton London Metropole 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-legacy101 || 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. Stefan Winter has kindly provided signed profiles that will supply the appropriate SSL certs: https://802.1x-config.org/?idp=137&profile=101

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 101, no experiments have been approved. The previous DPRIVE (DNS over TLS) experiment has been adopted as a production service, and continues to be available.


== Guest Room and Public Space Access ==

The IETF Network is being extended to the guest rooms and public spaces throughout the Hilton London Metropole.  This is being delivered via the hotel's wireless infrastructure as an additional SSID, "ietf-hotel".  There is no working wired Ethernet connectivity into the guest rooms. 

**Note** The Hilton Metropole has upgraded it's wireless on the renovated floors (The entire West Wing and  floors 16 and above in the Tower). If you're on a "classic" floor and are experiencing wireless issues, please enquire with the front desk about being moved to a renovated floor. If you have performance issues on the renovated floors,  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 us in the Terminal Room (Berkeley and Cadogan rooms) 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 in the Terminal Room and is available to all IETF users. The printer is an HP !OfficeJet Pro 8710 and is accessible via LPD, Bonjour, standard TCP/IP on port 9100.  The hostname for it is term-printer.meeting.ietf.org.  This printer is compatible with the !OfficeJet Pro 8620 we've used in previous meetings, so if you were able to use the printers previously, this one should "just work".


|| Name || Model || Capabilities || IPv4 Address|| IPv6 Address || Notes || Drivers ||
||term-printer.meeting.ietf.org || HP Officejet Pro 8710 || Inkjet w/Duplexer || 31.133.160.18 || 2001:67c:370:160::18 || Bonjour name: // term-printer // || [https://support.hp.com/us-en/product/HP-Officejet-Pro-8610-e-All-in-One-Printer-series/5367611/drivers 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 [https://tickets.meeting.ietf.org/wiki/IETF101network#InstructionsforMacOSXusingmanualconfiguration the manual configuration instructions].
1. Open System Preferences -> Print & Fax -> "+" below printer list
2. Choose "Default" in the top-menu.
3. You should see the printers discovered by Bonjour. Pick the right one.
4. Enjoy hassle-free printing.

=== Instructions for Mac OS X using manual configuration ===
1. Open System Preferences -> Print & Fax -> "+" below printer list
2. Select the "IP" icon at the top of window
3. Select the "HP !JetDirect - Socket" from the drop down
4. Enter "term-printer.meeting.ietf.org" in the Address field.  Leave the Queue field blank.
5. ''Use:'' should auto-populate with "Generic !PostScript Printer". In the drop-down select "Choose Software" and use "HP !OfficeJet Pro 8610 e-All-in-One"
6. Click Add

=== Instructions for Windows 7===
1. 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.
2. When you come to the installer page asking you to choose the "Network Type" -- choose "Wired (Ethernet)."
3. 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."
4. Ignore the "The Printer and Computer are Connected to Different Routers" message and select "Next."
5. The driver will finish it's installation and you *should* see a "Successful Network Installation" message.
6. The fax feature is *NOT* enabled, so you may cancel the fax installation portion.
7. Registering the printer is not necessary.
8. 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 ===
1. Download HP Universal Print Driver for Windows (see above)
2. Select "Dynamic installation" and wait until all drivers are copied (takes about 5-10 minutes)
3. Add printers by using their IP addresses in "control panel" appearing when select Start -> Settings -> Printers & faxes -> "HP Universal Printing PS" -> Properties

=== HP Eprint
1. Find the printer's email address on a label pasted to the printer.
2. Email the document to that address.
3. Retrieve your print out from the Terminal Room 

== 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
* A10
* Open Systems Consultants

Connectivity:
* British Telecom

Volunteers:
* Hirochika Asai (Preferred Networks/WIDE)
* Rob Austein (DRL)
* Randy Bush (IIJ)
* Joe Clarke (Cisco)
* Hans Kuhn (NSRC)
* Warren Kumari (Google)
* Bill Fenner in absentia (Arista)
* Bill Jensen (University of Wisconsin–Madison)
* Lucy Lynch
* Jim Martin (INOC)
* Karen O'Donoghue (ISOC)
* Clemens Schrimpe 


Staff: 
* Rick Alfvin
* Sean Croghan
* Nick Kukich
* Edward !McNair
* Con Reilly