doc.: ieee 802.11-12/1142r0 submission september2012 dorothy stanley, aruba networksslide 1 ieee...

doc.: IEEE 802.11-12/1142r0

Submission

September2012

Dorothy Stanley, Aruba NetworksSlide 1

IEEE 802.11-IETF Liaison ReportDate: 2012-09-19

Name Company Address Phone email Dorothy Stanley Aruba Networks 1322 Crossman Ave

Sunnyvale, CA 630-363-1389 dstanley@arubanetworks.

com

Authors:

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Abstract

This presentation contains the IEEE 802.11 – IETF liaison report for September 2012.

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Recall Recent Liaison Activity (May)

•802.1 Liaison– https://

datatracker.ietf.org/documents/LIAISON/liaison-2012-03-19-ieee-8021-the-iesg-liaison-to-iesg-from-ieee-8021-attachment-1.pdf

•IETF Response: May 10, 2012– http://datatracker.ietf.org/liaison/1155/ – Thank you for your liaison letter dated 3/19/2012. – We share your desire for the IETF and the IEEE 802 (and the IEEE 802.1 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 802.1.

– 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 802.11-12/1142r0

Submission

September2012


Follow-up from Liaison Activity

•Joint IETF/IEEE 802 Meeting held 25 July 2012– Agenda is here: http://trac.tools.ietf.org/group/iesg/trac/wiki/IEEE802andIETFleaders – Jon Rosdahl (head of delegation), Dorothy Stanley, Dave Halasz, Mark Hamilton,

Gabor Bajko, Andrew Myles, Donald Eastlake– Notes and meeting materials available here: http://www.ietf.org/iesg/ieee/

•Teleconference meeting held 5 Sept 2012– Notes

•Teleconference planned 29 Oct 2012

C:\Users\dstanley\Documents\IETF-IEEE_802

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Action Items – Initial Meeting

•From http://www.ietf.org/iesg/ieee/minutes-2012-07-25.txt •Spencer Dawkins, Eric Gray, Dan Romascanu, Dorothy Stanley and Pat Thaler agreed to work on an update to RFC 4441. •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 802.11-12/1142r0

Submission

September2012


About RFC 4441 & IETF liaisons

•Reference document: RFC 4441– 2006 document, but still relevant: “The IEEE 802/IETF Relationship”, see

http://tools.ietf.org/html/rfc4441– Liaison info: http://www.ietf.org/liaison/managers.html. IETF has a liaison manager

FROM IETF to IEEE SA and IEEE 802.1, not to 802.11. • 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: https://datatracker.ietf.org/liaison/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Diffie-Hellman Group Repository Liaison Request

•Liaison request from July 2012 meeting– See https://

mentor.ieee.org/802.11/dcn/12/11-12-0977-00-0000-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 802.11-12/1142r0

Submission

September2012


Protocol to Access White Space database (paws) WG

•paws Working Group was formed June 2011, see http://datatracker.ietf.org/wg/paws/ •Charter and problem statement documents:

– Charter, see https://datatracker.ietf.org/wg/paws/charter/ – Problem Statement, see https://datatracker.ietf.org/doc/draft-patil-paws-problem-stmt/

•Goals and Milestones [dated updated]– Aug 2012 - Submit 'Use Cases and Requirements for Accessing a Radio White Space Database' to

the IESG for publication as Informational – April 2013 - Submit 'Accessing a Radio White Space Database' to the IESG for publication as

Proposed Standard •Updates [Sept 2012]

– Updated Use Cases and requirements, see http://datatracker.ietf.org/doc/draft-ietf-paws-problem-stmt-usecases-rqmts/

– Updated drafts: http://datatracker.ietf.org/doc/draft-das-paws-protocol/ and http://datatracker.ietf.org/doc/draft-probasco-paws-discovery/

– Framework document, see http://datatracker.ietf.org/doc/draft-wei-paws-framework/ – Security Considerations, see http://datatracker.ietf.org/doc/draft-wu-paws-secutity/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Handover Keying (HOKEY)• Hokey Charter available at http://www.ietf.org/html.charters/hokey-charter.html

– Extensions to current EAP key framework to facilitate inter-authenticator handover and roaming.

• Published RFCs: – Handover Key Management and Re-authentication Problem Statement, see

http://www.ietf.org/rfc/rfc5169.txt – Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK),

see http://www.ietf.org/rfc/rfc5295.txt – EAP Extensions for EAP Re-authentication Protocol (ERP), see

http://www.ietf.org/rfc/rfc5296.txt – Distribution of EAP based keys for handover and re-authentication , see

http://www.ietf.org/rfc/rfc5749.txt [published March 2010]– Extensible Authentication Protocol (EAP) Early Authentication Problem Statement, see

http://tools.ietf.org/html/rfc5836 [published April 2010]• Updates [Sept 2012]

– Did not meet at July 2012 IETF– WG closed

doc.: IEEE 802.11-12/1142r0

Submission

September2012


EAP Method Update (EMU)

• Working Group website: http://www.ietf.org/html.charters/emu-charter.html • RFC Documents - published

– The EAP-TLS Authentication Protocol - http://datatracker.ietf.org/doc/rfc5216/ – Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) Method- http

://datatracker.ietf.org/doc/rfc5433/ – Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods http

://datatracker.ietf.org/doc/rfc6677/– Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method - http

://datatracker.ietf.org/doc/rfc6678/

• Updates [Sept 2012]:– Tunnel EAP Method (TEAP) Version 1 -

http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ – An EAP Authentication Method Based on Identity-Based Authenticated Key Exchange - http

://datatracker.ietf.org/doc/draft-cakulev-emu-eap-ibake/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


6LOWPAN Working Group

• Working Group website: http://datatracker.ietf.org/wg/6lowpan/charter/• Focus: IPv6 over Low Power PAN: Adaption of IPv6 protocol to operate on

constrained nodes and link layers– RFC 4944: adaption of IPv6 to 802.15.4 link layer– Improved header compression scheme, see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-hc/ – RFC 6282, “Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks”

published, see http://datatracker.ietf.org/doc/rfc6282/ – Design and Application Spaces (Use Cases), see

http://datatracker.ietf.org/doc/draft-ietf-6lowpan-usecases/ – RFC 6066 “Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal

Area Network (6LoWPAN) Routing” see http://datatracker.ietf.org/doc/rfc6606/

• Updates [Sept 2012]– Revision available: Transmission of IPv6 packets over Bluetooth Low Energy, see

http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ – Revision available: Neighbor Discovery Optimization, see

http://datatracker.ietf.org/doc/draft-ietf-6lowpan-nd/ – Of interest: Lightweight Secure Neighbor Discovery for Low-power and Lossy Networks, see

http://datatracker.ietf.org/doc/draft-sarikaya-6lowpan-cgand/ – New: 6LoWPAN Roadmap and Implementation Guide

http://datatracker.ietf.org/doc/draft-bormann-6lowpan-roadmap/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


ROLL Working Group• Working Group website: http://datatracker.ietf.org/wg/roll/

• Focus: Routing over Low Power and Lossy Networks– Routing Objectives, see http://datatracker.ietf.org/doc/rfc6552/

– Routing protocol for efficient operation in low-power, lossy networks, see http://datatracker.ietf.org/doc/rfc6550/

• Updates [Sept 2012]– Updated: A Mechanism to Measure the Quality of a Point-to-point Route in a Low Power and

Lossy Network, see http://datatracker.ietf.org/doc/draft-ietf-roll-p2p-measurement/

– Updated: Recommendations for Efficient Implementation of RPL: http://datatracker.ietf.org/doc/draft-gnawali-roll-rpl-recommendations/

– Of Interest: Applicability of ROLL in AMI Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-applicability-ami/

– Of Interest: Lightweight Key Establishment and Management Protocol in Dynamic Sensor Networks (KEMP), see http://datatracker.ietf.org/doc/draft-qiu-roll-kemp/

– Of Interest: A Security Framework for Routing over Low Power and Lossy Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-security-framework/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


CORE Working Group• CORE (Constrained RESTful Environments) Working Group

website: http://datatracker.ietf.org/wg/core/

• Focus: framework for resource-oriented applicationsintended to run on constrained IP networks

– Constrained Application Protocol, see http://datatracker.ietf.org/doc/draft-ietf-core-coap/

• Updates [Sept 2012] – Updated: Constrained Application Protocol, see

http://datatracker.ietf.org/doc/draft-ietf-core-coap/

– Of Interest: Security Considerations in IP based Internet of Things, see http://datatracker.ietf.org/doc/draft-garcia-core-security/

– Updated: Security Bootstrapping of Resource-Constrained Devices, see http://datatracker.ietf.org/doc/draft-sarikaya-core-sbootstrapping/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Emergency Context Resolution with Internet Technologies (ECRIT)

• Working Group website: http://www.ietf.org/dyn/wg/charter/ecrit-charter.html

• Emergency Services – Framework for Emergency Calling using Internet Multimedia, see

http://datatracker.ietf.org/doc/rfc6443/ – Describing boundaries for Civic Addresses, see

http://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 http://datatracker.ietf.org/doc/draft-ietf-ecrit-lost-sync/

– Updated: Internet Protocol-based In-Vehicle Emergency Call, see http://datatracker.ietf.org/doc/draft-rosen-ecrit-ecall/

– Updated: Additional data related to an emergency call, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/

– Updated: Using Imprecise location, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-rough-loc/ – Of interest: Out of Jurisdiction Emergency Routing, see

http://datatracker.ietf.org/doc/draft-winterbottom-ecrit-priv-loc/ – Of interest: Extensions to the Emergency Services Architecture for dealing with

Unauthenticated and Unauthorized Devices, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-unauthenticated-access/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


IETF Geographic Location and Privacy (Geopriv) WG

• See http://www.ietf.org/html.charters/geopriv-charter.html • Specific reference to WLANs:

– Carrying Location Objects in RADIUS, see http://www.ietf.org/proceedings/66/IDs/draft-ietf-geopriv-radius-lo-08.txt

• Documents referenced in 802.11 (TGv)– Geopriv Requirements, see http://www.ietf.org/rfc/rfc3693.txt – Civic Address definitions, see http://www.ietf.org/rfc/rfc4776.txt

• July 2009 Liaison to IETF GEOPRIV– See https://mentor.ieee.org/802.11/dcn/09/11-09-0718-01-000v-liaison-request-to-ietf-geopriv.doc

• Updates [July 2012]– Of Interest: Location Configuration Extensions for Policy Management, see

http://datatracker.ietf.org/doc/draft-ietf-geopriv-policy-uri/ – Updated: Relative Location, see http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/ – Updated: A Location Dereferencing Protocol using HELD, see

http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/ – Updated: Using Device-provided Location-Related Measurements in Location Configuration

Protocols, see http://datatracker.ietf.org/doc/draft-ietf-geopriv-held-measurements/ – Of Interest: Relative Location Representation, see

http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Home Networking (homenet) WG

• See https://datatracker.ietf.org/wg/homenet/ • 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

https://datatracker.ietf.org/doc/draft-ietf-homenet-arch/ – Updated: IPv6 Prefix Assignment in Small Networks,

http://datatracker.ietf.org/doc/draft-baker-homenet-prefix-assignment/ – Of Interest: Grazed and Lightweight Open Protocol, see

http://datatracker.ietf.org/doc/draft-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, http://datatracker.ietf.org/doc/draft-arkko-homenet-physical-standard/

– Of Interest: Extended Multicast DNS: http://datatracker.ietf.org/doc/draft-lynn-homenet-site-mdns/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


Dynamic Host Configuration (dhc) WG

• See http://datatracker.ietf.org/wg/dhc/ • 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: http://www.ietf.org/id/draft-cao-dhc-anqp-option-00.txt

doc.: IEEE 802.11-12/1142r0

Submission

September2012


New: RADEXT WG

• See http://datatracker.ietf.org/wg/radext/ • RADIUS Extensions

– The RADIUS Extensions Working Group will focus on extensions to theRADIUS protocol required to define extensions to the standardattribute space as well as to address cryptographic algorithmagility and use over new transports.

– In addition, RADEXT will work on RADIUS Design Guidelines and define new attributes forparticular applications of authentication, authorization andaccounting such as NAS management and local area network (LAN) usage.

• Updates [September 2012]– Of interest: RADIUS Attributes for IEEE 802 Networks, see

http://datatracker.ietf.org/doc/draft-ietf-radext-ieee802ext/

doc.: IEEE 802.11-12/1142r0

Submission

September2012


IETF Meetings• Meetings:

– November 4-9, 2012 - Atlanta

– March 10-15, 2013 – Orlando

– July 28 – August 2, 2013 – Berlin

– November 3-8, 2013 - Vancouver

• http://www.ietf.org

doc.: IEEE 802.11-12/1142r0

Submission

September2012


References

• RFC 4017 - IEEE 802.11 Requirements on EAP Methods

• Jan 2012 report (PAWS, Homenet details), https://mentor.ieee.org/802.11/dcn/12/11-12-0122-01-0000-january-2012-liaison-to-ietf.ppt