1 / 12

IEEE 802.11-IETF Liaison Report

IEEE 802.11-IETF Liaison Report. Authors:. Date: 2010-09-15. Abstract. This presentation contains the IEEE 802.11 – IETF liaison report for September 2010. New: Mobility EXTensions for IPv6(mext) WG. See https://datatracker.ietf.org/wg/mext/charter/

yen-doyle
Download Presentation

IEEE 802.11-IETF Liaison Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IEEE 802.11-IETF Liaison Report Authors: Date: 2010-09-15 Dorothy Stanley, Aruba Networks

  2. Abstract This presentation contains the IEEE 802.11 – IETF liaison report for September 2010. Dorothy Stanley, Aruba Networks

  3. New: Mobility EXTensions for IPv6(mext) WG • See https://datatracker.ietf.org/wg/mext/charter/ • The MEXT Working Group continues the work of the former MIP6, NEMO, and MONAMI6 Working Groups. • The primary goal of MEXT will be to enhance base IPv6 mobility bycontinuing work on developments that are required for wide-scaledeployments and specific deployment scenarios. • Additionally, the workinggroup will ensure that any issues identified by implementation andinteroperability experience are addressed, and that the basespecifications are maintained. • The group will also produce informationaldocumentation, such as design rationale documents or description ofspecific issues within the protocol. • The MEXT WG will also explore experimental alternative securitymechanisms. The security mechanism specified in the existing standardtrack RFCs (RFC3775bis, RFC4877) remains the mandatory to implementmechanism that guarantees interoperability between differentimplementations. • The MEXT WG is chartered to deliver one or moreexperimental alternative mechanisms. All the alternative solutions willbe published as experimental RFCs. Dorothy Stanley, Aruba Networks

  4. 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] • Updates [July 2010]: • Extensible Authentication Protocol (EAP) Early Authentication Problem Statement, see http://tools.ietf.org/html/rfc5836 [published April 2010] • Updates [September 2010] • EAP extensions for EAP Re-authentication protocol, see https://datatracker.ietf.org/doc/draft-ietf-hokey-rfc5296bis/ • Architecture design, see https://datatracker.ietf.org/doc/draft-ietf-hokey-arch-design/ Dorothy Stanley, Aruba Networks

  5. Update: EAP Method Update (EMU) • Working Group website: http://www.ietf.org/html.charters/emu-charter.html • IEEE 802.11 liaison request • Requirements are documented in 11-07-0508-01-000u-emergency-services-eap-requirements • Response received from IETF EMU, see https://mentor.ieee.org/802.11/public-file/07/11-07-2786-00-0000-liaison-from-ietf-emu-to-ieee-802-11u.doc . • Response under consideration in TGu • Updates [July 2010]: • Channel Binding, see http://datatracker.ietf.org/doc/draft-ietf-emu-chbind/ • Tunnel Method Requirements, see http://datatracker.ietf.org/doc/draft-ietf-emu-eaptunnel-req/ • Updates [September 2010]: • EAP Authentication using only a password, see http://datatracker.ietf.org/doc/rfc5931/published August 2010 • EAP Authentication based on the EKE protocol, see https://datatracker.ietf.org/doc/draft-sheffer-emu-eap-eke/ Dorothy Stanley, Aruba Networks

  6. 6LOWPAN Working Group • Working Group website: http://datatracker.ietf.org/wg/6lowpan/charter/ • Focus: 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/ • Neighbor discovery protocol modifications http://datatracker.ietf.org/doc/draft-ietf-6lowpan-nd/ • Reference: Smart Grid Tutorial Presentations, slides 58-60 • https://mentor.ieee.org/802-ec/dcn/10/ec-10-0013-00-00EC-smart-grid-information-update-july-2010.pdf Dorothy Stanley, Aruba Networks

  7. 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/ • Reference: Smart Grid Tutorial Presentations, slides 58-60 • https://mentor.ieee.org/802-ec/dcn/10/ec-10-0013-00-00EC-smart-grid-information-update-july-2010.pdf Dorothy Stanley, Aruba Networks

  8. CORE Working Group • 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/ • Reference: Smart Grid Tutorial Presentations, slides 58-60 • https://mentor.ieee.org/802-ec/dcn/10/ec-10-0013-00-00EC-smart-grid-information-update-july-2010.pdf Dorothy Stanley, Aruba Networks

  9. 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://www.ietf.org/id/draft-ietf-ecrit-framework-11.txt • Unauthenticated access being discussed, see http://tools.ietf.org/id/draft-schulzrinne-ecrit-unauthenticated-access-08.txt • Describing boundaries for Civic Addresses, see http://tools.ietf.org/id/draft-thomson-ecrit-civic-boundary-01.txt • Updates [September 2010] • Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries RFC published, see https://datatracker.ietf.org/doc/rfc5964/ Dorothy Stanley, Aruba Networks

  10. 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 • November 2009 Contributions • See http://www.ietf.org/id/draft-stanley-geopriv-int-ext-00.txt and http://tools.ietf.org/id/draft-polk-geopriv-int-relative-in-tlv-00.txt and http://tools.ietf.org/id/draft-thomson-geopriv-indoor-location-00.txt • March 2010 Contributions • http://tools.ietf.org/id/draft-rosen-geopriv-pidf-interior-01.txt and • http://tools.ietf.org/id/draft-thomson-geopriv-relative-location-00.txt • July 2010 Updated draft • http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/ • Updates [September 2010] • New draft, Location-related measurements in Location Configuration Protocols, see https://datatracker.ietf.org/doc/draft-ietf-geopriv-held-measurements/ • DHCP Options for LCI, see https://datatracker.ietf.org/doc/draft-ietf-geopriv-rfc3825bis/ Dorothy Stanley, Aruba Networks

  11. IETF Meetings • Meetings: • November 7-12, 2010, Beijing (overlaps next 802 plenary) • March 27-April 1, 2011, Prague • July 24-29, 2011Quebec City • November 13-18, 2011 Taipei • http://www.ietf.org Dorothy Stanley, Aruba Networks

  12. References • RFC 4017 - IEEE 802.11 Requirements on EAP Methods Dorothy Stanley, Aruba Networks

More Related