190 likes | 379 Views
IEEE 802.11-IETF Liaison Report. Authors:. Date: 2012-07-18. Abstract. This presentation contains the IEEE 802.11 – IETF liaison report for July 2012. Recall Recent Liaison Activity (May). 802.1 Liaison
E N D
IEEE 802.11-IETF Liaison Report Authors: Date: 2012-07-18 Dorothy Stanley, Aruba Networks
Abstract This presentation contains the IEEE 802.11 – IETF liaison report for July 2012. Dorothy Stanley, Aruba Networks
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) Dorothy Stanley, Aruba Networks
Follow-up from Liaison Activity • Joint IETF/IEEE 802 Meeting planned • Next week in Milpitas, draft agenda is here: http://trac.tools.ietf.org/group/iesg/trac/wiki/IEEE802andIETFleaders • 802 EC planning underway, see for example http://grouper.ieee.org/groups//802/secmail/msg14844.html • 802.11 Attendees • Jon Rosdahl (head of delegation) • Dorothy Stanley, Dave Halasz, Mark Hamilton, Gabor Bajko, Andrew Myles, Donald Eastlake • 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/ Dorothy Stanley, Aruba Networks
IEEE 802.11 & IETF Areas of Shared Interest - Monitored • EAP & EAP Methods: emu, hokey, eap, pana • RADIUS Attributes: radext • TVWS: paws • Smart Grid Applications: 6lowpan, roll, core • Emergency Services: ecrit & SDO Workshops • Location: geopriv • General: homenet • Security: RFC3610, RFC4017 • Other: capwap, mipshop, mobopts, bmwg, dna, mext • Monitor Via • Regular 802.11 to IETF liaison reports, such as this one Dorothy Stanley, Aruba Networks
802.11 Liaison letters & IETF related documents to date (Mentor) - 1 • https://mentor.ieee.org/802.11/dcn/12/11-12-0689-01-0000-may-2012-liaison-to-ietf.ppt • https://mentor.ieee.org/802.11/dcn/12/11-12-0122-01-0000-january-2012-liaison-to-ietf.ppt • https://mentor.ieee.org/802.11/dcn/11/11-11-0438-00-00af-ietf-paws.pptx • Liaison letters: • https://mentor.ieee.org/802.11/dcn/09/11-09-0718-01-000v-liaison-request-to-ietf-geopriv.doc • https://mentor.ieee.org/802.11/dcn/07/11-07-2786-00-0000-liaison-from-ietf-emu-to-ieee-802-11u.doc • https://mentor.ieee.org/802.11/dcn/07/11-07-1949-00-0000-liaison-response-to-ietf-radext.doc • https://mentor.ieee.org/802.11/dcn/07/11-07-0826-00-0000-ietf-eap-emergency-call-liaison.doc • https://mentor.ieee.org/802.11/dcn/07/11-07-0665-01-0000-liaison-response-to-ietf-capwap.doc • https://mentor.ieee.org/802.11/dcn/07/11-07-0508-01-000u-emergency-services-eap-requirements.ppt Dorothy Stanley, Aruba Networks
802.11 Liaison letters & IETF related documents to date (Mentor)-2 • https://mentor.ieee.org/802.11/dcn/07/11-07-0505-03-0000-emergency-services-shortened-tutorial.ppt • https://mentor.ieee.org/802.11/dcn/07/11-07-0476-01-0000-liaison-response-to-ietf-ecrit.doc • https://mentor.ieee.org/802.11/dcn/06/11-06-1723-00-0wng-summary-emergency-services-workshop.ppt • https://mentor.ieee.org/802.11/dcn/06/11-06-1563-00-0000-sdo-emergency-services-workshop.ppt • https://mentor.ieee.org/802.11/dcn/06/11-06-1538-01-000t-liaison-response-to-ietf-bmwg.doc • https://mentor.ieee.org/802.11/dcn/06/11-06-1124-00-0000-liaison-to-ietf-eap.doc • https://mentor.ieee.org/802.11/dcn/06/11-06-0577-01-ietf-liaison-response-ietf-pana.doc • https://mentor.ieee.org/802.11/dcn/05/11-05-0983-00-0000-liaison-to-ietf-from-ieee802-11u.doc • https://mentor.ieee.org/802.11/dcn/05/11-05-0347-01-ietf-letter-and-review-comments-capwap-objectives-draft.doc • https://mentor.ieee.org/802.11/dcn/05/11-05-0283-05-000u-liaison-to-ietf-from-ieee802-11-and-ieee802-21.doc • https://mentor.ieee.org/802.11/dcn/04/11-04-0160-07-000i-ieee-802-11-eap-requirements.doc Dorothy Stanley, Aruba Networks
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 • Oct 2011 - Submit 'Use Cases and Requirements for Accessing a Radio White Space Database' to the IESG for publication as Informational • April 2012 - Submit 'Accessing a Radio White Space Database' to the IESG for publication as Proposed Standard • Updates [July 2012] • UpdatedUse Cases and requirements, see http://www.ietf.org/id/draft-ietf-paws-problem-stmt-usecases-rqmts-06.txt • Updated drafts: http://datatracker.ietf.org/doc/draft-das-paws-protocol/ and http://datatracker.ietf.org/doc/draft-probasco-paws-discovery/ • New Framework document, see http://datatracker.ietf.org/doc/draft-wei-paws-framework/ • New Security Considerations, see http://datatracker.ietf.org/doc/draft-wu-paws-secutity/ Dorothy Stanley, Aruba Networks
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 [July 2012] • Updated – RFC 6630 Published, http://datatracker.ietf.org/doc/rfc6630/ - EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK) from http://datatracker.ietf.org/doc/draft-ietf-hokey-erp-aak/ • Remaining milestones: • Re-charter or shut down WG • Did not meet at March 2012 IETF Dorothy Stanley, Aruba Networks
EAP Method Update (EMU) • Working Group website: http://www.ietf.org/html.charters/emu-charter.html • Documents • Updates to draft of Standard Tunnel based EAP method, see http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ • Requirements for a Tunnel based EAP method in editor queue, see http://datatracker.ietf.org/doc/draft-ietf-emu-eaptunnel-req/ • Individual submissions: • An EAP Authentication Method Based on Identity-Based Authenticated Key Exchange: http://datatracker.ietf.org/doc/draft-cakulev-emu-eap-ibake/ • EAP Mutual Cryptographic Binding: http://datatracker.ietf.org/doc/draft-hartman-emu-mutual-crypto-bind/ • Updates [July 2012]: • New – Combination of Channel Binding and Tunnel Method: http://datatracker.ietf.org/doc/draft-zhou-emu-ch-tunnel/ • Updated version posted: Now in Area Director Evaluation: Channel Binding Support for EAP Methods draft, http://datatracker.ietf.org/doc/draft-ietf-emu-chbind/ Dorothy Stanley, Aruba Networks
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/ • Updates [July 2012] • Revision available: Transmission of IPv6 packets over Bluetooth Low Energy, see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ • New: Neighbor Discovery Optimization, see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-nd/ • RFC 6066 “Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing” published, see http://datatracker.ietf.org/doc/rfc6606/ Dorothy Stanley, Aruba Networks
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/draft-ietf-roll-of0/ • Routing protocol for efficient operation in low-power, lossy networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-rpl/ • Updates [July 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/ • Of Interest: Applicability of ROLL in AMI Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-applicability-ami/ • Updated: Reactive Discovery of Point-to-Point Routes in Low Power and Lossy Networks, see http://tools.ietf.org/html/draft-ietf-roll-p2p-rpl-12 • 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/ • New: Multicast Forwarding using Trickle, see http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ Dorothy Stanley, Aruba Networks
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 [July 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/ • Many new documents, see http://datatracker.ietf.org/wg/core/ Dorothy Stanley, Aruba Networks
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/draft-ietf-ecrit-framework/ • Describing boundaries for Civic Addresses, see http://tools.ietf.org/id/draft-thomson-ecrit-civic-boundary-02.txt • Updates [July 2012] • Of interest: Data only emergency calls, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ • 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/ • New: Out of Jurisdiction Emergency Routing, see http://datatracker.ietf.org/doc/draft-winterbottom-ecrit-priv-loc/ Dorothy Stanley, Aruba Networks
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/ Dorothy Stanley, Aruba Networks
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 [July 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/ Dorothy Stanley, Aruba Networks
New: Dynamic Host Configuration (dhc) WG • See http://datatracker.ietf.org/wg/dhc/ • This 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 [July 2012] • New: http://www.ietf.org/id/draft-cao-dhc-anqp-option-00.txt Dorothy Stanley, Aruba Networks
IETF Meetings • Meetings: • July 29 – August 3, 2012 - Vancouver • 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 Dorothy Stanley, Aruba Networks
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 Dorothy Stanley, Aruba Networks