draft-ietf-ipwave-ipv6-over-80211ocb-20.txt   draft-ietf-ipwave-ipv6-over-80211ocb-21.txt 
Network Working Group A. Petrescu Network 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: September 3, 2018 Moulay Ismail University Expires: September 4, 2018 Moulay Ismail University
J. Haerri J. Haerri
Eurecom Eurecom
J. Lee J. Lee
Sangmyung University Sangmyung University
T. Ernst T. Ernst
YoGoKo YoGoKo
March 2, 2018 March 3, 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-20.txt draft-ietf-ipwave-ipv6-over-80211ocb-21.txt
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 September 3, 2018. This Internet-Draft will expire on September 4, 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 6, line 5 skipping to change at page 6, line 5
An Ethernet Adaptation Layer makes an 802.11 MAC look to IP An Ethernet Adaptation Layer makes an 802.11 MAC look to IP
Networking layer as a more traditional Ethernet layer. At reception, Networking layer as a more traditional Ethernet layer. At reception,
this layer takes as input the IEEE 802.11 header and the Logical-Link this layer takes as input the IEEE 802.11 header and the Logical-Link
Layer Control Header and produces an Ethernet II Header. At sending, Layer Control Header and produces an Ethernet II Header. At sending,
the reverse operation is performed. the reverse operation is performed.
The operation of the Ethernet Adaptation Layer is depicted by the The operation of the Ethernet Adaptation Layer is depicted by the
double arrow in Figure 1. double arrow in Figure 1.
+--------------------+------------+-------------+---------+-----------+ +------------------+------------+-------------+---------+-----------+
| 802.11 header | LLC Header | IPv6 Header | Payload |.11 Trailer| | 802.11 header | LLC Header | IPv6 Header | Payload |.11 Trailer|
+--------------------+------------+-------------+---------+-----------+ +------------------+------------+-------------+---------+-----------+
\ / \ / \ / \ /
----------------------------- -------- --------------------------- --------
\---------------------------------------------/ \---------------------------------------------/
^ ^
| |
802.11-to-Ethernet Adaptation Layer 802.11-to-Ethernet Adaptation Layer
| |
v v
+---------------------+-------------+---------+ +---------------------+-------------+---------+
| Ethernet II Header | IPv6 Header | Payload | | Ethernet II Header | IPv6 Header | Payload |
+---------------------+-------------+---------+ +---------------------+-------------+---------+
Figure 1: Operation of the Ethernet Adaptation Layer Figure 1: Operation of the Ethernet Adaptation Layer
The Receiver and Transmitter Address fields in the 802.11 header MUST The Receiver and Transmitter Address fields in the 802.11 header MUST
contain the same values as the Destination and the Source Address contain the same values as the Destination and the Source Address
fields in the Ethernet II Header, respectively. The value of the fields in the Ethernet II Header, respectively. The value of the
Type field in the LLC Header MUST be the same as the value of the Type field in the LLC Header MUST be the same as the value of the
Type field in the Ethernet II Header. Type field in the Ethernet II Header.
The ".11 Trailer" contains solely a 4-byte Frame Check Sequence. The ".11 Trailer" contains solely a 4-byte Frame Check Sequence.
The specification of which type or subtype of 802.11 headers are used The specification of which type or subtype of 802.11 headers are used
to transmit IP packets is left outside the scope of this document. to transmit IP packets is left outside the scope of this document.
The placement of IPv6 networking layer on Ethernet Adaptation Layer The placement of IPv6 networking layer on Ethernet Adaptation Layer
is illustrated in Figure 2. is illustrated in Figure 2.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 | | IPv6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ethernet Adaptation Layer | | Ethernet Adaptation Layer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 802.11 MAC | | 802.11 MAC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 802.11 PHY | | 802.11 PHY |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Ethernet Adaptation Layer stacked with other layers Figure 2: Ethernet Adaptation Layer stacked with other layers
(in the above figure, a 802.11 profile is represented; this is used (in the above figure, a 802.11 profile is represented; this is used
also for 802.11 OCB profile.) also for 802.11 OCB profile.)
Other alternative views of layering are EtherType Protocol Other alternative views of layering are EtherType Protocol
Discrimination (EPD), see Appendix E, and SNAP see [RFC1042]. Discrimination (EPD), see Appendix E, and SNAP see [RFC1042].
4.3. Link-Local Addresses 4.3. Link-Local Addresses
skipping to change at page 10, line 37 skipping to change at page 10, line 37
document. document.
8. Acknowledgements 8. Acknowledgements
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 and William Margaret Cullen, Erik Kline, Carlos Jesus Bernardos Cano, Ronald in
Whyte. Their valuable comments clarified particular issues and 't Velt, Katrin Sjoberg, Roland Bless and William Whyte. Their
generally helped to improve the document. 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 14, line 5 skipping to change at page 14, line 5
over Ethernet Networks", draft-hinden-6man-rfc2464bis-02 over Ethernet Networks", draft-hinden-6man-rfc2464bis-02
(work in progress), March 2017. (work in progress), March 2017.
[I-D.ietf-ipwave-vehicular-networking-survey] [I-D.ietf-ipwave-vehicular-networking-survey]
Jeong, J., Cespedes, S., Benamar, N., Haerri, J., and M. Jeong, J., Cespedes, S., Benamar, N., Haerri, J., and M.
Wetterwald, "Survey on IP-based Vehicular Networking for Wetterwald, "Survey on IP-based Vehicular Networking for
Intelligent Transportation Systems", draft-ietf-ipwave- Intelligent Transportation Systems", draft-ietf-ipwave-
vehicular-networking-survey-00 (work in progress), July vehicular-networking-survey-00 (work in progress), July
2017. 2017.
[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-11 (work in
progress), December 2017.
[I-D.perkins-intarea-multicast-ieee802] [I-D.perkins-intarea-multicast-ieee802]
Perkins, C., Stanley, D., Kumari, W., and J. Zuniga, Perkins, C., Stanley, D., Kumari, W., and J. Zuniga,
"Multicast Considerations over IEEE 802 Wireless Media", "Multicast Considerations over IEEE 802 Wireless Media",
draft-perkins-intarea-multicast-ieee802-03 (work in draft-perkins-intarea-multicast-ieee802-03 (work in
progress), July 2017. progress), July 2017.
[IEEE-1609.2] [IEEE-1609.2]
"IEEE SA - 1609.2-2016 - IEEE Standard for Wireless Access "IEEE SA - 1609.2-2016 - IEEE Standard for Wireless Access
in Vehicular Environments (WAVE) -- Security Services for in Vehicular Environments (WAVE) -- Security Services for
Applications and Management Messages. Example URL Applications and Management Messages. Example URL
skipping to change at page 15, line 22 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.
From draft-ietf-ipwave-ipv6-over-80211ocb-20 to draft-ietf-ipwave-
ipv6-over-80211ocb-21
o Corrected a few nits and added names in Acknowledgments section.
o Removed unused reference to old Internet Draft tsvwg about QoS.
From draft-ietf-ipwave-ipv6-over-80211ocb-19 to draft-ietf-ipwave- From draft-ietf-ipwave-ipv6-over-80211ocb-19 to draft-ietf-ipwave-
ipv6-over-80211ocb-20 ipv6-over-80211ocb-20
o Reduced the definition of term "802.11-OCB". o Reduced the definition of term "802.11-OCB".
o Left out of this specification which 802.11 header to use to o Left out of this specification which 802.11 header to use to
transmit IP packets in OCB mode (QoS Data header, Data header, or transmit IP packets in OCB mode (QoS Data header, Data header, or
any other). any other).
o Added 'MUST' use an Ethernet Adaptation Layer, instead of 'is o Added 'MUST' use an Ethernet Adaptation Layer, instead of 'is
skipping to change at page 24, line 29 skipping to change at page 24, line 24
| | |<------ Data -------->| | | |<------ Data -------->|
|---- Auth Req. ------>| | | |---- Auth Req. ------>| | |
|<--- Auth Res. -------| |<------ Data -------->| |<--- Auth Res. -------| |<------ Data -------->|
| | | | | | | |
|---- Asso Req. ------>| |<------ Data -------->| |---- Asso Req. ------>| |<------ Data -------->|
|<--- Asso Res. -------| | | |<--- Asso Res. -------| | |
| | |<------ Data -------->| | | |<------ Data -------->|
|<------ Data -------->| | | |<------ Data -------->| | |
|<------ Data -------->| |<------ Data -------->| |<------ Data -------->| |<------ Data -------->|
(i) 802.11 Infrastructure mode (ii) 802.11-OCB mode (i) 802.11 Infrastructure mode (ii) 802.11-OCB mode
Figure 3: Difference between messages exchanged on 802.11 (left) and Figure 3: Difference between messages exchanged on 802.11 (left) and
802.11-OCB (right) 802.11-OCB (right)
The interface 802.11-OCB was specified in IEEE Std 802.11p (TM) -2010 The interface 802.11-OCB was specified in IEEE Std 802.11p (TM) -2010
[IEEE-802.11p-2010] as an amendment to IEEE Std 802.11 (TM) -2007, [IEEE-802.11p-2010] as an amendment to IEEE Std 802.11 (TM) -2007,
titled "Amendment 6: Wireless Access in Vehicular Environments". titled "Amendment 6: Wireless Access in Vehicular Environments".
Since then, this amendment has been integrated in IEEE 802.11(TM) Since then, this amendment has been integrated in IEEE 802.11(TM)
-2012 and -2016 [IEEE-802.11-2016]. -2012 and -2016 [IEEE-802.11-2016].
 End of changes. 12 change blocks. 
36 lines changed or deleted 39 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/