1 / 19

IEEE 802.11-IETF Liaison Report

IEEE 802.11-IETF Liaison Report. Authors:. Date: 2014-03-18. Abstract. This presentation contains the IEEE 802.11 – IETF liaison report for March 2014. IETF- IEEE 802 Liaison Activity - 1 . Joint Meetings, agenda and presentations: Telecon Meeting held 27 Jan 2014

kaemon
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:2014-03-18 Dorothy Stanley, Aruba Networks

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

  3. IETF- IEEE 802 Liaison Activity - 1 • Joint Meetings, agenda and presentations: Telecon Meeting held 27 Jan 2014 • http://www.iab.org/activities/joint-activities/iab-ieee-coordination/, see http://www.iab.org/wp-content/IAB-uploads/2013/01/2014-01-27-ietf-ieee802-minutes.txt • No new IEEE 802.11 items • Next joint IEEE 802/IETF IESG coordination meeting: Week June 16th, 2014 • Next face to face meeting: 29 Sept 2014 Dorothy Stanley, Aruba Networks

  4. IETF- IEEE 802 Liaison Activity - 2 • RFC4441bis update, see http://www.ietf.org/id/draft-iab-rfc4441rev-08.txt • Nearing completion • IEEE 802.11 Comment Collection held on PAWS document – no comments received • Request received from OPSAWG (next 2 slides) • New “IETF/IAB/IESG..” 802 EC Standing Committee being considered – Pat Thaler; structure, scope under discussion Dorothy Stanley, Aruba Networks

  5. Alternate Tunnel Liaison request From: Warren Kumari [mailto:warren@kumari.net] Sent: Friday, March 07, 2014 1:14 AM To: bkraemer@ieee.org Cc: Dorothy Stanley; pthaler@broadcom.com; Dan Romascanu; Benoit Claise; joel jaeggli; opsawg-chairs@tools.ietf.org Subject: Alternate Tunnel Encapsulation for Data Frames in CAPWAP.  The charter of the IETF Operations Area Working Group (OPSAWG) http://datatracker.ietf.org/wg/opsawg/charter/ covers new work as well as work that once belonged in IETF Operations Area WGs that have concluded.  One of these Working Groups is Control And Provisioning of Wireless Access Points (CAPWAP) Working Group that developed the CAPWAP protocol with advice and reviews from IEEE 802.11. At the OPSAWG meeting held in London on 3/4/2014 a proposal for an '"Alternate Tunnel Encapsulation for Data Frames in CAPWAP'" http://www.ietf.org/id/draft-zhang-opsawg-capwap-cds-02.txt was submitted for consideration as a new OPSAWG work item. The WG agreed that there is interest in proceeding with this work, but before approving it as WG item would like feedback on whether IEEE 802.11 sees any architectural or technical problems with the approach proposed by this work. We would be grateful if you can review this work-in-progress document and let us know if you detect any potential problems. If possible we would like to receive your response before April 11, 2014. We appreciate your continuous support and expert advice for the work done in the IETF. Yours, Melinda Shore, Scott Bradner, Warren Kumari. Dorothy Stanley, Aruba Networks

  6. Liaison response From: Bruce Kraemer bkraemer@ieee.org To: Warren Kumari [mailto:warren@kumari.net] Melinda Shore, Scott Bradner Cc: Dorothy Stanley; pthaler@broadcom.com; Dan Romascanu; Benoit Claise; joel jaeggli; opsawg-chairs@tools.ietf.org Subject: Alternate Tunnel Encapsulation for Data Frames in CAPWAP Thank you for the opportunity to review the "Alternate Tunnel Encapsulation for Data Frames in CAPWAP'" http://www.ietf.org/id/draft-zhang-opsawg-capwap-cds-02.txtdocument. The Alternate Tunnel Encapsulation draft appears to address implementation of the IEEE 802.11 Distribution System (DS). Implementation of the DS is outside the scope of the IEEE 802.11 standard. We will inform IEEE 802.11 members of this work, and welcome further requests from the OPSAWG for information or clarification of the IEEE 802.11 standard. Thank you, Bruce Kraemer Chair, IEEE 802.11 • Motion to approve the liaison response in 11-14-0368r1 Slide 6 approved in ARC (12-0-0) Dorothy Stanley, Aruba Networks

  7. Protocol to Access White Space database (paws) WG • Received request for IEEE 802.11 review of paws protocol draft document: https://datatracker.ietf.org/doc/draft-ietf-paws-protocol/ • Held IEEE 802.11 Call for Comments • No comments received • 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/ • Updated Use Cases and requirements, published as RFC 6953: https://datatracker.ietf.org/doc/rfc6953/ Dorothy Stanley, Aruba Networks

  8. 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/ • IEEE 802 Liaisons list is available • http://ieee-sa.centraldesktop.com/802liaisondb/FrontPage Dorothy Stanley, Aruba Networks

  9. IETF Meetings • Meetings: • March 2-5, 2014 – London • July 20-25, 2014 – Toronto • November 9-14, 2014 – Honolulu • March 22-27, 2015 – Dallas • July 19-24, 2015 – Prague • November 1-6, 2015 - Yokahama • http://www.ietf.org • Newcomer training: https://www.ietf.org/edu/process-oriented-tutorials.html#newcomers • Tutorials (process and technical); Wireless Tutorial (Donald Eastlake) : https://www.ietf.org/edu/tutorials.html Dorothy Stanley, Aruba Networks

  10. BOF Sessions – March 2014 • See http://trac.tools.ietf.org/bof/trac/wiki/WikiStart • Authentication and Authorization for Constrained Environments (ACE) • Domain Boundaries (DBound) • non-ASCII characters in RFCs and other format updates (rfcform) • DMSe - Encryption of DNS requests for confidentiality • Internet Governance Update (igovupdate) • Host Identification, Address and Prefix Sharing in Wi-Fi Access (HIAPS) • Transparency (Taps) • Transport (trans) • TURN revised and Modernized (Tram) • Virtualized Network Function Pool (VNFPool) • Traversal Using Relays around NAT (TURN) Revised and Modernized (TRAM) • Tunneling Compressed Multiplexed Traffic Flows (TCMTF) Dorothy Stanley, Aruba Networks

  11. New item - STRINT • Strengthening the Internet Against Pervasive Monitoring • STRINT workshop page, where you will find the materials (presentations and position papers): • https://www.w3.org/2014/strint/ • STRINT workshop summary (errata: should be IAB/W3C, and not IETF/W3C): • https://mentor.ieee.org/802-ec/dcn/14/ec-14-0023-00-00EC-strint-workshop-summary.pptx Dorothy Stanley, Aruba Networks

  12. 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 [March2014] • Submitted for publication: RADIUS Attributes for IEEE 802 Networks, see http://datatracker.ietf.org/doc/draft-ietf-radext-ieee802ext/ Dorothy Stanley, Aruba Networks

  13. 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/ • EAP Mutual Cryptographic Binding: Introduces a new form of cryptographic binding that protects both peer and server, rather than just the server. Published as http://datatracker.ietf.org/doc/rfc7029/ • Updates [March2014]: • Tunnel EAP Method (TEAP) in RFC editor queue: http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ Dorothy Stanley, Aruba Networks

  14. 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 • Relative Location, published as RFC 7035, see https://datatracker.ietf.org/doc/rfc7035/ • 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 [March2014] • Using Device-provided Location-Related Measurements in Location Configuration Protocols, Published as RFC 7105, http://datatracker.ietf.org/doc/rfc7105/ • Updated: Location Information Server Discovery using IP address and reverse DNS, see https://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/ Dorothy Stanley, Aruba Networks

  15. 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 [March 2014] • Updated: Additional Data related to an emergency call, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ • Updated: Trustworthy Location, see https://datatracker.ietf.org/doc/draft-ietf-ecrit-trustworthy-location/ • Of interest: Unauthorized access, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-unauthenticated-access/ in IESG review • Of interest: Internet Protocol-based In-Vehicle Emergency Calls, see https://datatracker.ietf.org/doc/draft-gellens-ecrit-car-crash/ Dorothy Stanley, Aruba Networks

  16. 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 [March2014] Documents of interest: • Updated: Home networking Architecture for IPv6, see https://datatracker.ietf.org/doc/draft-ietf-homenet-arch/ - submitted for publication Dorothy Stanley, Aruba Networks

  17. Operations Area Working Group • http://datatracker.ietf.org/wg/opsawg/ • Area WG processes submissions related to Operations Area WGs that have closed • Control and Provisioning of Wireless Access Points (CAPWAP) Working Group closed in 2009 • Operations Area Working Group work group items • http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/ • http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac • Have a request from OPSAWG chairs for IEEE 802.11 review of additional document • “Alternate Tunnel Encapsulation for Data Frames in CAPWAP” http://www.ietf.org/id/draft-zhang-opsawg-capwap-cds-02.txt Dorothy Stanley, Aruba Networks

  18. Of Interest to Smart Grid • 6LOWPAN • 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 • ROLL • Working Group website: http://datatracker.ietf.org/wg/roll/ • Focus: Routing over Low Power and LossyNetworks • CORE • (Constrained RESTful Environments) Working Group website: http://datatracker.ietf.org/wg/core/ • Focus: framework for resource-oriented applications intended to run on constrained IP networks. Dorothy Stanley, Aruba Networks

  19. 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

More Related