--- 1/draft-ietf-ipwave-ipv6-over-80211ocb-24.txt 2018-06-20 07:14:14.160446820 -0700 +++ 2/draft-ietf-ipwave-ipv6-over-80211ocb-25.txt 2018-06-20 07:14:14.244448834 -0700 @@ -1,26 +1,26 @@ IPWAVE Working Group A. Petrescu Internet-Draft CEA, LIST Intended status: Standards Track N. Benamar -Expires: December 17, 2018 Moulay Ismail University +Expires: December 21, 2018 Moulay Ismail University J. Haerri Eurecom J. Lee Sangmyung University T. Ernst YoGoKo - June 15, 2018 + June 19, 2018 Transmission of IPv6 Packets over IEEE 802.11 Networks operating in mode Outside the Context of a Basic Service Set (IPv6-over-80211-OCB) - draft-ietf-ipwave-ipv6-over-80211ocb-24 + draft-ietf-ipwave-ipv6-over-80211ocb-25 Abstract In order to transmit IPv6 packets on IEEE 802.11 networks running outside the context of a basic service set (OCB, earlier "802.11p") there is a need to define a few parameters such as the supported Maximum Transmission Unit size on the 802.11-OCB link, 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 @@ -35,21 +35,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 https://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 December 17, 2018. + This Internet-Draft will expire on December 21, 2018. Copyright Notice Copyright (c) 2018 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -78,44 +78,45 @@ 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . 13 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 15 Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 23 Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 23 Appendix D. Changes Needed on a software driver 802.11a to - become a 802.11-OCB driver . . . 27 - Appendix E. EtherType Protocol Discrimination (EPD) . . . . . . 28 - Appendix F. Design Considerations . . . . . . . . . . . . . . . 29 - F.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 29 + become a 802.11-OCB driver . . . 28 + Appendix E. EtherType Protocol Discrimination (EPD) . . . . . . 29 + Appendix F. Design Considerations . . . . . . . . . . . . . . . 30 + F.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 30 F.2. Reliability Requirements . . . . . . . . . . . . . . . . 30 - F.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 30 - F.4. MAC Address Generation . . . . . . . . . . . . . . . . . 31 + F.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 31 + F.4. MAC Address Generation . . . . . . . . . . . . . . . . . 32 - Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 31 + Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 32 Appendix H. Implementation Status . . . . . . . . . . . . . . . 32 H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 33 - H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 35 - Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 37 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 + H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 36 + Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 38 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 1. Introduction This document describes the transmission of IPv6 packets on IEEE Std 802.11-OCB networks [IEEE-802.11-2016] (a.k.a "802.11p" see - Appendix B). 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 expected - to IEEE Std 802.11 MAC and Logical Link sublayers: IPv6 works fine - directly over 802.11-OCB too, with an LLC layer. + Appendix B, Appendix C and Appendix D). 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 expected to IEEE Std 802.11 MAC and Logical Link + sublayers: IPv6 works fine directly over 802.11-OCB too, with an LLC + layer. The IPv6 network layer operates on 802.11-OCB in the same manner as operating on Ethernet, but there are two kinds of exceptions: o Exceptions due to different operation of IPv6 network layer on 802.11 than on Ethernet. To satisfy these exceptions, this document describes an Ethernet Adaptation Layer between Ethernet headers and 802.11 headers. The Ethernet Adaptation Layer is described Section 4.2.1. The operation of IP on Ethernet is described in [RFC1042], [RFC2464] and @@ -308,23 +309,24 @@ Transmitting IPv6 packets to multicast destinations over 802.11 links proved to have some performance issues [I-D.perkins-intarea-multicast-ieee802]. These issues may be exacerbated in OCB mode. Solutions for these problems should consider the OCB mode of operation. 4.5. Stateless Autoconfiguration The Interface Identifier for an 802.11-OCB interface is formed using the same rules as the Interface Identifier for an Ethernet interface; - this is described in section 4 of [RFC2464]. No changes are needed, - but some care must be taken when considering the use of the Stateless - Address Auto-Configuration procedure. + the RECOMMENDED method for forming stable Interface Identifiers + (IIDs) is described in [RFC8064]. The method of forming IIDs + described in section 4 of [RFC2464] MAY be used during transition + time. The bits in the interface identifier have no generic meaning and the identifier should be treated as an opaque value. The bits 'Universal' and 'Group' in the identifier of an 802.11-OCB interface are significant, as this is an IEEE link-layer address. The details of this significance are described in [RFC7136]. As with all Ethernet and 802.11 interface identifiers ([RFC7721]), the identifier of an 802.11-OCB interface may involve privacy, MAC address spoofing and IP address hijacking risks. A vehicle embarking @@ -445,23 +447,24 @@ The authors would like to thank Witold Klaudel, Ryuji Wakikawa, Emmanuel Baccelli, John Kenney, John Moring, Francois Simon, Dan Romascanu, Konstantin Khait, Ralph Droms, Richard 'Dick' Roy, Ray Hunter, Tom Kurihara, Michal Sojka, Jan de Jongh, Suresh Krishnan, Dino Farinacci, Vincent Park, Jaehoon Paul Jeong, Gloria Gwynne, Hans-Joachim Fischer, Russ Housley, Rex Buddenberg, Erik Nordmark, Bob Moskowitz, Andrew Dryden, Georg Mayer, Dorothy Stanley, Sandra Cespedes, Mariano Falcitelli, Sri Gundavelli, Abdussalam Baryun, Margaret Cullen, Erik Kline, Carlos Jesus Bernardos Cano, Ronald in - 't Velt, Katrin Sjoberg, Roland Bless, Russ Housley, Tijink Jasja, - Kevin Smith and William Whyte. Their valuable comments clarified - particular issues and generally helped to improve the document. + 't Velt, Katrin Sjoberg, Roland Bless, Tijink Jasja, Kevin Smith, + Brian Carpenter, Julian Reschke, Mikael Abrahamsson and William + Whyte. Their valuable comments clarified particular issues and + generally helped to improve the document. Pierre Pfister, Rostislav Lisovy, and others, wrote 802.11-OCB drivers for linux and described how. For the multicast discussion, the authors would like to thank Owen DeLong, Joe Touch, Jen Linkova, Erik Kline, Brian Haberman and participants to discussions in network working groups. The authors would like to thank participants to the Birds-of- a-Feather "Intelligent Transportation Systems" meetings held at IETF @@ -646,20 +649,26 @@ document freely available at URL http://standards.ieee.org/getieee802/ download/802.11p-2010.pdf retrieved on September 20th, 2013.". Appendix A. ChangeLog The changes are listed in reverse chronological order, most recent changes appearing at the top of the list. + -25: added a reference to 'IEEE Management Information Base', instead + of just 'Management Information Base'; added ref to further + appendices in the introductory phrases; improved text for IID + formation for SLAAC, inserting recommendation for RFC8064 before + RFC2464. + From draft-ietf-ipwave-ipv6-over-80211ocb-23 to draft-ietf-ipwave- ipv6-over-80211ocb-24 o Nit: wrote "IPWAVE Working Group" on the front page, instead of "Network Working Group". o Addressed the comments on 6MAN: replaced a sentence about ND problem with "is used over 802.11-OCB". From draft-ietf-ipwave-ipv6-over-80211ocb-22 to draft-ietf-ipwave- @@ -1049,26 +1059,26 @@ o Removed mentioning of the GeoNetworking discussion. o Moved references to scientific articles to a separate 'overview' draft, and referred to it. Appendix B. 802.11p The term "802.11p" is an earlier definition. The behaviour of "802.11p" networks is rolled in the document IEEE Std 802.11-2016. In that document the term 802.11p disappears. Instead, each 802.11p - feature is conditioned by the Management Information Base (MIB) - attribute "OCBActivated". Whenever OCBActivated is set to true the - IEEE Std 802.11-OCB state is activated. For example, an 802.11 - STAtion operating outside the context of a basic service set has the - OCBActivated flag set. Such a station, when it has the flag set, - uses a BSS identifier equal to ff:ff:ff:ff:ff:ff. + feature is conditioned by the IEEE Management Information Base (MIB) + attribute "OCBActivated" [IEEE-802.11-2016]. Whenever OCBActivated + is set to true the IEEE Std 802.11-OCB state is activated. For + example, an 802.11 STAtion operating outside the context of a basic + service set has the OCBActivated flag set. Such a station, when it + has the flag set, uses a BSS identifier equal to ff:ff:ff:ff:ff:ff. Appendix C. Aspects introduced by the OCB mode to 802.11 In the IEEE 802.11-OCB mode, all nodes in the wireless range can directly communicate with each other without involving authentication or association procedures. At link layer, it is necessary to set the same channel number (or frequency) on two stations that need to communicate with each other. The manner in which stations set their channel number is not specified in this document. Stations STA1 and STA2 can exchange IP packets if they are set on the same channel. At