Download presentation
Presentation is loading. Please wait.
1
IEEE 802.11-IETF Liaison Report
January 2005 doc.: IEEE yy/xxxxr0 July 2012 IEEE IETF Liaison Report Date: Authors: Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
2
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Abstract This presentation contains the IEEE – IETF liaison report for July 2012. Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
3
Recall Recent Liaison Activity (May)
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Recall Recent Liaison Activity (May) 802.1 Liaison 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) Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
4
Follow-up from Liaison Activity
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Follow-up from Liaison Activity Joint IETF/IEEE 802 Meeting planned Next week in Milpitas, draft agenda is here: 802 EC planning underway, see for example 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 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: Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
5
IEEE 802.11 & IETF Areas of Shared Interest - Monitored
January 2005 doc.: IEEE yy/xxxxr0 July 2012 IEEE & 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 to IETF liaison reports, such as this one Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
6
802.11 Liaison letters & IETF related documents to date (Mentor) - 1
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Liaison letters & IETF related documents to date (Mentor) - 1 Liaison letters: Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
7
802.11 Liaison letters & IETF related documents to date (Mentor)-2
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Liaison letters & IETF related documents to date (Mentor)-2 Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
8
Protocol to Access White Space database (paws) WG
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 Oct 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 [July 2012] UpdatedUse Cases and requirements, see Updated drafts: and New Framework document, see New Security Considerations, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
9
Handover Keying (HOKEY)
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 [July 2012] Updated – RFC 6630 Published, EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK) from Remaining milestones: Re-charter or shut down WG Did not meet at March 2012 IETF Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
10
EAP Method Update (EMU)
January 2005 doc.: IEEE yy/xxxxr0 July 2012 EAP Method Update (EMU) Working Group website: Documents Updates to draft of Standard Tunnel based EAP method, see Requirements for a Tunnel based EAP method in editor queue, see Individual submissions: An EAP Authentication Method Based on Identity-Based Authenticated Key Exchange: EAP Mutual Cryptographic Binding: Updates [July 2012]: New – Combination of Channel Binding and Tunnel Method: Updated version posted: Now in Area Director Evaluation: Channel Binding Support for EAP Methods draft, Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
11
6LOWPAN Working Group July 2012
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 Updates [July 2012] Revision available: Transmission of IPv6 packets over Bluetooth Low Energy, see New: Neighbor Discovery Optimization, see RFC 6066 “Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing” published, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
12
ROLL Working Group July 2012
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 [July 2012] Updated: A Mechanism to Measure the Quality of a Point-to-point Route in a Low Power and Lossy Network, see Of Interest: Applicability of ROLL in AMI Networks, 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 Of Interest: A Security Framework for Routing over Low Power and Lossy Networks, see New: Multicast Forwarding using Trickle, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
13
CORE Working Group July 2012
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 Updates [July 2012] Updated: Constrained Application Protocol, see Of Interest: Security Considerations in IP based Internet of Things, see Updated: Security Bootstrapping of Resource-Constrained Devices, see Many new documents, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
14
Emergency Context Resolution with Internet Technologies (ECRIT)
January 2005 doc.: IEEE yy/xxxxr0 July 2012 Emergency Context Resolution with Internet Technologies (ECRIT) Working Group website: Emergency Services Framework for Emergency Calling using Internet Multimedia, see Describing boundaries for Civic Addresses, see Updates [July 2012] Of interest: Data only emergency calls, see 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 Updated: Using Imprecise location, see New: Out of Jurisdiction Emergency Routing, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
15
IETF Geographic Location and Privacy (Geopriv) WG
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 Updates [July 2012] Of Interest: Location Configuration Extensions for Policy Management, see Updated: Relative Location, see Updated: A Location Dereferencing Protocol using HELD, see Updated: Using Device-provided Location-Related Measurements in Location Configuration Protocols, see Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
16
Home Networking (homenet) WG
January 2005 doc.: IEEE yy/xxxxr0 July 2012 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 [July 2012] Updated: Home networking Architecture for IPv6, see Updated: IPv6 Prefix Assignment in Small Networks, Of Interest: Grazed and Lightweight Open Protocol, see 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: Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
17
New: Dynamic Host Configuration (dhc) WG
January 2005 doc.: IEEE yy/xxxxr0 July 2012 New: Dynamic Host Configuration (dhc) WG See 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: Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
18
IETF Meetings Meetings: http://www.ietf.org
January 2005 doc.: IEEE yy/xxxxr0 July 2012 IETF Meetings Meetings: July 29 – August 3, Vancouver November 4-9, Atlanta March 10-15, 2013 – Orlando July 28 – August 2, 2013 – Berlin November 3-8, Vancouver Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
19
References RFC 4017 - IEEE 802.11 Requirements on EAP Methods
January 2005 doc.: IEEE yy/xxxxr0 July 2012 References RFC IEEE Requirements on EAP Methods Jan 2012 report (PAWS, Homenet details), Dorothy Stanley, Aruba Networks Dorothy Stanley, Agere Systems
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.