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

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

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 3 IETF- IEEE 802 Liaison Activity Joint Meetings, agenda and presentations: Telecon Meeting held 2 May – –Dual use registry item closed –New tracking item for 6tsch, see – coordination needed with Layer 2 Routing (Mesh Under Routing) study grouphttps:// –New tracking item for capwap extensions in Operations area working group RFC4441bis –RFC4441bis update, see –Includes resolutions to IEEE comments submitted to date. –Still opportunity to provide comments; Review any additional contributions in ARC session (Weds AM)

doc.: IEEE /0569r0 Submission May 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: IEEE 802 Liaisons link and list now available – –

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

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 7 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 [May 2013] –IKE Group Registry update RFC – brainpool-ike-groups/ brainpool-ike-groups/ –Document approved; RFC 6932 awaiting publication –The curves have been assigned values in the IANA registry: Value 27 for the 224-bit curve, Value 28 for the 256-bit curve, Value 29 for the 384-bit curve, and Value 30 for the 512-bit curve

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 8 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 [May 2013] –Updated Use Cases and requirements, see stmt-usecases-rqmts/ - in RFC Editor Queuehttp://datatracker.ietf.org/doc/draft-ietf-paws-problem- stmt-usecases-rqmts/ –Updated: Paws protocol draft document: –Potential future request for P802.11af draft

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

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 10 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 [May 2013]: –Of interest for enrollment of devices into a certificate infrastructure: Updated: Enrollment over Secure Transport: –X.509 Internet Public Key Infrastructure Online Certificate Status Protocol – OCSP –Working Group will close shortly

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 11 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 [May 2013] –Relative Location, see location/ draft updated and waiting for area directorhttp://datatracker.ietf.org/doc/draft-ietf-geopriv-relative- location/ –Group will close soon.

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 12 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 [May 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 /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 13 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 [May 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/

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 14 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 [May 2013] –Of interest: also –Updated: Access Network Identifier, see access-network-identifier/ access-network-identifier/

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 15 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 [May 2013] –Submitted for publication: Transmission of IPv6 Packets over BLUETOOTH Low Energy: –Updated: –Of interest: 6LoWPAN Roadmap and Implementation Guide

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 16 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 [May 2013] –Of Interest: A Security Threat Analysis for Routing over Low Power and Lossy Networks, see - In IESG Evaluation –Of Interest: Lightweight Key Establishment and Management Protocol in Dynamic Sensor Networks (KEMP), see –New: Applicability Statement: The use of the RPL protocol set in Home Automation and Building Control, see

doc.: IEEE /0569r0 Submission May 2013 Dorothy Stanley, Aruba NetworksSlide 17 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 [May 2013] –Updated: Constrained Application Protocol, see coap/ Submitted to IESGhttp://datatracker.ietf.org/doc/draft-ietf-core- coap/ –Updated: CoRE Roadmap and Implementation Guide, see bormann-core-roadmap/ bormann-core-roadmap/ –Of interest: Security Bootstrapping of Resource-Constrained Devices, see –Of interest: Security Considerations in the IP-based Internet of Things:

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