--- 1/draft-ietf-ipwave-ipv6-over-80211ocb-03.txt 2017-08-18 09:13:12.286713476 -0700 +++ 2/draft-ietf-ipwave-ipv6-over-80211ocb-04.txt 2017-08-18 09:13:12.354715098 -0700 @@ -1,30 +1,30 @@ Network Working Group A. Petrescu Internet-Draft CEA, LIST Intended status: Standards Track N. Benamar -Expires: November 30, 2017 Moulay Ismail University +Expires: February 18, 2018 Moulay Ismail University J. Haerri Eurecom C. Huitema J. Lee Sangmyung University T. Ernst YoGoKo T. Li Peloton Technology - May 29, 2017 + August 17, 2017 Transmission of IPv6 Packets over IEEE 802.11 Networks in mode Outside the Context of a Basic Service Set (IPv6-over-80211ocb) - draft-ietf-ipwave-ipv6-over-80211ocb-03.txt + draft-ietf-ipwave-ipv6-over-80211ocb-04.txt Abstract In order to transmit IPv6 packets on IEEE 802.11 networks run outside the context of a basic service set (OCB, earlier "802.11p") there is a need to define a few parameters such as the recommended Maximum Transmission Unit size, the header format preceding the IPv6 header, the Type value within it, and others. This document describes these parameters for IPv6 and IEEE 802.11 OCB networks; it portrays the layering of IPv6 on 802.11 OCB similarly to other known 802.11 and @@ -47,21 +47,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 30, 2017. + This Internet-Draft will expire on February 18, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -90,30 +90,30 @@ 6. Example IPv6 Packet captured over a IEEE 802.11-OCB link . . 16 6.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 17 6.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . 23 11.2. Informative References . . . . . . . . . . . . . . . . . 24 - Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 27 + Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 26 Appendix B. Changes Needed on a software driver 802.11a to - become a 802.11-OCB driver . . . 29 + become a 802.11-OCB driver . . . 28 Appendix C. Design Considerations . . . . . . . . . . . . . . . 30 - C.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 31 - C.2. Reliability Requirements . . . . . . . . . . . . . . . . 31 - C.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 32 + C.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 30 + C.2. Reliability Requirements . . . . . . . . . . . . . . . . 30 + C.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 31 C.4. MAC Address Generation . . . . . . . . . . . . . . . . . 32 - Appendix D. IEEE 802.11 Messages Transmitted in OCB mode . . . . 33 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 + Appendix D. IEEE 802.11 Messages Transmitted in OCB mode . . . . 32 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 1. Introduction This document describes the transmission of IPv6 packets on IEEE Std 802.11 OCB networks (earlier known as 802.11p). This involves the layering of IPv6 networking on top of the IEEE 802.11 MAC layer (with an LLC layer). Compared to running IPv6 over the Ethernet MAC layer, there is no modification required to the standards: IPv6 works fine directly over 802.11 OCB too (with an LLC layer). @@ -181,23 +181,23 @@ However, there may be some deployment considerations helping optimize the performances of running IPv6 over 802.11-OCB (e.g. in the case of handovers between 802.11 OCB-enabled access routers, or the consideration of using the IP security layer [RFC4301]). There are currently no specifications for handover between OCB links since these are currently specified as LLC-1 links (i.e. connectionless). Any handovers must be performed above the Data Link Layer. Also, while there is no encryption applied below the network - layer using 802.11p, 1609.2 does provide security services for - applications to use so that there can easily be data security over - the air without invoking IPsec. + layer using 802.11p, 1609.2 [ieee1609.2] does provide security + services for applications to use so that there can easily be data + security over the air without invoking IPsec. We briefly introduce the vehicular communication scenarios where IEEE 802.11-OCB links are used. This is followed by a description of differences in specification terms, between 802.11 OCB and 802.11a/b/g/n (and the same differences expressed in terms of requirements to software implementation are listed in Appendix B.) The document then concentrates on the parameters of layering IP over 802.11 OCB as over Ethernet: value of MTU, the contents of Frame Format, the rules for forming Interface Identifiers, the mechanism @@ -433,22 +433,22 @@ between the IP layer and the MAC layer. o In vehicular communications using 802.11-OCB links, there are strong privacy requirements with respect to addressing. While the 802.11-OCB standard does not specify anything in particular with respect to MAC addresses, in these settings there exists a strong need for dynamic change of these addresses (as opposed to the non- vehicular settings - real wall protection - where fixed MAC addresses do not currently pose some privacy risks). This is further described in section Section 7. A relevant function is - described in IEEE 1609.3-2016, clause 5.5.1 and IEEE 1609.4-2016, - clause 6.7. + described in IEEE 1609.3-2016 [ieee1609.3], clause 5.5.1 and IEEE + 1609.4-2016 [ieee1609.4], clause 6.7. Other aspects particular to 802.11-OCB which are also particular to 802.11 (e.g. the 'hidden node' operation) may have an influence on the use of transmission of IPv6 packets on 802.11-OCB networks. The subnet structure which may be assumed in 802.11-OCB networks is strongly influenced by the mobility of vehicles. 5. Layering of IPv6 over 802.11-OCB as over Ethernet 5.1. Maximum Transmission Unit (MTU) @@ -1039,147 +1039,138 @@ draft-ietf-6man-default-iids-16 (work in progress), September 2016. [I-D.ietf-6man-ug] Carpenter, B. and S. Jiang, "Significance of IPv6 Interface Identifiers", draft-ietf-6man-ug-06 (work in progress), December 2013. [I-D.ietf-tsvwg-ieee-802-11] Szigeti, T., Henry, J., and F. Baker, "Diffserv to IEEE - 802.11 Mapping", draft-ietf-tsvwg-ieee-802-11-03 (work in - progress), May 2017. + 802.11 Mapping", draft-ietf-tsvwg-ieee-802-11-06 (work in + progress), August 2017. [RFC1042] Postel, J. and J. Reynolds, "Standard for the transmission of IP datagrams over IEEE 802 networks", STD 43, RFC 1042, - DOI 10.17487/RFC1042, February 1988, - . + DOI 10.17487/RFC1042, February 1988, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, - . + DOI 10.17487/RFC2119, March 1997, . [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, - December 1998, . + December 1998, . [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, - . + . [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963, DOI 10.17487/RFC3963, January 2005, - . + . [RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, - DOI 10.17487/RFC4086, June 2005, - . + DOI 10.17487/RFC4086, June 2005, . [RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, - December 2005, . + December 2005, . [RFC4429] Moore, N., "Optimistic Duplicate Address Detection (DAD) for IPv6", RFC 4429, DOI 10.17487/RFC4429, April 2006, - . + . [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, - DOI 10.17487/RFC4861, September 2007, - . + DOI 10.17487/RFC4861, September 2007, . [RFC5889] Baccelli, E., Ed. and M. Townsley, Ed., "IP Addressing Model in Ad Hoc Networks", RFC 5889, DOI 10.17487/RFC5889, - September 2010, . + September 2010, . [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July - 2011, . + 2011, . [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. Bormann, "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC 6775, DOI 10.17487/RFC6775, November 2012, - . + . [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy Considerations for IPv6 Address Generation Mechanisms", RFC 7721, DOI 10.17487/RFC7721, March 2016, - . + . 11.2. Informative References - [etsi-302663-v1.2.1p-2013] - "Intelligent Transport Systems (ITS); Access layer - specification for Intelligent Transport Systems operating - in the 5 GHz frequency band, 2013-07, document - en_302663v010201p.pdf, document freely available at URL - http://www.etsi.org/deliver/etsi_en/302600_302699/302663/ - 01.02.01_60/en_302663v010201p.pdf downloaded on October - 17th, 2013.". - - [etsi-draft-102492-2-v1.1.1-2006] - "Electromagnetic compatibility and Radio spectrum Matters - (ERM); Intelligent Transport Systems (ITS); Part 2: - Technical characteristics for pan European harmonized - communications equipment operating in the 5 GHz frequency - range intended for road safety and traffic management, and - for non-safety related ITS applications; System Reference - Document, Draft ETSI TR 102 492-2 V1.1.1, 2006-07, - document tr_10249202v010101p.pdf freely available at URL - http://www.etsi.org/deliver/etsi_tr/102400_102499/ - 10249202/01.01.01_60/tr_10249202v010101p.pdf downloaded on - October 18th, 2013.". - [fcc-cc] "'Report and Order, Before the Federal Communications Commission Washington, D.C. 20554', FCC 03-324, Released on February 10, 2004, document FCC-03-324A1.pdf, document freely available at URL http://www.its.dot.gov/exit/fcc_edocs.htm downloaded on October 17th, 2013.". [fcc-cc-172-184] "'Memorandum Opinion and Order, Before the Federal Communications Commission Washington, D.C. 20554', FCC 06-10, Released on July 26, 2006, document FCC- 06-110A1.pdf, document freely available at URL http://hraunfoss.fcc.gov/edocs_public/attachmatch/ FCC-06-110A1.pdf downloaded on June 5th, 2014.". [I-D.jeong-ipwave-vehicular-networking-survey] Jeong, J., Cespedes, S., Benamar, N., Haerri, J., and M. Wetterwald, "Survey on IP-based Vehicular Networking for Intelligent Transportation Systems", draft-jeong-ipwave- - vehicular-networking-survey-02 (work in progress), March + vehicular-networking-survey-03 (work in progress), June 2017. [I-D.perkins-intarea-multicast-ieee802] Perkins, C., Stanley, D., Kumari, W., and J. Zuniga, "Multicast Considerations over IEEE 802 Wireless Media", - draft-perkins-intarea-multicast-ieee802-02 (work in - progress), March 2017. + draft-perkins-intarea-multicast-ieee802-03 (work in + progress), July 2017. [I-D.petrescu-its-scenarios-reqs] Petrescu, A., Janneteau, C., Boc, M., and W. Klaudel, "Scenarios and Requirements for IP in Intelligent Transportation Systems", draft-petrescu-its-scenarios- reqs-03 (work in progress), October 2013. - [ieee16094] - "1609.2-2016 - IEEE Standard for Wireless Access in - Vehicular Environments--Security Services for Applications - and Management Messages; document freely available at URL - https://standards.ieee.org/findstds/ - standard/1609.2-2016.html retrieved on July 08th, 2016.". + [ieee1609.2] + "IEEE SA - 1609.2-2016 - IEEE Standard for Wireless Access + in Vehicular Environments (WAVE) -- Security Services for + Applications and Management Messages. Example URL + http://ieeexplore.ieee.org/document/7426684/ accessed on + August 17th, 2017.". + + [ieee1609.3] + "IEEE SA - 1609.3-2016 - IEEE Standard for Wireless Access + in Vehicular Environments (WAVE) -- Networking Services. + Example URL http://ieeexplore.ieee.org/document/7458115/ + accessed on August 17th, 2017.". + + [ieee1609.4] + "IEEE SA - 1609.4-2016 - IEEE Standard for Wireless Access + in Vehicular Environments (WAVE) -- Multi-Channel + Operation. Example URL + http://ieeexplore.ieee.org/document/7435228/ accessed on + August 17th, 2017.". [ieee802.11-2012] "802.11-2012 - IEEE Standard for Information technology-- Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. Downloaded on October 17th, 2013, from IEEE Standards, document freely available at URL http://standards.ieee.org/findstds/ @@ -1191,58 +1182,36 @@ Technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 6: Wireless Access in Vehicular Environments; document freely available at URL http://standards.ieee.org/getieee802/ download/802.11p-2010.pdf retrieved on September 20th, 2013.". - [ieeep1609.0-D2] - "IEEE P1609.0/D2 Draft Guide for Wireless Access in - Vehicular Environments (WAVE) Architecture. pdf, length - 879 Kb. Restrictions apply.". +Appendix A. ChangeLog - [ieeep1609.2-D17] - "IEEE P1609.2(tm)/D17 Draft Standard for Wireless Access - in Vehicular Environments - Security Services for - Applications and Management Messages. pdf, length 2558 - Kb. Restrictions apply.". + The changes are listed in reverse chronological order, most recent + changes appearing at the top of the list. - [ieeep1609.3-D9-2010] - "IEEE P1609.3(tm)/D9, Draft Standard for Wireless Access - in Vehicular Environments (WAVE) - Networking Services, - August 2010. Authorized licensed use limited to: CEA. - Downloaded on June 19, 2013 at 07:32:34 UTC from IEEE - Xplore. Restrictions apply, document at persistent link - http://ieeexplore.ieee.org/servlet/opac?punumber=5562705". + From draft-ietf-ipwave-ipv6-over-80211ocb-03 to draft-ietf-ipwave- + ipv6-over-80211ocb-04 - [ieeep1609.4-D9-2010] - "IEEE P1609.4(tm)/D9 Draft Standard for Wireless Access in - Vehicular Environments (WAVE) - Multi-channel Operation. - Authorized licensed use limited to: CEA. Downloaded on - June 19, 2013 at 07:34:48 UTC from IEEE Xplore. - Restrictions apply. Document at persistent link - http://ieeexplore.ieee.org/servlet/opac?punumber=5551097". + o Removed a few informative references pointing to Dx draft IEEE + 1609 documents. - [TS103097] - "Intelligent Transport Systems (ITS); Security; Security - header and certificate formats; document freely available - at URL http://www.etsi.org/deliver/ - etsi_ts/103000_103099/103097/01.01.01_60/ - ts_103097v010101p.pdf retrieved on July 08th, 2016.". + o Removed outdated informative references to ETSI documents. -Appendix A. ChangeLog + o Added citations to IEEE 1609.2, .3 and .4-2016. - The changes are listed in reverse chronological order, most recent - changes appearing at the top of the list. + o Minor textual issues. From draft-ietf-ipwave-ipv6-over-80211ocb-02 to draft-ietf-ipwave- ipv6-over-80211ocb-03 o Keep the previous text on multiple addresses, so remove talk about MIP6, NEMOv6 and MCoA. o Clarified that a 'Beacon' is an IEEE 802.11 frame Beacon. o Clarified the figure showing Infrastructure mode and OCB mode side @@ -1394,23 +1363,23 @@ strong link asymetry and very short connection makes the 802.11-OCB link significantly different from other 802.11 networks. Also, the automotive applications have specific requirements for reliability, security and privacy, which further add to the particularity of the 802.11-OCB link. C.1. Vehicle ID Automotive networks require the unique representation of each of their node. Accordingly, a vehicle must be identified by at least - one unique ID. The current specification at ETSI and at IEEE 1609 - identifies a vehicle by its MAC address uniquely obtained from the - 802.11-OCB NIC. + one unique identifier. The current specification at ETSI and at IEEE + 1609 identifies a vehicle by its MAC address uniquely obtained from + the 802.11-OCB NIC. A MAC address uniquely obtained from a IEEE 802.11-OCB NIC implicitely generates multiple vehicle IDs in case of multiple 802.11-OCB NICs. A mechanims to uniquely identify a vehicle irrespectively to the different NICs and/or technologies is required. C.2. Reliability Requirements The dynamically changing topology, short connectivity, mobile transmitter and receivers, different antenna heights, and many-to-