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

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

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 3 Follow-up from IETF- IEEE 802 Liaison Activity Joint IETF/IEEE 802 Meeting held 25 July 2012 –Agenda is here: –Notes and meeting materials available here: Teleconference meetings –5 Sept notes, including action items –29 Oct 2012 –17 Dec 2012 –Next: 12 Feb 2013 IEEE items –RFC4441bis update, see (posted) and revision in progress; comments welcomehttp:// –Description of new Trill related area of mutual interest: “Area Name - use of TRILL as an alternative path selection protocol for use in mesh networks” –List of topic areas of mutual interest:

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 4 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:

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 5 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 [January 2013] –Of interest: RADIUS Attributes for IEEE 802 Networks, see –Additional comments provided based on Nov discussion in ARC, see archive/web/radext/current/msg07916.html, in addition to archive/web/radext/current/msg07864.htmlhttp:// archive/web/radext/current/msg07916.htmlhttp:// archive/web/radext/current/msg07864.html

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 6 Diffie-Hellman Group Repository Liaison Request Liaison request from July 2012 meeting –See repository.dochttps://mentor.ieee.org/802.11/dcn/12/ liaison-to-ietf-group- repository.doc –Liaison was discussed at IETF July Vancouver meeting, at Security Area Directorate –Agreed way forward Registry update by IANA is “RFC required” RFC being written to define requested updates Updates [January 2013] –IKE Group Registry update RFC – Draft available: –Currently in IETF last call (Sponsor Ballot equivalent) –Expect document approval early 2013

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 7 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 [January 2013] –Updated Use Cases and requirements, see stmt-usecases-rqmts/ stmt-usecases-rqmts/ –New: Paws protocol draft document: –Security Considerations, see

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 8 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 [January 2013]: –New: 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. crypto-bind/ –Tunnel EAP Method (TEAP) Version tunnel-method/ - In Working Group Last Call (analogous to Working Group Letter Ballot) tunnel-method/

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 9 New: 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 [January 2013]: –Of interest for enrollment of devices into a certificate infrastructure: Updated: Enrollment over Secure Transport:

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 10 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 [January 2013] –Relative Location, see location/ draft to be submitted for publicationhttp://datatracker.ietf.org/doc/draft-ietf-geopriv-relative- location/ –No meeting at March IETF.

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 11 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 [January 2013] –Updated: Public Safety Answering Point (PSAP) Callback ietf-ecrit-psap-callback/ ietf-ecrit-psap-callback/ –Updated: Policy for defining new service-identifying lables, see

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 12 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 [January 2013] Documents of interest: –Home networking Architecture for IPv6, see arch/ arch/ –IPv6 Home Network Front End Naming Delegation, see mglt-homenet-front-end-naming-delegation/ mglt-homenet-front-end-naming-delegation/ –Secret Gardens are Better than Walled Gardens, see richardson-homenet-secret-gardens/ richardson-homenet-secret-gardens/ –BRDP for homenet, see gardens/ gardens/ –Bootstrapping trust on a Homenet, see trust-bootstrap/ trust-bootstrap/ –Grazed and Lightweight Open Protocol, see homenet-galop-proto/ homenet-galop-proto/ –Extended Multicast DNS:

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 13 Dynamic Host Configuration (dhc) WG See The DHC WG is responsible for reviewing DHCP options or other extensions (for both IPv4 and IPv6). –The DHC WG is expected to review all proposed extensions to DHCP to ensure that they are consistent with the DHCP specification and other option formats, that they do not duplicate existing mechanisms, etc. –Generally speaking, the DHC WG will not be responsible for evaluating the semantic content of proposed options. Similarly, the ownership of specifications typically belongs the relevant working group that needs more functionality from DHCP, not the DHC WG. The DHC WG coordinates reviews of the proposed options together with those working groups. It is required that those working groups have consensus to take on the work and that the work is within their charter. Exceptionally, with AD agreement, this same process can also be used for Individual Submissions originating outside WGs. Updates [January 2013] –Of interest: also –New: –New:

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 14 6LOWPAN Working Group Working Group website: Focus: IPv6 over Low Power PAN: Adaption of IPv6 protocol to operate on constrained nodes and link layers –RFC 4944: adaption of IPv6 to link layer –Improved header compression scheme, see –RFC 6282, “Compression Format for IPv6 Datagrams over IEEE Based Networks” published, see –Design and Application Spaces (Use Cases), see 6lowpan-usecases/ 6lowpan-usecases/ –RFC 6066 “Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing” see –RFC “Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)”, see Updates [January 2013] –New: –Of interest: 6LoWPAN Roadmap and Implementation Guide

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 15 ROLL Working Group Working Group website: Focus: Routing over Low Power and Lossy Networks –Routing Objectives, see –Routing protocol for efficient operation in low-power, lossy networks, see –RFC 6719, “The Minimum Rank with Hysteresis Objective Function“, see Updates [January 2013] –Of Interest: A Security Threat Analysis for Routing over Low Power and Lossy Networks, see –Updated: A Mechanism to Measure the Quality of a Point-to-point Route in a Low Power and Lossy Network, see –Updated: Reactive Discovery of Point-to-Point Routes in Low Power and Lossy Networks, see –Of Interest: Lightweight Key Establishment and Management Protocol in Dynamic Sensor Networks (KEMP), see

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 16 CORE Working Group CORE ( Constrained RESTful Environments) Working Group website: Focus: framework for resource-oriented applications intended to run on constrained IP networks. –Constrained networks can occur as part of home and building automation, energy management, and the Internet of Things. –RFC 6690, Constrained RESTful Environments (CoRE) Link Format, see Updates [January 2013] –Updated: Constrained Application Protocol, see coap/ coap/ –Updated: Group Communication for CoAP:, see groupcomm/ groupcomm/ –Of Interest: Blockwise transfers in CoAP, see block/ block/ –Of interest: Security Bootstrapping of Resource-Constrained Devices, see

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 17 IETF Meetings Meetings: –March 10-15, 2013 – Orlando –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

doc.: IEEE /0097r0 Submission January 2013 Dorothy Stanley, Aruba NetworksSlide 18 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