From nobody Fri Nov 3 07:24:39 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C8B13FC10; Fri, 3 Nov 2017 07:24:30 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: "IETF Announcement List" Cc: recentattendees@ietf.org, ietf@ietf.org, 100all@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.64.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: IETF Agenda Message-ID: <150971907077.29038.1461911075651754442.idtracker@ietfa.amsl.com> Date: Fri, 03 Nov 2017 07:24:30 -0700 Archived-At: Subject: [100all] IETF 100 Early Bird Deadline Today! X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2017 14:24:31 -0000 IETF 100 Singapore November 11-17, 2017 Host: Cisco IETF 100 Information: https://ietf.org/meeting/100/index.html 1. Early Bird Deadline The early bird deadline for registration is Friday, November 3rd. Be sure to register and pay before the deadline passes! Register online at: https://ietf.org/meeting/register.html 2. Thursday Speaker Series Topic — 3 years on: Open Standards, Open Source, Open Loop At IETF 91, many outrageous claims were emphatically made about the relationship between Open Standards and Open Source. Three years later, let’s take a look at how much progress has been made, if any; and discuss successes and failures. Communities of developers and engineers have fully formed Open Source efforts and are building large, effective communities without any documented standardization as a part of their strategy. How should SDOs interact with developers, communities and deployers of Open Source? There are claims and perhaps proof that Open Source now fully defines the industries "de facto Standards." Does the process of standardization and the contents and lifecycle of a standard need to fundamentally change? Logistics: • Room: Canning • Date: Thursday, November 16, 2017 • Time: 12:30 – 13:15 • Lunch will NOT be provided. Speaker Biography: Dave Ward, Senior Vice President, Chief Architect & CTO - Engineering Dave is Chief Architect at Cisco Systems, responsible for architectural governance, defining strategy, development of new technology and leading use-inspired research. Working via tight partnerships with customers, partners, developers and academia he is also leading co-development and co-innovation initiatives. He has been the Routing Area Director at the IETF and chair of four Working Groups: IS-IS, HIP, BFD and Softwires and worked with the ITU-T, ONF and several Open Source consortia. David was also a Juniper Fellow and Chief Architect working on the operating system and next-generation routing systems. Dave has a small vineyard in the Santa Cruz Mountains and an heirloom tomato farm along the St. Croix River in Somerset, Wisconsin. 3. Code Sprint The IETF 100 Code Sprint in Singapore will, as always, let you work on fixing those things about the datatracker which you most urgently desire to do something about. When: Saturday, November 11 from 09:30 to 18:00 Where: Raffles City Convention Center, Room Ord Signup: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF100SprintSignUp More information: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF100Sprint 4. Hackathon The IETF is holding a Hackathon at IETF 100 to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. When: Saturday November 11 and Sunday November 12 Where: Raffles City Convention Center, Room Moor/Morrison Signup: https://www.ietf.org/registration/ietf100/hackathonregistration.py More information: http://ietf.org/hackathon/100-hackathon.html Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon The Hackathon is free to attend and open to all. Extend the invitation to colleagues outside the IETF! Descriptions and information regarding the technologies for the hackathon are located on the IETF 100 Meeting Wiki: https://www.ietf.org/registration/MeetingWiki/wiki/100hackathon Don’t see anything that interests you? Feel free to add your preferred technology to the list, sign up as its Champion and show up to work on it. Note: you must login to the wiki to add content. If you do add a new technology, we strongly suggest that you send an email to hackathon@ietf.org to let others know. You may generate interest in your technology, and find other people who want to contribute to it. To request a wiki account, please click on the “login” button on the bottom right corner of the page, and choose “register.” If you need a new password please click on the “login” button on the bottom right corner of the page and choose “Send new password.” 5. Side Meetings The IESG is continuing the side meeting experiment in Singapore with some slight modifications based on the comments received from the experiment in Prague. For IETF 100, two rooms are available for first-come first-served (FCFS) signup online. The larger of the two (Hullet) will hold approximately 40 people and will be configured with a U-shaped table. The smaller room (Butterworth) will be configured as a boardroom and will hold approximately 12 people; please note that this smaller room was previously the onsite signup room, so there will be no onsite signup room at IETF 100. Both Hullet and Butterworth rooms will have projectors. You can sign up for either room by visiting the IETF meeting wiki and navigating to Side Meetings via the Table of Contents. See: https://www.ietf.org/registration/MeetingWiki/wiki/ietf100# side_meetings You will need to login to the wiki in order to reserve a room. If you’ve registered for an IETF meeting in the recent past, an account has been automatically created for you. If you have trouble logging into the wiki, you can choose to reset your password. The coveted morning, lunch and evening slots are not currently available for reservation, but will be made available at the start of IETF 100. Please include your name, email and a short description of the meeting when reserving the room, and please limit yourself to no more than a total of three hours during the IETF meeting week. In addition, please remember that meetings held in these rooms are subject to the IETF Meeting Policy: https://www.ietf.org/meeting/meeting-rooms-policy.html. Important Dates: https://ietf.org/meeting/important-dates.html#ietf100 From nobody Mon Nov 6 11:33:30 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 713C213AF75 for <100all@ietf.org>; Mon, 6 Nov 2017 11:33:28 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <150999680842.5393.7575727317009756718.idtracker@ietfa.amsl.com> Date: Mon, 06 Nov 2017 11:33:28 -0800 Archived-At: Subject: [100all] Bringing Medications to Singapore X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Nov 2017 19:33:28 -0000 As you get ready to travel to IETF 100 in Singapore, we want to remind you that Singapore has very strict rules about bringing personal medications into the country. For more information, please see http://www.hsa.gov.sg/pub/faq/faq/faqcategory/bringing-personal-medication-into-singapore.aspx. In addition, the consequences for bringing prohibited substances and goods into Singapore are very severe. Please be aware of which items are prohibited. For more information, please see: https://www.customs.gov.sg/individuals/going-through-customs/arrival/prohibited-and-controlled-goods. IETF Secretariat From nobody Thu Nov 9 02:02:16 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E07A11289C3 for <100all@ietf.org>; Thu, 9 Nov 2017 02:02:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151022173387.31099.14574208012912018369.idtracker@ietfa.amsl.com> Date: Thu, 09 Nov 2017 02:02:13 -0800 Archived-At: Subject: [100all] Reminder: Breakfast not provided at IETF 100 X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2017 10:02:14 -0000 We are looking forward to seeing all of you soon in Singapore! We would like to remind you that, as previously announced [1] and stated online [2], breakfast will not be provided at IETF 100. Both the Fairmont and the Swissotel have a breakfast-included guest room option, as do the majority of the IETF overflow properties. If you choose to forgo the breakfast-included rate, please make sure to make alternate arrangements for your morning meal. The Raffles City Convention Center (RCCC) contains a shopping mall with a number of breakfast options, some opening as early 7:30am. Regards, IETF Secretariat [1] https://mailarchive.ietf.org/arch/msg/ietf-announce/LXasx-ZsDRMBuoLz9KIeGUjDVPY [2] https://www.ietf.org/meeting/100/hotel.html From nobody Thu Nov 9 21:51:42 2017 Return-Path: X-Original-To: 100all@ietfa.amsl.com Delivered-To: 100all@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D44129AA8 for <100all@ietfa.amsl.com>; Thu, 9 Nov 2017 21:51:40 -0800 (PST) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 YwD0eO2M3kV8 for <100all@ietfa.amsl.com>; Thu, 9 Nov 2017 21:51:36 -0800 (PST) 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 9EAFA12EAA4 for <100all@ietf.org>; Thu, 9 Nov 2017 21:51:36 -0800 (PST) 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 90315880E3 for <100all@ietf.org>; Thu, 9 Nov 2017 21:51:36 -0800 (PST) Received: from [IPv6:2001:67c:1232:144:5536:3e05:76fe:37f0] (unknown [IPv6:2001:67c:1232:144:5536:3e05:76fe:37f0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id A5DE413083E5 for <100all@ietf.org>; Thu, 9 Nov 2017 21:51:35 -0800 (PST) From: Jim Martin Content-Type: multipart/alternative; boundary="Apple-Mail=_C91E4145-1D7D-4DAC-A9E0-09C2739928AC" Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.11\)) Message-Id: <074664C2-8231-4DFD-83B3-3AEA4E96AD38@daedelus.com> Date: Fri, 10 Nov 2017 13:51:31 +0800 To: 100all@ietf.org X-Mailer: Apple Mail (2.3445.5.11) Archived-At: Subject: [100all] IETF 100 Network Information X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 05:51:40 -0000 --Apple-Mail=_C91E4145-1D7D-4DAC-A9E0-09C2739928AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Gentlepeople, Welcome to Singapore! Below you will find the usual Network = Information documentation. As always, it=E2=80=99s a render of the wiki = page the NOC keeps at = https://tickets.meeting.ietf.org/wiki/IETF100network = =E2=80=A6 please = reference that as it=E2=80=99s MUCH more readable. This meeting we=E2=80=99re trying very hard to help NAT64 mature = enough that it could potentially be viable as the primary way people = access the Internet. To that end, Jen Linkova (furry@google.com = ) and Randy Bush (randy@psg.com = ) have put forth the following request: =E2=80=94=E2=80=94 The IPv6-only SSID 'ietf-nat64' has been available at IETF meetings for years; but unfortunately the number of devices using that network is usually far lower than on the dual-stack one. It would be highly desirable to see more people using it (or to know why they can not) as we should eat our own dogfood. If you have not been using the 'ietf-nat64' SSID please try to use it instead of the dual-stack 'ietf' one. You may want to modify your network preferences to ensure that 'ietf-nat64' SSID is preferred over other SSIDs (MacOS instructions can = be found at https://support.apple.com/kb/PH25285?locale=3Den_US = MS Windows instructions are available at = https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/ho= w-do-i-change-wireless-network-priority-in/17b30700-d710-44d9-abbf-74efda2= 2b039?auth=3D1 = ) If for some reason you'd prefer to use an unencrypted wireless SSID, the 'ietf-nat64-unencrypted' is an open SSID that drops you on the same L3 network segment as 'ietf-net64'. Unfortunately it is possible that some applications may have problems using the NAT64 network. If you experience issues while using the 'ietf-nat64' SSID (or 'ietf-nat64-unencrypted') please follow these instructions: - connect to the dual-stack 'ietf' (or 'ietf-legacy100') SSID. If the problem disappears open a ticket with NOC, either by using the ticketing system https://tickets.meeting.ietf.org/ = or by sending email to tickets@meeting.ietf.org . = It would really help if you could provide the following information: . Operating System and the application you are using, with version numbers . The symptoms you observed; . Any other information you believe is relevant; (if you can provide a tcpdump capture it would be really appreciated). There will be a survey sent at the end of the IETF100 week so you can share your experience/suggestions/concerns/complains/etc. Everyone who reported the broken application or filled out the survey will be entered in a drawing: USD100 will be anonymously donated to a charity of the winner's choice! (Yes, if you did both you enter twice). =E2=80=94 Again, welcome to Singapore, and have a great week! - Jim and the NOC Team = --------------------------------------------------------------------------= ----------------------------------------------------------- =3D IETF 100 Network Information =E2=80=93 Singapore, Singapore =3D =3D=3D Terminal Room =3D=3D 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 = 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 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. =3D=3D Help Desk =3D=3D A help desk is being provided and will be staffed the following hours:=20= || 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 || =3D=3D NOC and Ticketing =3D=3D There are several ways to communicate with the NOC staff.=20 * 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.=20 * 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=20 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 =3D=3D External Connectivity =3D=3D =20 The 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 both wired and wireless in the Fairmont = hotel.=20 =20 =3D=3D Meeting Room Wireless =3D=3D=20 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.=20 The main =E2=80=9Cietf=E2=80=9D wireless network is encrypted; make sure = you enter ietf for both the username and password. Here=E2=80=99s a quick summary of the network layout: || SSID || Description || Encrypted || Frequencies || IP Versions || || ietf || Our default network || yes || 5Ghz only || v4 and v6 ||=20 || ietf-legacy100 || 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 = =E2=80=9Cietf=E2=80=9D, password =E2=80=9Cietf=E2=80=9D), 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=3D137&profile=3D101 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. =3D=3D Experiments =3D=3D Experiments 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: * DNS-over-TCP (DPRIVE)=20 =3D=3D Guest Room and Public Space Access =3D=3D 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". = In the Fairmont, the wired ethernet in the guest rooms will connect you = to the IETF network. There is no wired ethernet in the Swissotel guest = rooms. **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. =20 =3D=3D Support =3D=3D If you have trouble using the guest room and public space SSID = "ietf-hotel", please contact us in the Terminal Room (Ord and Blundell = rooms) or via '''`tickets @ meeting.ietf.org`''' and we=E2=80=99ll be = glad to help! =3D=3D=3D A Note For Windows Users =3D=3D=3D 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%2= 0Wifi%20Instructions%20Windows.pdf =3D=3D Printing =3D=3D 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-P= rinter-series/5367611/drivers Printer Drivers] || =3D=3D=3D Instructions for Mac OS X using Bonjour auto-setup (DNS-Based = Service Discovery) =3D=3D=3D (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#InstructionsforMacOSXu= singmanualconfiguration 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. =3D=3D=3D Instructions for Mac OS X using manual configuration =3D=3D=3D 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 =3D=3D=3D Instructions for Windows 7=3D=3D=3D 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. =20 =3D=3D=3D Instructions for Windows using HP printing framework =3D=3D=3D 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 =3D=3D=3D 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=20 =3D=3D=3D Scanning Services =3D=3D=3D 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.=20 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 =3D=3D Services =3D=3D 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]=20 or 31.130.229.7 / [2001:67c:370:229::7] =3D=3D Geolocation =3D=3D 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). =3D=3D Thanks =3D=3D 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: * !StarHub * NTT Communications * !ViewQuest * Moratelino Volunteers: * 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=E2=80=93Madison) * Lucy Lynch * Jim Martin (INOC) * Karen O'Donoghue (ISOC) * Clemens Schrimpe=20 Staff:=20 * Rick Alfvin * Nick Kukich * Edward !McNair * Con Reilly * Brandon Height --Apple-Mail=_C91E4145-1D7D-4DAC-A9E0-09C2739928AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Gentlepeople,
Welcome = to Singapore! Below you will find the usual Network Information = documentation. As always, it=E2=80=99s a render of the wiki page the NOC = keeps at https://tickets.meeting.ietf.org/wiki/IETF100network =E2= =80=A6 please reference that as it=E2=80=99s MUCH more = readable.

This = meeting we=E2=80=99re trying very hard to help NAT64 mature enough that = it could potentially be viable as the primary way people access the = Internet. To that end, Jen Linkova (furry@google.com) and Randy Bush (randy@psg.com) have put = forth the following request:

=E2=80=94=E2=80=94
The IPv6-only SSID 'ietf-nat64' has been available at IETF = meetings for
years; but unfortunately the number of = devices using that network is
usually far lower than on = the dual-stack one.  It would be highly
desirable to = see more people using it (or to know why they can not) as
we= should eat our own dogfood.  If you have not been using the
'ietf-nat64' SSID please try to use it instead of the = dual-stack 'ietf'
one.  You may want to modify your = network preferences to ensure that
'ietf-nat64' SSID is = preferred over other SSIDs (MacOS instructions can be
found = at https://support.apple.com/kb/PH25285?locale=3Den_US

MS Windows instructions are available at
https://answers.microsoft.com/en-us/windows/forum/windows_10-ne= tworking/how-do-i-change-wireless-network-priority-in/17b30700-d710-44d9-a= bbf-74efda22b039?auth=3D1)

If for some = reason you'd prefer to use an unencrypted wireless SSID, the
'ietf-nat64-unencrypted' is an open SSID that drops you on = the same L3
network segment as 'ietf-net64'.

Unfortunately it is possible that some = applications may have problems
using the NAT64 network. =  If you experience issues while using the
'ietf-nat64' = SSID (or 'ietf-nat64-unencrypted') please follow these
instructions:

 - connect to = the dual-stack 'ietf' (or 'ietf-legacy100') SSID. If the
   problem disappears open a ticket with NOC, = either by using the
   ticketing = system https://tickets.meeting.ietf.org/ or by sending
   email to tickets@meeting.ietf.org. It would really help if you = could
   provide the following = information:
   . Operating System and the = application you are using, with version
     numbers
   . The symptoms you observed;
   . Any other information you believe is = relevant; (if you can provide
     a tcpdump capture it would be = really appreciated).

There will be a survey = sent at the end of the IETF100 week so you can
share your = experience/suggestions/concerns/complains/etc.

Everyone who reported the broken application or filled out = the survey
will be entered in a drawing: USD100 will be = anonymously donated to a
charity of the winner's choice! = (Yes, if you did both you enter twice).
=E2=80=94

Again, = welcome to Singapore, and have a great week!

- Jim and the NOC Team

---------------------------------------------------------------= ----------------------------------------------------------------------


=3D IETF 100 Network Information =E2=80=93= Singapore, Singapore =3D

=3D=3D Terminal Room =3D=3D

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 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 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.

=3D=3D = Help Desk =3D=3D
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 ||

=3D=3D = NOC and Ticketing =3D=3D

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

=3D=3D= External Connectivity =3D=3D
 
The 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 both wired and wireless in the = Fairmont hotel. 
      =  
=3D=3D Meeting Room Wireless = =3D=3D 

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 =E2=80=9Cietf=E2=80=9D wireless network is = encrypted; make sure you enter ietf for both the username and = password.

Here=E2=80=99s a quick summary of the network = layout:

|| = SSID || Description || Encrypted || Frequencies || IP Versions = ||
|| ietf  || Our default network || yes || = 5Ghz only || v4 and v6 || 
|| ietf-legacy100 = || 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 =E2=80=9Cietf=E2=80=9D, password = =E2=80=9Cietf=E2=80=9D), 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=3D137&profile=3D101

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.

=3D=3D Experiments = =3D=3D

Experiments 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:
    * = DNS-over-TCP (DPRIVE) 


=3D=3D Guest Room and = Public Space Access =3D=3D

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".  In the Fairmont, the wired ethernet in the = guest rooms will connect you to the IETF network. There is no wired = ethernet in the Swissotel guest rooms.

**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. =  

=3D=3D = Support =3D=3D

If you have trouble using the guest room and public space = SSID "ietf-hotel", please contact us in the Terminal Room (Ord and = Blundell rooms) or via '''`tickets @ meeting.ietf.org`'''  and we=E2=80=99ll be glad to = help!

=3D=3D=3D = A Note For Windows Users =3D=3D=3D

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/WindowsInforma= tion/IETF%20Wifi%20Instructions%20Windows.pdf
=3D=3D Printing =3D=3D

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-Al= l-in-One-Printer-series/5367611/drivers Printer Drivers] = ||

=3D=3D=3D = Instructions for Mac OS X using Bonjour auto-setup (DNS-Based Service = Discovery) =3D=3D=3D
(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#Instruction= sforMacOSXusingmanualconfiguration 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.

=3D=3D= =3D Instructions for Mac OS X using manual configuration =3D=3D=3D
 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

=3D=3D=3D Instructions = for Windows 7=3D=3D=3D
 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.

 
=3D=3D=3D Instructions for = Windows using HP printing framework =3D=3D=3D
 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

=3D=3D=3D 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 

=3D=3D=3D Scanning Services =3D=3D=3D
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


=3D=3D Services =3D=3D

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]

=3D=3D Geolocation =3D=3D
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).


=3D=3D Thanks =3D=3D
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:
* !StarHub
* NTT Communications
* = !ViewQuest
* Moratelino

Volunteers:
* = 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=E2=80=93Madison)
* Lucy = Lynch
* Jim Martin (INOC)
* = Karen O'Donoghue (ISOC)
* Clemens = Schrimpe 


Staff: 
* Rick Alfvin
* Nick Kukich
* Edward !McNair
* Con Reilly
* Brandon Height

= --Apple-Mail=_C91E4145-1D7D-4DAC-A9E0-09C2739928AC-- From nobody Fri Nov 10 18:17:24 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFB731200C1 for <100all@ietf.org>; Fri, 10 Nov 2017 18:17:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151036664182.32766.3957294795498077044.idtracker@ietfa.amsl.com> Date: Fri, 10 Nov 2017 18:17:21 -0800 Archived-At: Subject: [100all] Social Ticket Exchange and Refund X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2017 02:17:22 -0000 We discovered an issue with the social ticket system where, for a brief period of time, attendees successfully purchased social tickets, yet the tickets were not assigned to them in the system. This has resulted in a situation where we inadvertently sold a few more tickets than were actually available. If you have purchased a ticket for the Tuesday social event and find that you are unable to attend, please come to the registration desk. We will refund your ticket and make sure that it goes to someone who has already purchased a ticket, and who otherwise might not be able to attend. Regards, IETF Secretariat From nobody Fri Nov 10 19:43:08 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8B9124B18 for <100all@ietf.org>; Fri, 10 Nov 2017 19:43:06 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151037178686.389.164874714584324899.idtracker@ietfa.amsl.com> Date: Fri, 10 Nov 2017 19:43:06 -0800 Archived-At: Subject: [100all] Code Lounge at IETF 100 X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2017 03:43:07 -0000 Hi Everyone, In case you missed it, all attendees now have the opportunity to schedule time in the Code Lounge to continue to work on hackathon and other coding projects during the week of IETF 100: https://www.ietf.org/registration/MeetingWiki/wiki/doku.php?id=100codelounge. The Code Lounge is a portion of the IETF Lounge set aside for groups to meet informally to brainstorm, code and otherwise test out their ideas. We hope that you give it a try, and we look forward to hearing any suggestions on how it can be improved. In addition, because we know that snacking leads to better coding, we will be providing some snacks in the IETF 100 Code Lounge (Moor/Morrison room) each afternoon, Monday through Thursday. - IETF Secretariat From nobody Sun Nov 12 02:57:57 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 219F4128D44 for <100all@ietf.org>; Sun, 12 Nov 2017 02:57:55 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Agenda To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: IETF Agenda Message-ID: <151048427509.30856.4928588510399402531.idtracker@ietfa.amsl.com> Date: Sun, 12 Nov 2017 02:57:55 -0800 Archived-At: Subject: [100all] IETF 100 Final Agenda Changes X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 10:57:55 -0000 Hi Everyone! Below are changes to the final agenda. As always, the most up to date version of the agenda is online. https://datatracker.ietf.org/meeting/100/agenda.html https://datatracker.ietf.org/meeting/100/agenda.txt CANCELED: DINRG (was Mon 09:30) MTGVENUE (was Mon 17:40) TLS (was Mon 17:40) I2RS (was Mon 17:40) DMARC (was Thurs 09:30) DNSOP (was Thurs 15:50) ICE (was Thurs 15:50) CURDLE (was Thurs 18:10) ROOM CHANGE: NETMOD (Weds 1330) room change from Padang to Sophia SIDROPS (Weds 1330) room change from Sophia to Padang DAY CHANGE: TRILL moved from Thursday 1810 to Monday 17:40 in VIP A TIME CHANGE: AVTCORE was Thursday 09:30-10:30 now 09:30-11:00 LWIG Wednesday 1100-1200 NEW: INT AD Office Hours - Thursday 10:00-11:30 in Clark Thanks! IETF Secretariat From nobody Mon Nov 13 20:38:09 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABA23126C19 for <100all@ietf.org>; Mon, 13 Nov 2017 20:38:07 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ietf-secretariat@ietf.org Message-ID: <151063428765.6051.8567910680866447345.idtracker@ietfa.amsl.com> Date: Mon, 13 Nov 2017 20:38:07 -0800 Archived-At: Subject: [100all] FOUND: A phone X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 04:38:08 -0000 If you lost your phone, one has been turned in to the IETF Registration desk. If you think it might be yours, please come by the desk to claim it. From nobody Mon Nov 13 21:48:52 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F12F127078 for <100all@ietf.org>; Mon, 13 Nov 2017 21:48:51 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ietf-secretariat@ietf.org Message-ID: <151063853141.5764.3803983863371037421.idtracker@ietfa.amsl.com> Date: Mon, 13 Nov 2017 21:48:51 -0800 Archived-At: Subject: [100all] FOUND: A couple of sweaters X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 05:48:51 -0000 A couple of lightweight sweaters have been FOUND and turned in to the IETF Registration desk. If you find yourself cold because you left one behind, please come claim it at the desk. Thank you. From nobody Tue Nov 14 00:57:09 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF95124D6C for <100all@ietf.org>; Tue, 14 Nov 2017 00:57:01 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151064982131.5764.17165697439692081244.idtracker@ietfa.amsl.com> Date: Tue, 14 Nov 2017 00:57:01 -0800 Archived-At: Subject: [100all] A few more social tickets have become available! X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 08:57:01 -0000 Great news! We have a few additional social tickets available, first-come, first-served. Please come to Bailey as soon as possible if you’d like a social ticket. Credit card only, please. IETF Secretariat From nobody Tue Nov 14 01:03:43 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B42120046 for <100all@ietf.org>; Tue, 14 Nov 2017 01:03:42 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151065022251.6050.2875782153516605685.idtracker@ietfa.amsl.com> Date: Tue, 14 Nov 2017 01:03:42 -0800 Archived-At: Subject: [100all] No more social tickets X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 09:03:42 -0000 Wow, that was fast! All extra tickets have now been sold. IETF Secretariat From nobody Tue Nov 14 01:18:05 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0BE712008A for <100all@ietf.org>; Tue, 14 Nov 2017 01:18:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151065108381.6041.14837887073381622233.idtracker@ietfa.amsl.com> Date: Tue, 14 Nov 2017 01:18:03 -0800 Archived-At: Subject: [100all] Buses to Tonight's Social Event X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 09:18:04 -0000 Following are details about transportation to tonight’s social event at the S.E.A. Aquarium, sponsored by Cisco. It is a 30-minute journey from Raffles to the S.E.A. Aquarium, and the bus schedule is below. Please meet near the IETF registration desk anytime between 17:45 and 18:15. IETF Secretariat will escort groups of 45 down to the buses. Upon arrival at the event, S.E.A. Aquarium staff will take your paper ticket and give you a wristband. Please note that no entry will be allowed into the event without this wristband. Buses depart from IETF Venue: 18:00 - 18:30 All buses will arrive at the event by 19:00 NOTE: Once the final bus departs from the IETF venue attendees will need to find their own transportation to the event. Please do not arrive at IETF Registration later than 18:15. Buses return from social event: 22:00 - 23:00 NOTE: Once the final bus departs from the social event at 23:00, attendees will need to find their own return transportation. Taxi cabs from Sentosa are readily available, however there is a $5 SGD surcharge from Resort world.  If you want to take your own transportation please do not arrive at the S.E.A. Aquarium prior to18:00, as you will not be able to enter. Please ask the taxi driver to drop you off at the Coach Bay by the casino, at the address below. S.E.A. Aquarium Resorts World Sentosa 8 Sentosa Gateway, Sentosa Island From nobody Tue Nov 14 23:02:53 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 86DD212951E for <100all@ietf.org>; Tue, 14 Nov 2017 23:02:51 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.65.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151072937152.25915.9517301654022059776.idtracker@ietfa.amsl.com> Date: Tue, 14 Nov 2017 23:02:51 -0800 Archived-At: Subject: [100all] REMINDER: Thursday Speaker Series Tomorrow X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 07:02:51 -0000 Topic — 3 years on: Open Standards, Open Source, Open Loop At IETF 91, many outrageous claims were emphatically made about the relationship between Open Standards and Open Source. Three years later, let’s take a look at how much progress has been made, if any; and discuss successes and failures. Communities of developers and engineers have fully formed Open Source efforts and are building large, effective communities without any documented standardization as a part of their strategy. How should SDOs interact with developers, communities and deployers of Open Source? There are claims and perhaps proof that Open Source now fully defines the industries "de facto Standards." Does the process of standardization and the contents and lifecycle of a standard need to fundamentally change? Logistics: • Room: Canning • Date: Thursday, November 16, 2017 • Time: 12:30 – 13:15 • Lunch will NOT be provided. Speaker Biography: Dave Ward, Senior Vice President, Chief Architect & CTO - Engineering Dave is Chief Architect at Cisco Systems, responsible for architectural governance, defining strategy, development of new technology and leading use-inspired research. Working via tight partnerships with customers, partners, developers and academia he is also leading co-development and co-innovation initiatives. He has been the Routing Area Director at the IETF and chair of four Working Groups: IS-IS, HIP, BFD and Softwires and worked with the ITU-T, ONF and several Open Source consortia. David was also a Juniper Fellow and Chief Architect working on the operating system and next-generation routing systems. Dave has a small vineyard in the Santa Cruz Mountains and an heirloom tomato farm along the St. Croix River in Somerset, Wisconsin. From nobody Wed Nov 15 19:31:42 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA367124BE8 for <100all@ietf.org>; Wed, 15 Nov 2017 19:31:40 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.66.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151080310091.28393.12095562470906177372.idtracker@ietfa.amsl.com> Date: Wed, 15 Nov 2017 19:31:40 -0800 Archived-At: Subject: [100all] Reminder: Thursday Speaker Series Today During Lunch Break X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 03:31:41 -0000 Topic — 3 years on: Open Standards, Open Source, Open Loop At IETF 91, many outrageous claims were emphatically made about the relationship between Open Standards and Open Source. Three years later, let’s take a look at how much progress has been made, if any; and discuss successes and failures. Communities of developers and engineers have fully formed Open Source efforts and are building large, effective communities without any documented standardization as a part of their strategy. How should SDOs interact with developers, communities and deployers of Open Source? There are claims and perhaps proof that Open Source now fully defines the industries "de facto Standards." Does the process of standardization and the contents and lifecycle of a standard need to fundamentally change? Logistics: • Room: Canning • Date: Today, November 16, 2017 • Time: 12:30 – 13:15 • Lunch will NOT be provided. Speaker Biography: Dave Ward, Senior Vice President, Chief Architect & CTO - Engineering Dave is Chief Architect at Cisco Systems, responsible for architectural governance, defining strategy, development of new technology and leading use-inspired research. Working via tight partnerships with customers, partners, developers and academia he is also leading co-development and co-innovation initiatives. He has been the Routing Area Director at the IETF and chair of four Working Groups: IS-IS, HIP, BFD and Softwires and worked with the ITU-T, ONF and several Open Source consortia. David was also a Juniper Fellow and Chief Architect working on the operating system and next-generation routing systems. Dave has a small vineyard in the Santa Cruz Mountains and an heirloom tomato farm along the St. Croix River in Somerset, Wisconsin. From nobody Wed Nov 15 21:12:58 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAC2126B6D for <100all@ietf.org>; Wed, 15 Nov 2017 21:12:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Agenda To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.66.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: IETF Agenda Message-ID: <151080917602.28329.15295124873468622061.idtracker@ietfa.amsl.com> Date: Wed, 15 Nov 2017 21:12:56 -0800 Archived-At: Subject: [100all] IETF 100 Final Agenda Changes and Registration Desk on Friday, November 17 X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 05:12:56 -0000 Hi Everyone! Below are changes to the final agenda. As always, the most up to date version of the agenda is online. https://datatracker.ietf.org/meeting/100/agenda.html https://datatracker.ietf.org/meeting/100/agenda.txt MOVED: BABEL to Thursday 18:10 in Bras Basah (from Friday 09:30) CANCELED: GROW Friday at 11:50 Please be advised that registration desk for IETF 100 will be open from 08:30 AM to 11:00 AM on Friday, November 17th. After 11:00 AM, the Secretariat can be found in the general vicinity of the registration area, or around the Bailey Room as we pack up meeting supplies. We will also still be monitoring the trouble ticket queue at mtd@ietf.org. Blue Sheets: WG/RG/BoF Chairs, please turn your blue sheets in to the designated box in the IETF registration area, or hand them off to any Secretariat staff you find roaming the hallways. Lost & Found: We do still have a couple of unclaimed lost and found items; if you are missing anything, please stop by. Safe travels home, and we hope to see you all again in London! From nobody Wed Nov 15 22:57:04 2017 Return-Path: X-Original-To: 100all@ietfa.amsl.com Delivered-To: 100all@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7EC512956D for <100all@ietfa.amsl.com>; Wed, 15 Nov 2017 22:56:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O79HiLDh0E8 for <100all@ietfa.amsl.com>; Wed, 15 Nov 2017 22:56:51 -0800 (PST) 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 81BDA1294B3 for <100all@ietf.org>; Wed, 15 Nov 2017 22:56:51 -0800 (PST) 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 7149B88136 for <100all@ietf.org>; Wed, 15 Nov 2017 22:56:51 -0800 (PST) Received: from [IPv6:2001:67c:370::ace9:99fd:1749:e7fa] (unknown [IPv6:2001:67c:370:0:ace9:99fd:1749:e7fa]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id C75C61308395 for <100all@ietf.org>; Wed, 15 Nov 2017 22:56:50 -0800 (PST) From: Jim Martin Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Reply-To: 100attendees@ietf.org Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.18\)) Message-Id: Date: Thu, 16 Nov 2017 14:56:43 +0800 To: 100all@ietf.org X-Mailer: Apple Mail (2.3445.5.18) Archived-At: Subject: [100all] IETF 100 Network Shutdown Schedule X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 06:56:53 -0000 Gentlepeople, As the meeting comes to a close, we wanted to update everyone on = the shutdown schedule for the IETF Network. The wireless APs that = deliver the main IETF networks in the Raffles City Convention Center = meeting rooms will be removed throughout the day tomorrow as sessions = come to a close. The Terminal Room which originally was scheduled to = close at 3pm tomorrow will be closed as of 1pm, as the only afternoon = working group meeting has been cancelled.=20 As there is an ISOC meeting this weekend following the IETF, = we=E2=80=99re able to keep the =E2=80=9Cietf-hotel=E2=80=9D wireless = SSID active through Sunday, though on a best-effort basis due to very = limited staff. However, the wired guest room Internet in the Fairmont = will revert to the traditional hotel network as of 12 Noon tomorrow. Let me thank Cisco, Juniper and A10 again for their = contributions of equipment, and NTT, StarHub, Moratel and ViewQwest for = the Internet circuits.=20 We hope you all have a good trip home and look forward to seeing = everyone in London! - Jim and the NOC Team= From nobody Thu Nov 16 19:03:23 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E5ECA124D68 for <100all@ietf.org>; Thu, 16 Nov 2017 19:02:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.66.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ietf@ietf.org Message-ID: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com> Date: Thu, 16 Nov 2017 19:02:21 -0800 Archived-At: X-Mailman-Approved-At: Thu, 16 Nov 2017 19:03:22 -0800 Subject: [100all] Very Few T-shirts Left X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 03:02:22 -0000 But if you want one there are a very few 3XL size t-shirts available. First come first served. Again, 3XL only. From nobody Thu Nov 16 22:02:21 2017 Return-Path: X-Original-To: 100all@ietfa.amsl.com Delivered-To: 100all@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975A7120227 for <100all@ietfa.amsl.com>; Thu, 16 Nov 2017 22:02:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 UufXhw9oxmdH for <100all@ietfa.amsl.com>; Thu, 16 Nov 2017 22:02:18 -0800 (PST) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47F3112785F for <100all@ietf.org>; Thu, 16 Nov 2017 22:02:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 37C621CAC42; Thu, 16 Nov 2017 22:01:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axp-KuanU9zt; Thu, 16 Nov 2017 22:01:38 -0800 (PST) Received: from [IPv6:2001:67c:370:236:e07c:968a:f787:ec31] (unknown [IPv6:2001:67c:370:236:e07c:968a:f787:ec31]) by c8a.amsl.com (Postfix) with ESMTPSA id 5FF2A1CAC41; Thu, 16 Nov 2017 22:01:37 -0800 (PST) From: Alexa Morris Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_30F560AB-2994-44B5-9407-1F5D5D18F1D2" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Fri, 17 Nov 2017 14:03:42 +0800 In-Reply-To: <19524.1510882008@obiwan.sandelman.ca> Cc: Jodi Haasz , 100all@ietf.org To: Michael Richardson References: <151080310091.28393.12095562470906177372.idtracker@ietfa.amsl.com> <5244163065687355257@unknownmsgid> <19524.1510882008@obiwan.sandelman.ca> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [100all] [100attendees] Reminder: Thursday Speaker Series Today During Lunch Break X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 06:02:19 -0000 --Apple-Mail=_30F560AB-2994-44B5-9407-1F5D5D18F1D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii The slides were posted to the Datatracker yesterday: = https://datatracker.ietf.org/meeting/100/materials/slides-100-edu-sessa-3-= years-on-open-standards-open-source-open-loop/ = . Alexa > On Nov 17, 2017, at 9:26 AM, Michael Richardson = wrote: >=20 >=20 > Jodi Haasz wrote: >> Will the slides shown today be made available? >=20 > It's already also on youtube: = https://www.youtube.com/watch?v=3DOlG556CuT7g >=20 > -- > Michael Richardson , Sandelman Software Works > -=3D IPv6 IoT consulting =3D- >=20 >=20 >=20 > _______________________________________________ > 100attendees mailing list > 100attendees@ietf.org > https://www.ietf.org/mailman/listinfo/100attendees --Apple-Mail=_30F560AB-2994-44B5-9407-1F5D5D18F1D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii The slides were posted to the Datatracker yesterday: https://datatracker.ietf.org/meeting/100/materials/slides-100-e= du-sessa-3-years-on-open-standards-open-source-open-loop/.

Alexa


On = Nov 17, 2017, at 9:26 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:


Jodi Haasz <j.haasz@ieee.org> wrote:
Will the slides shown today be made = available?

It's already also = on youtube:   https://www.youtube.com/watch?v=3DOlG556CuT7g

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-=3D IPv6 IoT consulting =3D-


_______________________________________________
100attendees mailing list
100attendees@ietf.org
https://www.ietf.org/mailman/listinfo/100attendees

= --Apple-Mail=_30F560AB-2994-44B5-9407-1F5D5D18F1D2-- From nobody Thu Nov 16 22:41:40 2017 Return-Path: X-Original-To: 100all@ietf.org Delivered-To: 100all@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D52F1200C1 for <100all@ietf.org>; Thu, 16 Nov 2017 22:41:39 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Secretariat To: <100all@ietf.org> X-Test-IDTracker: no X-IETF-IDTracker: 6.66.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: 100attendees@ietf.org Message-ID: <151090089920.22140.6543606435648779700.idtracker@ietfa.amsl.com> Date: Thu, 16 Nov 2017 22:41:39 -0800 Archived-At: Subject: [100all] Tutorials at IETF 100: please provide feedback X-BeenThere: 100all@ietf.org X-Mailman-Version: 2.1.22 List-Id: <100all.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 06:41:39 -0000 If you attended any of the tutorials held this past Sunday, please take a few moments to complete the appropriate survey(s). Your input will be used to improve future tutorials. - Newcomers Orientation, presented by Michael StJohns: https://www.surveymonkey.com/r/100newcomers - Transport Layer Security (TLS) 1.3 Tutorial, presented by Sean Turner and Joseph Salowey: https://www.surveymonkey.com/r/100tls - WebRTC Tutorial, presented by Dan Burnett and "Dr. Alex” Gouaillard: https://www.surveymonkey.com/r/100webrtc - Routing Area Tutorial, presented by Joel Halpern and Sue Hares: https://www.surveymonkey.com/r/100routing