doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 1 IEEE IETF Liaison Report Date: Authors:

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 2 Abstract This presentation contains the IEEE – IETF liaison report for March 2014.

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 3 IETF- IEEE 802 Liaison Activity - 1 Joint Meetings, agenda and presentations: Telecon Meeting held 27 Jan 2014 – see ieee802-minutes.txthttp:// ieee802-minutes.txt –No new IEEE items Next joint IEEE 802/IETF IESG coordination meeting: Week June 16 th, 2014 Next face to face meeting: 29 Sept 2014

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 4 IETF- IEEE 802 Liaison Activity - 2 RFC4441bis update, see 08.txthttp:// 08.txt –Nearing completion IEEE Comment Collection held on PAWS document – no comments received Request received from OPSAWG (next 2 slides) New “IETF/IAB/IESG..” 802 EC Standing Committee being considered – Pat Thaler; structure, scope under discussion

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 5 Alternate Tunnel Liaison request From: Warren Kumari Sent: Friday, March 07, :14 AM To: Cc: Dorothy Stanley; Dan Romascanu; Benoit Claise; joel jaeggli; Subject: Alternate Tunnel Encapsulation for Data Frames in CAPWAP. The charter of the IETF Operations Area Working Group (OPSAWG) covers new work as well as work that once belonged in IETF Operations Area WGs that have concluded. One of these Working Groups is Control And Provisioning of Wireless Access Points (CAPWAP) Working Group that developed the CAPWAP protocol with advice and reviews from IEEE At the OPSAWG meeting held in London on 3/4/2014 a proposal for an '"Alternate Tunnel Encapsulation for Data Frames in CAPWAP'" zhang-opsawg-capwap-cds-02.txt was submitted for consideration as a new OPSAWG work item. zhang-opsawg-capwap-cds-02.txt The WG agreed that there is interest in proceeding with this work, but before approving it as WG item would like feedback on whether IEEE sees any architectural or technical problems with the approach proposed by this work. We would be grateful if you can review this work-in-progress document and let us know if you detect any potential problems. If possible we would like to receive your response before April 11, We appreciate your continuous support and expert advice for the work done in the IETF. Yours, Melinda Shore, Scott Bradner, Warren Kumari.

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 6 Liaison draft response From: Bruce Kraemer To: Warren Kumari Melinda Shore, Scott Cc: Dorothy Stanley; Dan Romascanu; Benoit Claise; joel jaeggli; Subject: Alternate Tunnel Encapsulation for Data Frames in CAPWAP Thank you for the opportunity to review the "Alternate Tunnel Encapsulation for Data Frames in CAPWAP'" document. The AlternateTunnel Encapsulation draft addresses possible architecture implementations of the IEEE Distribution System (DS). Implementation architectures of the DS are outside the scope of the IEEE standard. Thank you, Bruce Kraemer Chair, IEEE

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 7 Protocol to Access White Space database (paws) WG Received request for IEEE review of paws protocol draft document: Held IEEE Call for Comments –No comments received Paws Charter and problem statement documents: –Charter, see –Problem Statement, see –Updated Use Cases and requirements, published as RFC 6953:

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 8 About RFC 4441 & IETF liaisons Reference document: RFC 4441 –2006 document, but still relevant: “The IEEE 802/IETF Relationship”, see –Liaison info: IETF has a liaison manager FROM IETF to IEEE SA and IEEE 802.1, not to The IETF has a limited number of liaison relationships with other organizations. Liaisons are appointed by the IAB when the IAB feels that conditions warrant appointing a specific person to such a task. Note that such appointments are rare as the best way for organizations to work with the IETF is to do so within the working groups –Liaison statements are here: IEEE 802 Liaisons list is available –

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 9 IETF Meetings Meetings: –March 2-5, 2014 – London –July 20-25, 2014 – Toronto –November 9-14, 2014 – Honolulu –March 22-27, 2015 – Dallas –July 19-24, 2015 – Prague –November 1-6, Yokahama –Newcomer training: tutorials.html#newcomershttps:// tutorials.html#newcomers –Tutorials (process and technical); Wireless Tutorial (Donald Eastlake) :

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 10 BOF Sessions – March 2014 See Authentication and Authorization for Constrained Environments (ACE) Domain Boundaries (DBound) non-ASCII characters in RFCs and other format updates (rfcform) DMSe - Encryption of DNS requests for confidentiality Internet Governance Update (igovupdate) Host Identification, Address and Prefix Sharing in Wi-Fi Access (HIAPS) Transparency (Taps) Transport (trans) TURN revised and Modernized (Tram) Virtualized Network Function Pool (VNFPool) Traversal Using Relays around NAT (TURN) Revised and Modernized (TRAM) Tunneling Compressed Multiplexed Traffic Flows (TCMTF)

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 11 New item - STRINT Strengthening the Internet Against Pervasive Monitoring STRINT workshop page, where you will find the materials (presentations and position papers): STRINT workshop summary (errata: should be IAB/W3C, and not IETF/W3C): workshop-summary.pptxhttps://mentor.ieee.org/802-ec/dcn/14/ec EC-strint- workshop-summary.pptx

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 12 RADEXT WG See RADIUS Extensions –The RADIUS Extensions Working Group will focus on extensions to the RADIUS protocol required to define extensions to the standard attribute space as well as to address cryptographic algorithm agility and use over new transports. –In addition, RADEXT will work on RADIUS Design Guidelines and define new attributes for particular applications of authentication, authorization and accounting such as NAS management and local area network (LAN) usage. Updates [March 2014] –Submitted for publication: RADIUS Attributes for IEEE 802 Networks, see

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 13 EAP Method Update (EMU) Working Group website: RFC Documents - published –The EAP-TLS Authentication Protocol - –Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) Method- –Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods –Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method –EAP Mutual Cryptographic Binding: Introduces a new form of cryptographic binding that protects both peer and server, rather than just the server. Published as Updates [March 2014]: –Tunnel EAP Method (TEAP) in RFC editor queue: emu-eap-tunnel-method/ emu-eap-tunnel-method/

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 14 IETF Geographic Location and Privacy (Geopriv) WG See Specific reference to WLANs: –Carrying Location Objects in RADIUS, see –Relative Location, published as RFC 7035, see Documents referenced in (TGv) –Geopriv Requirements, see –Civic Address definitions, see July 2009 Liaison to IETF GEOPRIV –See ietf-geopriv.dochttps://mentor.ieee.org/802.11/dcn/09/ v-liaison-request-to- ietf-geopriv.doc Updates [March 2014] –Using Device-provided Location-Related Measurements in Location Configuration Protocols, Published as RFC 7105, –Updated: Location Information Server Discovery using IP address and reverse DNS, see

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 15 Emergency Context Resolution with Internet Technologies (ECRIT) Working Group website: charter.htmlhttp:// charter.html Emergency Services –Framework for Emergency Calling using Internet Multimedia, see –Describing boundaries for Civic Addresses, see thomson-ecrit-civic-boundary-02.txthttp://tools.ietf.org/id/draft- thomson-ecrit-civic-boundary-02.txt Updates [March 2014] –Updated: Additional Data related to an emergency call, see ietf-ecrit-additional-data/ ietf-ecrit-additional-data/ –Updated: Trustworthy Location, see location/ location/ –Of interest: Unauthorized access, see unauthenticated-access/ in IESG reviewhttp://datatracker.ietf.org/doc/draft-ietf-ecrit- unauthenticated-access/ –Of interest: Internet Protocol-based In-Vehicle Emergency Calls, see

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 16 Home Networking (homenet) WG See This working group focuses on the evolving networking technology within and among relatively small "residential home" networks –The task of the group is to produce an architecture document that outlines how to construct home networks involving multiple routers and subnets. –This document is expected to apply the IPv6 addressing architecture, prefix delegation, global and ULA addresses, source address selection rules and other existing components of the IPv6 architecture, as appropriate. Updates [March 2014] Documents of interest: –Updated: Home networking Architecture for IPv6, see homenet-arch/ - submitted for publicationhttps://datatracker.ietf.org/doc/draft-ietf- homenet-arch/

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 17 Operations Area Working Group –Area WG processes submissions related to Operations Area WGs that have closed –Control and Provisioning of Wireless Access Points (CAPWAP) Working Group closed in 2009 Operations Area Working Group work group items – – Have a request from OPSAWG chairs for IEEE review of additional document –“Alternate Tunnel Encapsulation for Data Frames in CAPWAP” zhang-opsawg-capwap-cds-02.txthttp:// zhang-opsawg-capwap-cds-02.txt

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 18 Of Interest to Smart Grid 6LOWPAN –Working Group website: –Focus: IPv6 over Low Power PAN: Adaption of IPv6 protocol to operate on constrained nodes and link layers ROLL –Working Group website: –Focus: Routing over Low Power and Lossy Networks CORE –(Constrained RESTful Environments) Working Group website: –Focus: framework for resource-oriented applications intended to run on constrained IP networks.

doc.: IEEE /0368r0 Submission March 2014 Dorothy Stanley, Aruba NetworksSlide 19 References RFC IEEE Requirements on EAP Methods Jan 2012 report (PAWS, Homenet details), january-2012-liaison-to-ietf.ppt january-2012-liaison-to-ietf.ppt