[99all] IETF 99 Prague Network Information

Jim Martin <jim@daedelus.com> Fri, 14 July 2017 15:18 UTC

Return-Path: <jim@daedelus.com>
X-Original-To: 99all@ietfa.amsl.com
Delivered-To: 99all@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 64C4E1318F6 for <99all@ietfa.amsl.com>; Fri, 14 Jul 2017 08:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id u88JgRt3oH_P for <99all@ietfa.amsl.com>; Fri, 14 Jul 2017 08:18:17 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B001318A9 for <99all@ietf.org>; Fri, 14 Jul 2017 08:18:17 -0700 (PDT)
Received: from imladris.daedelus.com (imladris.daedelus.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0489D8814A for <99all@ietf.org>; Fri, 14 Jul 2017 08:18:17 -0700 (PDT)
Received: from [IPv6:2001:67c:370:128:49ca:8914:7bf8:1f65] (unknown [IPv6:2001:67c:370:128:49ca:8914:7bf8:1f65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id 380901308395 for <99all@ietf.org>; Fri, 14 Jul 2017 08:18:16 -0700 (PDT)
From: Jim Martin <jim@daedelus.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <EC912F62-CBCF-45BE-9DF6-0B292B4A0E26@daedelus.com>
Date: Fri, 14 Jul 2017 17:18:14 +0200
To: 99all@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/99all/cymHOGVcoUDTymDcvTsE4Ttoi3Q>
Subject: [99all] IETF 99 Prague Network Information
X-BeenThere: 99all@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of all 99 attendees for official communication <99all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/99all>, <mailto:99all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/99all/>
List-Post: <mailto:99all@ietf.org>
List-Help: <mailto:99all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/99all>, <mailto:99all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 15:18:19 -0000

	Welcome to IETF 99 in Prague! Appended below is a text representation of the Network Information wiki page available at https://tickets.meeting.ietf.org/wiki/IETF99network . Please forgive formatting peccadillos … the version on the wiki is cleaner.

	There are a few things worth calling out as different for this meeting. As many of you know, the IETF NOC provides a number of wireless SSIDs.  One of them has no over-the-air encryption.  It has been traditionally named ietf-legacy; and many attendees' laptops may remember and prefer it.  In order to make running without over-the-air encryption a conscious decision, the SSID has been renamed to ietf-legacy99, and will likely have a new name for every new meeting.  The list of all SSIDs and their attributes can be found in the document below.

	Secondly, the “ietf-nat64” SSID has been available for many meetings as an experimental network providing NAT64 services. With many thanks to A10 and John Brzozowski of Comcast, we’ve received a second A10 switch to provide redundancy, and thus we can now consider the NAT64 network as a production service. Please consider using this network as your primary Internet access this week! Please do report any issues via the ticketing system (see below).

	Finally, there is an experimental deployment of DNS-over-TLS (RFC 7858 /DPRIVE) that has been organized by Warren Kumari and Erik Kline.  If you’re interested in trying it, details can be found at https://tickets.meeting.ietf.org/wiki/IETF99Experiments .
	As always, please let the NOC know if you have any issues. The Helpdesk is available in the Terminal Room (Sofia), and the ticketing system can be found at tickets.meeting.ietf.org or you can simply email to tickets@meeting.ietf.org.

	Have a good meeting!

	-Jim & the IETF NOC Team


= IETF 99 Network Information – Prague, Czech Republic =

== Terminal Room ==

The Terminal Room is located in Sofia on the Lobby Level near the business center. The Terminal Room is open 24 hours each day beginning Sunday, 17 July, 2017 at 16:00 and ending on Friday, 21 July, 2017 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. 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 19:00 ||
|| Monday       ||  8:00 to 20:00 ||
|| Tuesday.     ||  8:00 to 19: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 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 99 network connects to the Internet via multiple 1Gb/s uplinks donated by T-mobile.cz and Dial Telecom. The IETF uses 2001:67c:370::/48 and 2001:67c:1230::/46 for IPv6 and and for IPv4. We are supplying bandwidth for the conference space, as well as wired and wireless connections in the guest rooms of the Hilton Prague 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-legacy99 || 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 ||
|| 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

== Experiments ==

Experiments on the IETF network need to be approved by the IETF Chair.  For IETF 99, the following Experiment has been approved and has been implemented:
    * DNS-over-TCP (DPRIVE) - Information can be found at https://tickets.meeting.ietf.org/wiki/IETF99Experiments

== Guest Room and Public Space Access ==

The IETF Network is being extended to the guest rooms and public spaces throughout the Prague Hilton.  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 us in the Terminal Room (Sofia room) 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 || || 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/IETF91network#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. ''Print Using'' should auto-populate
 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 {} 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 

=== Scanning Services ===
1. In a browser (Firefox appears to be the only browser that renders the pages properly) go to: https://term-printer.meeting.ietf.org/
2. Select the "Scan" tab located at the top of the page.
3. Select Document Type "PDF" in the drop-down menu
4. Place pages to be scanned face-up in the page feeder on top of the printer. 
5. Press "Start Scan" on the web page.
6. Once the Scan has completed a window to the right will display the PDF contents of the scan.
7. Using the scroll bar in the Image Preview - Scroll to the right and select the "Download" button

== 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: / [2001:67c:370:229::6] 
or / [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!

* Juniper Networks
* Cisco
* Netbeez
* nephos6
* A10
* Open Systems Consultants

* T-mobile.cz
* Dial Telecom

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

* Rick Alfvin
* Sean Croghan
* Nick Kukich
* Edward McNair
* Con Reilly