doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 1 IEEE IETF Liaison Report Date: Authors:

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 2 Abstract This presentation contains the IEEE – IETF liaison report for September 2012.

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 3 Recall Recent Liaison Activity (May) Liaison – iesg-liaison-to-iesg-from-ieee-8021-attachment-1.pdfhttps://datatracker.ietf.org/documents/LIAISON/liaison ieee-8021-the- iesg-liaison-to-iesg-from-ieee-8021-attachment-1.pdf IETF Response: May 10, 2012 – –Thank you for your liaison letter dated 3/19/2012. –We share your desire for the IETF and the IEEE 802 (and the IEEE in particular) to work together in order to avoid the creation and proliferation of multiple solutions to the same problems. –We agree on the need for concerted efforts that will ensure that the technologies developed by the two organizations interoperate with each other and are operated and controlled in a consistent manner. –We appreciate your sharing the list of projects completed in the last two years, the ones in progress, and the new proposals in IEEE – In response to your request to list the work items in the IETF that are proposed or underway that relate to MAC networks together with a brief description of the problems these are addressing, –IETF Work areas listed include all relevant 802 (not just 802.1)

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 4 Follow-up from Liaison Activity Joint IETF/IEEE 802 Meeting held 25 July 2012 –Agenda is here: –Jon Rosdahl (head of delegation), Dorothy Stanley, Dave Halasz, Mark Hamilton, Gabor Bajko, Andrew Myles, Donald Eastlake –Notes and meeting materials available here: Teleconference meeting held 5 Sept 2012 –Notes Teleconference planned 29 Oct 2012

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 5 Action Items – Initial Meeting From Spencer Dawkins, Eric Gray, Dan Romascanu, Dorothy Stanley and Pat Thaler agreed to work on an update to RFC Howard Frazier and Dan Romascanu agreed to write an Informational RFC that will document the MIB transfer process. The IEEE 802 agreed to review and update the people they currently have subscribed to the new-work mailing list, and to send PARs to new-work. The IEEE 802 agreed to add a page to their website listing their current liaison relationships. The IEEE 802 will look at removing mailing list restrictions that prevent IETF participants from contributing to IEEE 802 work. The IESG agreed to draft an IESG Statement regarding Ethertype Requests. The IAB and IESG will suggest a process for providing feedback to the IEEE RAC on Virtualization and OUI Tiers.

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 6 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 /1142r0 Submission September2012 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 Target completion Nov 2012

doc.: IEEE /1142r0 Submission September2012 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 [dated updated] –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 [Sept 2012] –Updated Use Cases and requirements, see stmt-usecases-rqmts/ stmt-usecases-rqmts/ –Updated drafts: and –Framework document, see –Security Considerations, see

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 9 Handover Keying (HOKEY) Hokey Charter available at –Extensions to current EAP key framework to facilitate inter-authenticator handover and roaming. Published RFCs: –Handover Key Management and Re-authentication Problem Statement, see –Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK), see –EAP Extensions for EAP Re-authentication Protocol (ERP), see –Distribution of EAP based keys for handover and re-authentication, see [published March 2010] –Extensible Authentication Protocol (EAP) Early Authentication Problem Statement, see [published April 2010] Updates [Sept 2012] –Did not meet at July 2012 IETF –WG closed

doc.: IEEE /1142r0 Submission September2012 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 [Sept 2012]: –Tunnel EAP Method (TEAP) Version tunnel-method/ tunnel-method/ –An EAP Authentication Method Based on Identity-Based Authenticated Key Exchange -

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 11 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 Updates [Sept 2012] –Revision available: Transmission of IPv6 packets over Bluetooth Low Energy, see –Revision available: Neighbor Discovery Optimization, see ietf-6lowpan-nd/ ietf-6lowpan-nd/ –Of interest: Lightweight Secure Neighbor Discovery for Low-power and Lossy Networks, see –New: 6LoWPAN Roadmap and Implementation Guide bormann-6lowpan-roadmap/ bormann-6lowpan-roadmap/

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 12 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 Updates [Sept 2012] –Updated: A Mechanism to Measure the Quality of a Point-to-point Route in a Low Power and Lossy Network, see –Updated: Recommendations for Efficient Implementation of RPL: –Of Interest: Applicability of ROLL in AMI Networks, see ietf-roll-applicability-ami/ ietf-roll-applicability-ami/ –Of Interest: Lightweight Key Establishment and Management Protocol in Dynamic Sensor Networks (KEMP), see –Of Interest: A Security Framework for Routing over Low Power and Lossy Networks, see

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 13 CORE Working Group CORE ( Constrained RESTful Environments) Working Group website: Focus: framework for resource-oriented applications intended to run on constrained IP networks –Constrained Application Protocol, see coap/ coap/ Updates [Sept 2012] –Updated: Constrained Application Protocol, see coap/ coap/ –Of Interest: Security Considerations in IP based Internet of Things, see –Updated: Security Bootstrapping of Resource-Constrained Devices, see

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 14 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 [Sept 2012] –Updated: Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements, see –Updated: Internet Protocol-based In-Vehicle Emergency Call, see –Updated: Additional data related to an emergency call, see ietf-ecrit-additional-data/ ietf-ecrit-additional-data/ –Updated: Using Imprecise location, see –Of interest: Out of Jurisdiction Emergency Routing, see winterbottom-ecrit-priv-loc/ winterbottom-ecrit-priv-loc/ –Of interest: Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices, see unauthenticated-access/ unauthenticated-access/

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 15 IETF Geographic Location and Privacy (Geopriv) WG See Specific reference to WLANs: –Carrying Location Objects in RADIUS, see geopriv-radius-lo-08.txthttp:// geopriv-radius-lo-08.txt Documents referenced in (TGv) –Geopriv Requirements, see –Civic Address definitions, see July 2009 Liaison to IETF GEOPRIV –See geopriv.dochttps://mentor.ieee.org/802.11/dcn/09/ v-liaison-request-to-ietf- geopriv.doc Updates [July 2012] –Of Interest: Location Configuration Extensions for Policy Management, see –Updated: Relative Location, see location/ location/ –Updated: A Location Dereferencing Protocol using HELD, see –Updated: Using Device-provided Location-Related Measurements in Location Configuration Protocols, see –Of Interest: Relative Location Representation, see geopriv-relative-location/ geopriv-relative-location/

doc.: IEEE /1142r0 Submission September2012 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 [Sept 2012] –Updated: Home networking Architecture for IPv6, see homenet-arch/ homenet-arch/ –Updated: IPv6 Prefix Assignment in Small Networks, baker-homenet-prefix-assignment/ baker-homenet-prefix-assignment/ –Of Interest: Grazed and Lightweight Open Protocol, see ruminski-homenet-galop-proto/ ruminski-homenet-galop-proto/ The main goal for the protocol is to provide fast and reliable communication between mobile devices (client software) and Personal Computer (server software) via Bluetooth with minimal data size needed to realize full functionality of the project. The protocol was designed to be easy to extend - adding new features and developing clients for other mobile platforms should be as easy as possible. –Of Interest: Minimum Requirements for Physical Layout of Home Networks, –Of Interest: Extended Multicast DNS: mdns/ mdns/

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 17 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 [September 2012] –Of interest:

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 18 New: 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 [September 2012] –Of interest: RADIUS Attributes for IEEE 802 Networks, see

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 19 IETF Meetings Meetings: –November 4-9, Atlanta –March 10-15, 2013 – Orlando –July 28 – August 2, 2013 – Berlin –November 3-8, Vancouver

doc.: IEEE /1142r0 Submission September2012 Dorothy Stanley, Aruba NetworksSlide 20 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