doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 1 IEEE IETF Liaison Report Date: Authors:

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 2 Abstract This presentation contains the IEEE – IETF liaison report for July 2013.

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 3 IETF- IEEE 802 Liaison Activity - 1 Joint Meetings, agenda and presentations: Telecon Meeting held 17 June 2013 – –No new items

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 4 IETF- IEEE 802 Liaison Activity - 2 RFC4441bis update, see –Includes resolutions to collected IEEE comments in comments-cc6.xlsx comments-cc6.xlsx –No revision since May meeting (IETF editor change) Status of IEEE review of RFC4441rev-04 –IEEE WG has completed review of RFC4441rev-04, and –The identified comment will be forwarded to the IETF/IEEE 802 RFC4441bis editing team

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 5 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 link and list now available – –

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 6 IETF Meetings Meetings: –July 28 – August 2, 2013 – Berlin –November 3-8, 2013 – Vancouver –March 2-5, 2014 – London –July 20-25, 2014 – Toronto –November 9-14, Honolulu –Newcomer training: tutorials.html#newcomershttps:// tutorials.html#newcomers –Tutorials (process and technical); 802.1Q tutorial presented last week:

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 7 IETF Berlin Meeting BOFs Stacked Tunnels for Source Routing BOF Network Service Chaining Proposed Update IPR Policy BOF PKIX over Secure HTTP BOF Secure Telephone Identity Revisited BOFSecure Telephone Identity Revisited Deterministic IPv6 over IEEE e Timeslotted Channel Hopping BOF Domain-based Message Authentication, Reporting & Conformance BOFDomain-based Message Authentication, Reporting & Conformance Active Queue Management and Packet Scheduling BOFActive Queue Management and Packet Scheduling DNS-SD Extensions BOFDNS-SD Extensions DTLS In Constrained Environments BOF Tunneling Compressed Multiplexed Traffic Flows BOFTunneling Compressed Multiplexed Traffic Flows See

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 8 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 [July 2013] –Of interest: RADIUS Attributes for IEEE 802 Networks, see

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 9 Protocol to Access White Space database (paws) WG paws Working Group was formed June 2011, see Charter and problem statement documents: –Charter, see –Problem Statement, see Goals and Milestones –Aug Submit 'Use Cases and Requirements for Accessing a Radio White Space Database' to the IESG for publication as Informational –April Submit 'Accessing a Radio White Space Database' to the IESG for publication as Proposed Standard Updates [July 2013] –Updated Use Cases and requirements, published as RFC 6953: –Updated: Paws protocol draft document: –Potential future request for P802.11af draft

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 10 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 Updates [July 2013]: –Tunnel EAP Method (TEAP) Version tunnel-method/ - New version posted. Last call ends tunnel-method/ –Updated: EAP Mutual Cryptographic Binding, see crypto-bind/. Introduces a new form of cryptographic binding that protects both peer and server, rather than just the server. Last call ends crypto-bind/

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 11 Public-Key Infrastructure (X.509) (pkix) Working Group website: –Develops Internet standards to support X.509-based Public Key Infrastructures (PKIs). RFC Documents - published –Numerous – see website Updates [July 2013]: –Of interest for enrollment of devices into a certificate infrastructure: Updated: Enrollment over Secure Transport, IESG review: –Working Group will close shortly

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 12 IETF Geographic Location and Privacy (Geopriv) WG See Specific reference to WLANs: –Carrying Location Objects in RADIUS, 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 [July 2013] –Relative Location, see location/ draft updated; area director follow-uphttp://datatracker.ietf.org/doc/draft-ietf-geopriv-relative- location/ –Group will close soon.

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 13 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 [July 2013] –Updated: Public Safety Answering Point (PSAP) Callback ietf-ecrit-psap-callback/ ietf-ecrit-psap-callback/ –Updated: Unauthorized access, see unauthenticated-access/ unauthenticated-access/ –Updated: Additional Data related to an emergency call, see ietf-ecrit-additional-data/ ietf-ecrit-additional-data/

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 14 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 [July 2013] Documents of interest: –Grazed and Lightweight Open Protocol, see homenet-galop-proto/ homenet-galop-proto/ –Home networking Architecture for IPv6, see arch/ - in Working Group last Callhttps://datatracker.ietf.org/doc/draft-ietf-homenet- arch/ –Connecting Home Networks via the social network GooglePlus, see

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 15 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 Recently, individual submissions related to the CAPWAP protocol and extensions were submitted – Operations Area Working Group has agreed to accept the first 2 as work group items

doc.: IEEE /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 16 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 /0862r0 Submission July 2013 Dorothy Stanley, Aruba NetworksSlide 17 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