doc.: ieee 802.11-13/0097r0 submission january 2013 dorothy stanley, aruba networksslide 1 ieee...
TRANSCRIPT
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 1
IEEE 802.11-IETF Liaison ReportDate: 2013-01-16
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-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 2
Abstract
This presentation contains the IEEE 802.11 – IETF liaison report for January 2013.
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 3
Follow-up from IETF- IEEE 802 Liaison Activity
• Joint IETF/IEEE 802 Meeting held 25 July 2012– Agenda is here: http://trac.tools.ietf.org/group/iesg/trac/wiki/IEEE802andIETFleaders – Notes and meeting materials available here: http://www.ietf.org/iesg/ieee/
• Teleconference meetings– 5 Sept 2012 - notes, including action items– 29 Oct 2012– 17 Dec 2012– Next: 12 Feb 2013
• IEEE 802.11 items– RFC4441bis update, see http://www.ietf.org/id/draft-dawkins-iab-rfc4441rev-02.txt
(posted) and revision in progress; comments welcome – Description of new Trill related area of mutual interest: “Area Name - use of TRILL as
an alternative path selection protocol for use in 802.11 mesh networks”– List of topic areas of mutual interest:
C:\Users\dstanley\Documents\IETF-IEEE_802
29Oct2012-notesC:\Users\dstanley\
Documents\IETF-IEEE_802
Microsoft Word Document
C:\Users\dstanley\Documents\IETF-IEEE_802
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 4
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-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 5
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 [January 2013]– Of interest: RADIUS Attributes for IEEE 802 Networks, see
http://datatracker.ietf.org/doc/draft-ietf-radext-ieee802ext/ – Additional comments provided based on Nov discussion in ARC, see http://
www.ietf.org/mail-archive/web/radext/current/msg07916.html , in addition to http://www.ietf.org/mail-archive/web/radext/current/msg07864.html
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 6
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
• Updates [January 2013]– IKE Group Registry update RFC – Draft available: https
://datatracker.ietf.org/doc/draft-harkins-brainpool-ike-groups/ – Currently in IETF last call (Sponsor Ballot equivalent)– Expect document approval early 2013
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 7
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 – 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 [January 2013]
– Updated Use Cases and requirements, see http://datatracker.ietf.org/doc/draft-ietf-paws-problem-stmt-usecases-rqmts/
– New: Paws protocol draft document: https://datatracker.ietf.org/doc/draft-ietf-paws-protocol/ – Security Considerations, see http://datatracker.ietf.org/doc/draft-wu-paws-secutity/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 8
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 [January 2013]:– New: EAP Mutual Cryptographic Binding, see
http://datatracker.ietf.org/doc/draft-ietf-emu-crypto-bind/ . Introduces a new form of cryptographic binding that protects both peer and server, rather than just the server.
– Tunnel EAP Method (TEAP) Version 1 - http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ - In Working Group Last Call (analogous to Working Group Letter Ballot)
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 9
New: Public-Key Infrastructure (X.509) (pkix)
• Working Group website: http://datatracker.ietf.org/wg/pkix/charter/ – Develops Internet standards to support X.509-based Public
Key Infrastructures (PKIs).• RFC Documents - published
– Numerous – see website
• Updates [January 2013]:– Of interest for enrollment of devices into a certificate infrastructure:
Updated: Enrollment over Secure Transport: http://tools.ietf.org/html/draft-ietf-pkix-est-03
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 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
• Updates [January 2013]– Relative Location, see
http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/ draft to be submitted for publication
– No meeting at March IETF.
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 11
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 [January 2013]
– Updated: Public Safety Answering Point (PSAP) Callback http://datatracker.ietf.org/doc/draft-ietf-ecrit-psap-callback/
– Updated: Policy for defining new service-identifying lables, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-service-urn-policy/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 12
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 [January 2013] Documents of interest:– Home networking Architecture for IPv6, see
https://datatracker.ietf.org/doc/draft-ietf-homenet-arch/ – IPv6 Home Network Front End Naming Delegation, see
https://datatracker.ietf.org/doc/draft-mglt-homenet-front-end-naming-delegation/ – Secret Gardens are Better than Walled Gardens, see
https://datatracker.ietf.org/doc/draft-richardson-homenet-secret-gardens/ – BRDP for homenet, see
https://datatracker.ietf.org/doc/draft-richardson-homenet-secret-gardens/ – Bootstrapping trust on a Homenet, see
https://datatracker.ietf.org/doc/draft-behringer-homenet-trust-bootstrap/ – Grazed and Lightweight Open Protocol, see
http://datatracker.ietf.org/doc/draft-ruminski-homenet-galop-proto/– Extended Multicast DNS: http://datatracker.ietf.org/doc/draft-lynn-homenet-site-mdns/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 13
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 [January 2013]– Of interest: http://tools.ietf.org/html/draft-cao-dhc-anqp-option-01 also
http://datatracker.ietf.org/doc/draft-cao-dhc-anqp-option/history/ – New: http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-radius-opt/ – New: http://datatracker.ietf.org/doc/draft-ietf-dhc-relay-id-suboption/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 14
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/ – RFC 6775 - “Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs)”, see https://datatracker.ietf.org/doc/rfc6775/ • Updates [January 2013]
– New: http://datatracker.ietf.org/doc/draft-schoenw-6lowpan-mib/ – Of interest: 6LoWPAN Roadmap and Implementation Guide
http://datatracker.ietf.org/doc/draft-bormann-6lowpan-roadmap/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 15
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/ – RFC 6719, “The Minimum Rank with Hysteresis Objective Function“, see
http://datatracker.ietf.org/doc/rfc6719/ • Updates [January 2013]
– Of Interest: A Security Threat Analysis for Routing over Low Power and Lossy Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-security-threats/
– 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: Reactive Discovery of Point-to-Point Routes in Low Power and Lossy Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-p2p-rpl/
– Of Interest: Lightweight Key Establishment and Management Protocol in Dynamic Sensor Networks (KEMP), see http://datatracker.ietf.org/doc/draft-qiu-roll-kemp/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 16
CORE Working Group• 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. – Constrained networks can occur as part of home and building automation, energy management,
and the Internet of Things. – RFC 6690, Constrained RESTful Environments (CoRE) Link Format, see
http://datatracker.ietf.org/doc/rfc6690/ • Updates [January 2013]
– Updated: Constrained Application Protocol, see http://datatracker.ietf.org/doc/draft-ietf-core-coap/
– Updated: Group Communication for CoAP:, see http://datatracker.ietf.org/doc/draft-ietf-core-groupcomm/
– Of Interest: Blockwise transfers in CoAP, see http://datatracker.ietf.org/doc/draft-ietf-core-block/
– Of interest: Security Bootstrapping of Resource-Constrained Devices, see http://datatracker.ietf.org/doc/draft-sarikaya-core-sbootstrapping/
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 17
IETF Meetings• Meetings:
– March 10-15, 2013 – Orlando– July 28 – August 2, 2013 – Berlin– November 3-8, 2013 – Vancouver– March 2-5, 2014 – London – July 20-25, 2014 – Toronto– November 9-14, 2014 - Honolulu
• http://www.ietf.org
doc.: IEEE 802.11-13/0097r0
Submission
January 2013
Dorothy
Stanley, Aruba Networ
ks
Slide 18
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