Changes between Initial Version and Version 1 of IETF100network


Ignore:
Timestamp:
9 Nov 2017, 05:19:07 (8 months ago)
Author:
bmheight@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IETF100network

    v1 v1  
     1= IETF 100 Network Information – Prague, Czech Republic =
     2
     3== Terminal Room ==
     4
     5The Terminal Room is located in ORD/Blundell which is adjacent to the South Atrium. The Terminal Room is open 24 hours each day beginning Sunday, November 12th, 2017 at 16:00 and ending on Friday, 27 November, 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.
     6
     7Please 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.
     8
     9When 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.
     10
     11Please note that at the request of the IETF Chair, demonstrations are no longer permitted in the Terminal Room.
     12
     13== Help Desk ==
     14A help desk is being provided and will be staffed the following hours:
     15
     16|| Sunday || 16:00 to 19:00 ||
     17|| Monday ||  8:00 to 20:00 ||
     18|| Tuesday ||  8:00 to 19:00 ||
     19|| Wednesday ||  8:00 to 20:00 ||
     20|| Thursday ||  8:00 to 20:00 ||
     21|| Friday ||  8:00 to 15:00 ||
     22
     23== NOC and Ticketing ==
     24
     25There are several ways to communicate with the NOC staff.
     26 * 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"].
     27 * Send an email to '''`tickets @ meeting.ietf.org`''' with as much detail regarding your issue and configuration as possible.
     28 * 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.
     29{{{#!comment
     30* Use the Jabber room at noc @ jabber.ietf.org to report issues or communicate with the NOC.
     31}}}
     32
     33You can also use trac to review outstanding tickets before reporting an issue or to update outstanding tickets.
     34
     35The Secretariat also maintains a ticket system for the reporting of meeting issues. Please send
     36mail to: '''`mtd @ietf.org`''' to report a problem. The Secretariat is responsible for addressing issues with:
     37
     38    * A/V in meeting rooms
     39    * Beverage and food
     40    * Jabber
     41    * Projectors
     42    * Temperature fluctuation
     43
     44
     45
     46== External Connectivity ==
     47 
     48The IETF 100 network connects to the Internet via multiple 1Gb/s uplinks donated by Starhub, NTT Communications, ViewQuest, and Moratelindo. 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 Fairmont hotels..
     49       
     50== Meeting Room Wireless ==
     51
     52An 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.
     53
     54''The main “ietf” wireless network is encrypted; make sure you enter ietf for both the username and password.''
     55
     56Here’s a quick summary of the network layout:
     57
     58|| SSID || Description || Encrypted || Frequencies || IP Versions ||
     59|| ietf || Our default network || yes || 5Ghz only || v4 and v6 ||
     60|| ietf-legacy100 || For legacy and unencrypted use || no || 2.4 and 5Ghz || v4 and v6 ||
     61|| ietf-2.4ONLY || An encrypted network for 2.4Ghz users || yes || 2.4Ghz only || v4 and v6 ||
     62|| ietf-v6ONLY || For users wanting pure IPv6 || yes || 5Ghz only || v6 only ||
     63|| ietf-nat64 || IPv6 stack with NAT64 to access IPv4 resources || yes || 5Ghz only || v6 with NAT64 & DNS64 ||
     64|| ietf-nat64-unencrypted || IPv6 stack with NAT64 to access IPv4 resources || no || 5Ghz only || v6 with NAT64 & DNS64 ||
     65|| eduroam || educational users || yes || 2.4 and 5Ghz || v4 and v6 ||
     66
     67All 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
     68
     69Our wireless LAN infrastructure implements the following two BCP38-like filtering.
     70* 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.
     71* 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.
     72
     73== Experiments ==
     74
     75Experiments on the IETF network need to be approved by the IETF Chair.  For IETF 100, the following Experiment has been approved and has been implemented:
     76    * DNS-over-TCP (DPRIVE) - Information can be found [wiki:IETF100Experiments "here"]
     77
     78
     79== Guest Room and Public Space Access ==
     80
     81The 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". 
     82
     83**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. 
     84
     85== Support ==
     86
     87If 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!
     88
     89=== A Note For Windows Users ===
     90
     91Connecting 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
     92
     93== Printing ==
     94
     95There 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".
     96
     97
     98|| Name || Model || Capabilities || IPv4 Address|| IPv6 Address || Notes || Drivers ||
     99||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] ||
     100
     101=== Instructions for Mac OS X using Bonjour auto-setup (DNS-Based Service Discovery) ===
     102(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].
     103 1. Open System Preferences -> Print & Fax -> "+" below printer list
     104 2. Choose "Default" in the top-menu.
     105 3. You should see the printers discovered by Bonjour. Pick the right one.
     106 4. Enjoy hassle-free printing.
     107
     108=== Instructions for Mac OS X using manual configuration ===
     109 1. Open System Preferences -> Print & Fax -> "+" below printer list
     110 2. Select the "IP" icon at the top of window
     111 3. Select the "HP JetDirect - Socket" from the drop down
     112 4. Enter "term-printer.meeting.ietf.org" in the Address field.  Leave the Queue field blank.
     113 5. ''Print Using'' should auto-populate
     114 6. Click Add
     115
     116=== Instructions for Windows 7===
     117 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.
     118 2. When you come to the installer page asking you to choose the "Network Type" -- choose "Wired (Ethernet)."
     119 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."
     120 4. Ignore the "The Printer and Computer are Connected to Different Routers" message and select "Next."
     121 5. The driver will finish it's installation and you *should* see a "Successful Network Installation" message.
     122 6. The fax feature is *NOT* enabled, so you may cancel the fax installation portion.
     123 7. Registering the printer is not necessary.
     124 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.
     125
     126 
     127=== Instructions for Windows using HP printing framework ===
     128 1. Download HP Universal Print Driver for Windows (see above)
     129 2. Select "Dynamic installation" and wait until all drivers are copied (takes about 5-10 minutes)
     130 3. Add printers by using their IP addresses in "control panel" appearing when select Start -> Settings -> Printers & faxes -> "HP Universal Printing PS" -> Properties
     131
     132=== HP Eprint
     1331. Find the printer's email address on a label pasted to the printer.
     1342. Email the document to that address.
     1353. Retrieve your print out from the Terminal Room
     136
     137=== Scanning Services ===
     1381. In a browser (Firefox appears to be the only browser that renders the pages properly) go to: https://term-printer.meeting.ietf.org/
     1392. Select the "Scan" tab located at the top of the page.
     1403. Select Document Type "PDF" in the drop-down menu
     1414. Place pages to be scanned face-up in the page feeder on top of the printer.
     1425. Press "Start Scan" on the web page.
     1436. Once the Scan has completed a window to the right will display the PDF contents of the scan.
     1447. Using the scroll bar in the Image Preview - Scroll to the right and select the "Download" button
     145
     146
     147== Services ==
     148
     149The following network services are provided:
     150
     151|| Service || Address || Notes ||
     152|| SMTP || smtp.meeting.ietf.org || Will provide SMTP relay for anything within the IETF network ||
     153|| NTP || ntp.meeting.ietf.org || A stratum 2 time service is provided via IPv4 and IPv6 unicast ||
     154|| DNS || ns1.meeting.ietf.org ns2.meeting.ietf.org || Validating recursive resolvers. The domain name is meeting.ietf.org. ||
     155
     156These services are being provided from both of the following servers:
     15731.130.229.6 / [2001:67c:370:229::6]
     158or
     15931.130.229.7 / [2001:67c:370:229::7]
     160
     161== Geolocation ==
     162There is a geolocation feed published here: [https://noc.ietf.org/geo/google.csv]
     163Geolocation service for temporary networks is often hit or miss. Suggestions/assistance is welcomed.
     164You can also try searching via www.google.com/ncr (no country re-direct).
     165
     166
     167== Thanks ==
     168The 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!
     169
     170
     171Contributors:
     172* Juniper Networks
     173* Cisco
     174* Netbeez
     175* nephos6
     176* A10
     177* Open Systems Consultants
     178
     179Connectivity:
     180* Starhub
     181* NTT Communications
     182* ViewQuest
     183* Moratelindo
     184
     185Volunteers:
     186* Hirochika Asai (Preferred Networks/WIDE)
     187* Rob Austein (DRL)
     188* Randy Bush (IIJ)
     189* Joe Clarke (Cisco)
     190* Warren Kumari (Google)
     191* Bill Fenner (Arista)
     192* Joel Jaeggli (Fastly)
     193* Bill Jensen (University of Wisconsin–Madison)
     194* Lucy Lynch
     195* Mikael Kresk(CESNET)
     196* Jim Martin (INOC)
     197* Karen O'Donoghue (ISOC)
     198* Clemens Schrimpe
     199
     200
     201Staff:
     202* Rick Alfvin
     203* Nick Kukich
     204* Edward !McNair
     205* Con Reilly
     206* Brandon Height