[94all] IETF 94 Network Information – Yokohama, Japan

Jim Martin <jrmii@isc.org> Sun, 01 November 2015 07:07 UTC

Return-Path: <jrmii@isc.org>
X-Original-To: 94all@ietfa.amsl.com
Delivered-To: 94all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEB8A1B6C4E for <94all@ietfa.amsl.com>; Sun, 1 Nov 2015 00:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.611
X-Spam-Level:
X-Spam-Status: No, score=-8.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 CMa7x43uTEab for <94all@ietfa.amsl.com>; Sun, 1 Nov 2015 00:07:49 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5433E1B6C38 for <94all@ietf.org>; Sun, 1 Nov 2015 00:07:49 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id F1D6A1FCAB3 for <94all@ietf.org>; Sun, 1 Nov 2015 07:07:44 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5CAC216003E for <94all@ietf.org>; Sun, 1 Nov 2015 07:08:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4AED0160097 for <94all@ietf.org>; Sun, 1 Nov 2015 07:08:16 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PyublwFjXfRs for <94all@ietf.org>; Sun, 1 Nov 2015 07:08:16 +0000 (UTC)
Received: from [133.93.1.219] (unknown [133.93.1.219]) by zmx1.isc.org (Postfix) with ESMTPSA id B5F9B16003E for <94all@ietf.org>; Sun, 1 Nov 2015 07:08:15 +0000 (UTC)
From: Jim Martin <jrmii@isc.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF0B99A3-CD02-48C8-B885-6368B374A216@isc.org>
Date: Sun, 1 Nov 2015 16:07:41 +0900
To: 94all@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3106\))
X-Mailer: Apple Mail (2.3106)
Archived-At: <http://mailarchive.ietf.org/arch/msg/94all/jIk3oZWtASE6_VCwTvsJYfM_cMA>
Subject: [94all] =?utf-8?q?_IETF_94_Network_Information_=E2=80=93_Yokohama?= =?utf-8?q?=2C_Japan?=
X-BeenThere: 94all@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of all 94 attendees for official communication." <94all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/94all>, <mailto:94all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/94all/>
List-Post: <mailto:94all@ietf.org>
List-Help: <mailto:94all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/94all>, <mailto:94all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 07:07:53 -0000

Gentlepeople,
	I’ve been asked to post this, but it’s the excellent engineers of WIDE and their partners who have brought you the network for IETF 94, with consultation from a number of the international IETF NOC team. Please join me in thanking them for their hard work and dedication.

	This is a rough text extraction of https://tickets.meeting.ietf.org/wiki/IETF94network - Please check that out, as it’s clickable and gets updated!

	- Jim


= IETF 94 Network Information – Yokohama, Kanagawa, JP =

== Terminal Room ==

The Terminal Room is located in room 315 on the 3rd Floor of the Pacifico Yokohama and is open until 24:00 (midnight) beginning on Monday, 2 November 2015 at 08:00 and ending on Friday, 6 November 2015 at 15:00. A help desk is being provided with hours listed below.  The room itself consists of approximately 120 seats, providing some wired access and 100v power ports. There is also an HP Officejet Pro 8610 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, Internet access, help desk support, or print documents.

When using the Ethernet connections in the Terminal Room, IPv4 addressing is provided via DHCP. Please use Dynamic Auto-configuration for IPv6. A stateless 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: 

|| Monday ||  08:00 to 20:00 ||
|| Tuesday ||  08:00 to 20:00 ||
|| Wednesday ||  08:00 to 20:00 ||
|| Thursday ||  08:00 to 20:00 ||
|| Friday ||  08:00 to 16:00 ||

== NOC and Ticketing ==

There are several ways to communicate with the NOC staff. 
1. 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" may 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"].
2. Send an email to '''`tickets@meeting.ietf.org`''' with as much detail regarding your issue and configuration as possible. 
3. 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.
4. Use the Jabber room at noc @ jabber.ietf.org to report issues or communicate with the NOC. 

You can also use trac to review outstanding tickets before reporting an issue or to update outstanding tickets.

== Network Basics ==

=== External Connectivity ===

The IETF 94 network connects to the Internet via four 1 Gb/s links provided by NTT Communications and NTT East, KDDI, and Softbank. The IETF is using 133.93.0.0/16 for IPv4 and 2001:c40::/32 for IPv6. We are supplying bandwidth for the conference space, public spaces, in-room wireless, and wired connections at the Yokohama Grand !InterContinental Hotel and Bay Hotel Tokyu Yokohama.

== Meeting Room Wireless ==


An 802.11 a/g/n/ac wireless network is provided throughout the venue on both 2.4 and 5 GHz bands, in conjunction with IPv4 and IPv6 addresses.

The main "ietf" wireless network is now encrypted; when prompted for credentials, enter ietf for both the username and password.

Here’s a quick summary of the new network layout:


|| SSID          || Description                                                                          || Encrypted   || Frequencies    || IP Versions                     ||
|| ietf              || Our default network                                                            || yes         || 5Ghz only            || v4 and v6                        ||
|| ietf-legacy   || 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 a 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                         ||
|| ietf-wheel      || for Wheel guys, Grab it on the top of Ferris wheel           || no          || 2.4 and 5GHz       || v4 and v6                         ||
|| ietf-outdoor  || southern area from Pacifico                                               || no          || 2.4 and 5GHz       || v4 and v6                         ||


All networks marked as encrypted will offer layer 2 security. This is done using WPA enterprise with 802.1X (PEAP or TTLS) authentication and AES  encryption. Although all users have the same credentials (user "ietf", password "ietf"), each user will get unique session encryption keys. Our Radius authentication servers use a certificate that you can verify by going to this page: https://www.ietf.org/registration/MeetingWiki/wiki/92net

See the following archived email from Chris Elliot for an in-depth explanation of the changes made to the wireless configuration. https://www.ietf.org/mail-archive/web/92all/current/msg00009.html

If you plan to ride the Ferris wheel, you may want to check ssid 'ietf-wheel' so that you can work even in a cage of the Ferris wheel :-)

== Guest Room Access ==

The IETF Network is being extended to the guest rooms in the !InterContinental Yokohama Grand and The Yokohama Bay Hotel Tokyu. *Note* that while we are using the IETF meeting network for Internet connectivity, we are using the hotel's infrastructure for the delivery to the guest rooms, so there are limits to the improvements we can effect.  We recommend using the wired connection if you experience poor connectivity in your guest room.

Wired:
	IPv4 and IPv6 and provided via the wired connection in your room. 

Wireless:
	In the guest room areas you should find the "ietf-hotel" SSID.  This network is 2.4GHz/5GHz and is being delivered via the hotels' access points. We encourage heavy users and/or those having poor coverage to use the wired connection.

== Support ==

If you have trouble using any of the public or guest room services, please try to switch to the hotel SSIDs ("INTERCONTINENTAL" at InterContinental Yokohama Grand, "YBHTROOM-WiFi" at The Yokohama Bay Hotel Tokyu) or the hotel wired port.  If that doesn’t work, please contact your hotel support as listed in your room. If things are working fine on the hotel offerings but not on the IETF SSIDs/ports, please contact us in the Terminal Room (315) or via tickets @ meeting.ietf.org  and we’ll be glad to help!

== Printing ==

There is a printer in the Terminal Room that is available to all IETF users. The printer is an HP Officejet Pro 8610 and is accessible via LPD, Bonjour, and standard TCP/IP on port 9100.  The hostname for it is term-printer.meeting.ietf.org.  A4 paper only (sorry no letter size paper).


|| Name || Model || Capabilities || IPv4 Address|| IPv6 Address || Notes || Drivers ||
||term-printer.meeting.ietf.org || HP Officejet Pro 8610 || Inkjet w/Duplexer || 133.93.0.240 || 2001:c40:0:3000::240 || Bonjour name: // term-printer // || [http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en&lc=en&product=4323659& 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 {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. Your 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 from /// [http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=4323647&lang=en&cc=us&taskId=135&prodSeriesId=4322915&prodTypeId=18972 HP Support] ///
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 for Android devices
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: http://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.ietf94.jp ns2.meeting.ietf94.jp || Validating recursive resolvers. The domain name is meeting.ietf94.jp. ||

These services are being provided from both of the following servers:[[br]]
133.93.5.6 / [2001:c40:0:3005::6] [[br]]
or[[br]]
133.93.5.7 / [2001:c40:370:3005::7] [[br]]

== 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:
* A10 Networks
• Alaxala Networks
• Cisco Systems
* NTT East

Connectivity:
• KDDI 
• NTT Communications 
* Softbank

Volunteers:
• Hirochika Asai (WIDE)
• Chris Elliott
• Tetsuya Innami (!CiscoSystems)
• Bill Jensen (University of Wisconsin –Madison)
• Teppei Kamata (!CiscoSystems)
• Satoshi Katayama (!CiscoSystems)
* Akira Kato (Keio University/WIDE Project)
* Ryosuke Kato (BBTower)
• Kentaro Koba (!CiscoSystems)
* Dai Kobayashi (Alaxala Networks)
• Hans Kuhn (NSRC)
• Warren Kumari (Google)
• Lucy Lynch (NSRC)
• Jim Martin (Internet Systems Consortium)
• Mami Nakamura (Keio University)
• Ryo Nakamura (WIDE)
• Kaname Nishizuka (NTT Communications)
* Masafumi Oe (NAOJ)
* Fumiko Ohmiya (Alaxala Networks)
• Yoshihiro Onodera (!CiscoSystems)
• Shoichi Sakane (!CiscoSystems)
* Yuji Sekiya (WIDE)
* Shoya Taguchi (University of Tokyo)
* Yuichiro Tahara (KDDI)
• Takashi Tomine (WIDE/NICT)
* Yukito Ueno (Keio University)
* Motomu Utsumi (University of Tokyo)
• Ayumu Yasuda (NTT Communications)
• Takaaki Naruse (KDDI)
* Randy Bush (IIJ/DRL)