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

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/