--- 1/draft-ietf-ipwave-ipv6-over-80211ocb-15.txt 2018-02-14 02:13:08.507707322 -0800 +++ 2/draft-ietf-ipwave-ipv6-over-80211ocb-16.txt 2018-02-14 02:13:08.587709205 -0800 @@ -1,26 +1,26 @@ Network Working Group A. Petrescu Internet-Draft CEA, LIST Intended status: Standards Track N. Benamar -Expires: August 17, 2018 Moulay Ismail University +Expires: August 18, 2018 Moulay Ismail University J. Haerri Eurecom J. Lee Sangmyung University T. Ernst YoGoKo - February 13, 2018 + February 14, 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-15.txt + draft-ietf-ipwave-ipv6-over-80211ocb-16.txt 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 August 17, 2018. + This Internet-Draft will expire on August 18, 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 @@ -75,34 +75,34 @@ 4.5. Stateless Autoconfiguration . . . . . . . . . . . . . . . 8 4.6. Subnet Structure . . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 9.2. Informative References . . . . . . . . . . . . . . . . . 14 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 16 - Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 22 + 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 - F.2. Reliability Requirements . . . . . . . . . . . . . . . . 29 + F.2. Reliability Requirements . . . . . . . . . . . . . . . . 30 F.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 30 F.4. MAC Address Generation . . . . . . . . . . . . . . . . . 31 Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 31 - Appendix H. Implementation Status . . . . . . . . . . . . . . . 31 - H.1. Capture in Monitor 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 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 @@ -131,22 +131,20 @@ In the published literature, many documents describe aspects and problems related to running IPv6 over 802.11-OCB: [I-D.ietf-ipwave-vehicular-networking-survey]. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. - WiFi: Wireless Fidelity. - IP-OBU (Internet Protocol On-Board Unit): an IP-OBU is a computer situated in a vehicle such as an automobile, bicycle, or similar. It has at least one IP interface that runs in mode OCB of 802.11, and that has an "OBU" transceiver. See the definition of the term "OBU" in section Appendix I. IP-RSU (IP Road-Side Unit): an IP-RSU is situated along the road. An IP-RSU has at least two distinct IP-enabled interfaces; at least one interface is operated in mode OCB of IEEE 802.11 and is IP-enabled. An IP-RSU is similar to a Wireless Termination Point (WTP), as @@ -193,40 +191,40 @@ 4.1. Maximum Transmission Unit (MTU) The default MTU for IP packets on 802.11-OCB MUST be 1500 octets. It is the same value as IPv6 packets on Ethernet links, as specified in [RFC2464]. This value of the MTU respects the recommendation that every link on the Internet must have a minimum MTU of 1280 octets (stated in [RFC8200], and the recommendations therein, especially with respect to fragmentation). If IPv6 packets of size larger than 1500 bytes are sent on an 802.11-OCB interface card then the IP stack - will fragment. In case there are IP fragments, the field "Sequence - number" of the 802.11 Data header containing the IP fragment field is - increased. + MUST fragment. In case there are IP fragments, the field "Sequence + number" of the 802.11 Data header containing the IP fragment field + MUST be increased. Non-IP packets such as WAVE Short Message Protocol (WSMP) can be delivered on 802.11-OCB links. Specifications of these packets are out of scope of this document, and do not impose any limit on the MTU size, allowing an arbitrary number of 'containers'. Non-IP packets such as ETSI GeoNetworking packets have an MTU of 1492 bytes. The operation of IPv6 over GeoNetworking is specified at [ETSI-IPv6-GeoNetworking]. 4.2. Frame Format IP packets are transmitted over 802.11-OCB as standard Ethernet packets. As with all 802.11 frames, an Ethernet adaptation layer is used with 802.11-OCB as well. This Ethernet Adaptation Layer performing 802.11-to-Ethernet is described in Section 4.2.1. The - Ethernet Type code (EtherType) for IPv6 is 0x86DD (hexadecimal 86DD, - or otherwise #86DD). + Ethernet Type code (EtherType) for IPv6 MUST be 0x86DD (hexadecimal + 86DD, or otherwise #86DD). The Frame format for transmitting IPv6 on 802.11-OCB networks is the same as transmitting IPv6 on Ethernet networks, and is described in section 3 of [RFC2464]. 1 0 0 0 0 1 1 0 1 1 0 1 1 1 0 1 is the binary representation of the EtherType value 0x86DD. 4.2.1. Ethernet Adaptation Layer @@ -302,29 +300,29 @@ mode. The placement of IPv6 networking layer on Ethernet Adaptation Layer is illustrated in Figure 3. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv6 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Ethernet Adaptation Layer | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | 802.11 WiFi MAC | + | 802.11 MAC | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | 802.11 WiFi PHY | + | 802.11 PHY | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: Ethernet Adaptation Layer stacked with other layers - (in the above figure, a WiFi profile is represented; this is used - also for OCB profile.) + (in the above figure, a 802.11 profile is represented; this is used + also for 802.11 OCB profile.) Other alternative views of layering are EtherType Protocol Discrimination (EPD), see Appendix E, and SNAP see [RFC1042]. 4.3. Link-Local Addresses The link-local address of an 802.11-OCB interface is formed in the same manner as on an Ethernet interface. This manner is described in section 5 of [RFC2464]. Additionally, if stable identifiers are needed, it is recommended to follow the Recommendation on Stable IPv6 @@ -497,23 +495,23 @@ 8. Acknowledgements 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 and William Whyte. Their valuable - comments clarified particular issues and generally helped to improve - the document. + Margaret Cullen, Erik Kline, Carlos Jesus Bernardos Cano 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 @@ -714,20 +712,31 @@ 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. + From draft-ietf-ipwave-ipv6-over-80211ocb-15 to draft-ietf-ipwave- + ipv6-over-80211ocb-16 + + o Removed the definition of the 'WiFi' term and its occurences. + Clarified a phrase that used it in Appendix C "Aspects introduced + by the OCB mode to 802.11". + + o Added more normative words: MUST be 0x86DD, MUST fragment if size + larger than MTU, Sequence number in 802.11 Data header MUST be + increased. + From draft-ietf-ipwave-ipv6-over-80211ocb-14 to draft-ietf-ipwave- ipv6-over-80211ocb-15 o Added normative term MUST in two places in section "Ethernet Adaptation Layer". From draft-ietf-ipwave-ipv6-over-80211ocb-13 to draft-ietf-ipwave- ipv6-over-80211ocb-14 o Created a new Appendix titled "Extra Terminology" that contains @@ -1128,24 +1137,24 @@ While 'p' is a letter identifying the Ammendment, just like 'a, b, g' and 'n' are, 'p' is concerned more with MAC modifications, and a little with PHY modifications; the others are mainly about PHY modifications. It is possible in practice to combine a 'p' MAC with an 'a' PHY by operating outside the context of a BSS with OFDM at 5.4GHz and 5.9GHz. The 802.11-OCB links are specified to be compatible as much as possible with the behaviour of 802.11a/b/g/n and future generation IEEE WLAN links. From the IP perspective, an 802.11-OCB MAC layer - offers practically the same interface to IP as the WiFi and Ethernet - layers do (802.11a/b/g/n and 802.3). A packet sent by an IP-OBU may - be received by one or multiple IP-RSUs. The link-layer resolution is - performed by using the IPv6 Neighbor Discovery protocol. + offers practically the same interface to IP as the 802.11a/b/g/n and + 802.3. A packet sent by an IP-OBU may be received by one or multiple + IP-RSUs. The link-layer resolution is performed by using the IPv6 + Neighbor Discovery protocol. To support this similarity statement (IPv6 is layered on top of LLC on top of 802.11-OCB, in the same way that IPv6 is layered on top of LLC on top of 802.11a/b/g/n (for WLAN) or layered on top of LLC on top of 802.3 (for Ethernet)) it is useful to analyze the differences between 802.11-OCB and 802.11 specifications. During this analysis, we note that whereas 802.11-OCB lists relatively complex and numerous changes to the MAC layer (and very little to the PHY layer), there are only a few characteristics which may be important for an implementation transmitting IPv6 packets on 802.11-OCB links.