1. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 1 IEEE 802.11-IETF Liaison Report Date: 2011-05-11 Authors:

2. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 2 Abstract This presentation contains the IEEE 802.11 – IETF liaison report for May 2011.

3. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 3 Protocol to Access White Space database (paws) WG A paws BOF was held at the March 2011 IETF meeting –BOF minutes, see http://www.ietf.org/mail-archive/web/paws/current/msg00117.htmlhttp://www.ietf.org/mail-archive/web/paws/current/msg00117.html Draft charter and problem statement documents: –Problem Statement, see http://tools.ietf.org/html/draft-patil-paws-problem-stmt-01http://tools.ietf.org/html/draft-patil-paws-problem-stmt-01 –Use Case Scenarios, see http://www.ietf.org/id/draft-probasco-paws-overview-usecases-00.txthttp://www.ietf.org/id/draft-probasco-paws-overview-usecases-00.txt –Draft charter, see http://www.ietf.org/mail-archive/web/paws/current/msg00109.htmlhttp://www.ietf.org/mail-archive/web/paws/current/msg00109.html Also see Gabor’s 11af submission, https://mentor.ieee.org/802.11/dcn/11/11-11- 0438-00-00af-ietf-paws.pptxhttps://mentor.ieee.org/802.11/dcn/11/11-11- 0438-00-00af-ietf-paws.pptx IESG considering formation of the paws Working Group, Decision May 12 th –Work to refine charter is underway –Likely preference for re-use of existing IETF protocols

4. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 4 Handover Keying (HOKEY) Hokey Charter available at http://www.ietf.org/html.charters/hokey-charter.htmlhttp://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 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.txthttp://www.ietf.org/rfc/rfc5295.txt –EAP Extensions for EAP Re-authentication Protocol (ERP), see http://www.ietf.org/rfc/rfc5296.txt 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] http://www.ietf.org/rfc/rfc5749.txt –Extensible Authentication Protocol (EAP) Early Authentication Problem Statement, see http://tools.ietf.org/html/rfc5836 [published April 2010] http://tools.ietf.org/html/rfc5836 Updates [May 2011] –EAP extensions for EAP Re-authentication protocol, see https://datatracker.ietf.org/doc/draft- ietf-hokey-rfc5296bis/https://datatracker.ietf.org/doc/draft- ietf-hokey-rfc5296bis/ –Architecture design, see https://datatracker.ietf.org/doc/draft-ietf-hokey-arch-design/https://datatracker.ietf.org/doc/draft-ietf-hokey-arch-design/ –EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK) http://datatracker.ietf.org/doc/draft-ietf-hokey-erp-aak/ http://datatracker.ietf.org/doc/draft-ietf-hokey-erp-aak/ –ERP Local Domain Name DHCPv6 Option, see http://datatracker.ietf.org/doc/draft-ietf-hokey- ldn-discovery/http://datatracker.ietf.org/doc/draft-ietf-hokey- ldn-discovery/

5. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 5 Update: EAP Method Update (EMU) Working Group website: http://www.ietf.org/html.charters/emu-charter.htmlhttp://www.ietf.org/html.charters/emu-charter.html Updates [May 2011]: –Channel Binding Support for EAP Methods, http://datatracker.ietf.org/doc/draft-ietf-emu- chbind/http://datatracker.ietf.org/doc/draft-ietf-emu- chbind/ –Requirements for a Tunnel based EAP method, see http://datatracker.ietf.org/doc/draft-ietf- emu-eaptunnel-req/http://datatracker.ietf.org/doc/draft-ietf- emu-eaptunnel-req/ –Decision to base Standard Tunnel based EAP method on http://datatracker.ietf.org/doc/draft- zhou-emu-eap-fastv2/http://datatracker.ietf.org/doc/draft- zhou-emu-eap-fastv2/

6. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 6 6LOWPAN Working Group Working Group website: http://datatracker.ietf.org/wg/6lowpan/charter/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/http://datatracker.ietf.org/doc/draft- ietf-6lowpan-hc/ –Neighbor discovery protocol modifications http://datatracker.ietf.org/doc/draft- ietf-6lowpan-nd/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.pdfhttps://mentor.ieee.org/802-ec/dcn/10/ec-10-0013-00-00EC-smart-grid- information-update-july-2010.pdf Updates [May 2011] –Design and Application Spaces (Use Cases), see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-usecases/ http://datatracker.ietf.org/doc/draft-ietf-6lowpan-usecases/ –Problem Statement and Requirements for 6LOWPAN, see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-routing-requirements/ http://datatracker.ietf.org/doc/draft-ietf-6lowpan-routing-requirements/ –Transmission of IPv6 packets over Bluetooth Low Energy, see http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/

7. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 7 ROLL Working Group Working Group website: http://datatracker.ietf.org/wg/roll/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/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/ 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.pdfhttps://mentor.ieee.org/802-ec/dcn/10/ec-10-0013-00-00EC-smart-grid- information-update-july-2010.pdf Updates [May 2011] –A Security Framework for Routing over Low Power and Lossy Networks, see http://datatracker.ietf.org/doc/draft-ietf-roll-security-framework/http://datatracker.ietf.org/doc/draft-ietf-roll-security-framework/ –RFC 6206, The Trickle Algorithm, allows nodes in a lossy shared medium (e.g., low-power and lossy networks) to exchange information in a highly robust, energy efficient, simple, and scalable manner.

8. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 8 CORE Working Group CORE ( Constrained RESTful Environments) Working Group website: http://datatracker.ietf.org/wg/core/http://datatracker.ietf.org/wg/core/ Focus: framework for resource-oriented applications intended to run on constrained IP networks –Constrained Application Protocol, see http://datatracker.ietf.org/doc/draft-ietf-core- coap/http://datatracker.ietf.org/doc/draft-ietf-core- coap/ Updates [May 2011] –Security Bootstrapping of Resource-Constrained Devices, see http://tools.ietf.org/html/draft-sarikaya-core-sbootstrapping-01 http://tools.ietf.org/html/draft-sarikaya-core-sbootstrapping-01 –Blockwise transfers in CoAP, see http://datatracker.ietf.org/doc/draft-ietf-core- block/http://datatracker.ietf.org/doc/draft-ietf-core- block/ –Core link format, see http://datatracker.ietf.org/doc/draft-ietf-core-link-format/http://datatracker.ietf.org/doc/draft-ietf-core-link-format/ –Observing Resources in CoAP, see http://datatracker.ietf.org/doc/draft-ietf-core- observe/http://datatracker.ietf.org/doc/draft-ietf-core- observe/

9. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 9 Emergency Context Resolution with Internet Technologies (ECRIT) Working Group website: http://www.ietf.org/dyn/wg/charter/ecrit- charter.htmlhttp://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-12.txt http://www.ietf.org/id/draft-ietf-ecrit-framework-12.txt –Unauthenticated access being discussed, see http://tools.ietf.org/id/draft- schulzrinne-ecrit-unauthenticated-access-08.txthttp://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.txthttp://tools.ietf.org/id/draft- thomson-ecrit-civic-boundary-01.txt Updates [May 2011] –Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices, see http://www.ietf.org/id/draft-ietf- ecrit-unauthenticated-access-02.txthttp://www.ietf.org/id/draft-ietf- ecrit-unauthenticated-access-02.txt –Best Current Practice for Communications Services in support of Emergency Calling, see http://datatracker.ietf.org/doc/draft-ietf-ecrit-phonebcp/http://datatracker.ietf.org/doc/draft-ietf-ecrit-phonebcp/

10. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 10 IETF Geographic Location and Privacy (Geopriv) WG See http://www.ietf.org/html.charters/geopriv-charter.htmlhttp://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.txthttp://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.txthttp://www.ietf.org/rfc/rfc3693.txt –Civic Address definitions, see http://www.ietf.org/rfc/rfc4776.txthttp://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.dochttps://mentor.ieee.org/802.11/dcn/09/11-09-0718-01-000v-liaison-request-to-ietf- geopriv.doc Updates [May 2011] –Location-related measurements in Location Configuration Protocols, see https://datatracker.ietf.org/doc/draft-ietf-geopriv-held-measurements/ https://datatracker.ietf.org/doc/draft-ietf-geopriv-held-measurements/ –DHCP Options for LCI, see https://datatracker.ietf.org/doc/draft-ietf-geopriv-rfc3825bis/https://datatracker.ietf.org/doc/draft-ietf-geopriv-rfc3825bis/ –Relative Location, see http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/http://datatracker.ietf.org/doc/draft-ietf-geopriv-relative-location/ –Location Information Server (LIS) Discovery using IP address and Reverse DNS, see http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/ http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/

11. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 11 Mobility EXTensions for IPv6(mext) WG See https://datatracker.ietf.org/wg/mext/charter/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 by continuing work on developments that are required for wide-scale deployments and specific deployment scenarios. –Additionally, the working group will ensure that any issues identified by implementation and interoperability experience are addressed, and that the base specifications are maintained. –The group will also produce informational documentation, such as design rationale documents or description of specific issues within the protocol. –The MEXT WG will also explore experimental alternative security mechanisms. The security mechanism specified in the existing standard track RFCs (RFC3775bis, RFC4877) remains the mandatory to implement mechanism that guarantees interoperability between different implementations. –The MEXT WG is chartered to deliver one or more experimental alternative mechanisms. All the alternative solutions will be published as experimental RFCs. Updates [May 2011 – no change] –TLS-based Mobile IPv6 Security Framework for Mobile Node to Home Agent Communication, see https://datatracker.ietf.org/doc/draft-korhonen-mext-mip6-altsec/https://datatracker.ietf.org/doc/draft-korhonen-mext-mip6-altsec/ –Home Agent Reliability Protocol, see https://datatracker.ietf.org/doc/draft-ietf-mip6- hareliability/https://datatracker.ietf.org/doc/draft-ietf-mip6- hareliability/

12. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 12 IETF Meetings Meetings: –July 24-29, 2011Quebec City –November 13-18, 2011 Taipei –March 25-30, 2012 Paris –July 29 – August 3, 2012 Vancouver –November 4-9, 2012 Atlanta http://www.ietf.org

13. doc.: IEEE 802.11-11/0691r0 Submission May 2011 Dorothy Stanley, Aruba NetworksSlide 13 References RFC 4017 - IEEE 802.11 Requirements on EAP Methods