draft-ietf-ipwave-ipv6-over-80211ocb-38.txt   draft-ietf-ipwave-ipv6-over-80211ocb-39.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: October 13, 2019 Moulay Ismail University Expires: October 16, 2019 Moulay Ismail University
J. Haerri J. Haerri
Eurecom Eurecom
J. Lee J. Lee
Sangmyung University Sangmyung University
T. Ernst T. Ernst
YoGoKo YoGoKo
April 11, 2019 April 14, 2019
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-38 draft-ietf-ipwave-ipv6-over-80211ocb-39
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 October 13, 2019. This Internet-Draft will expire on October 16, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 25 skipping to change at page 2, line 25
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Communication Scenarios where IEEE 802.11-OCB Links are Used 4 3. Communication Scenarios where IEEE 802.11-OCB Links are Used 4
4. IPv6 over 802.11-OCB . . . . . . . . . . . . . . . . . . . . 5 4. IPv6 over 802.11-OCB . . . . . . . . . . . . . . . . . . . . 4
4.1. Maximum Transmission Unit (MTU) . . . . . . . . . . . . . 5 4.1. Maximum Transmission Unit (MTU) . . . . . . . . . . . . . 4
4.2. Frame Format . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Frame Format . . . . . . . . . . . . . . . . . . . . . . 5
4.2.1. Ethernet Adaptation Layer . . . . . . . . . . . . . . 5 4.2.1. Ethernet Adaptation Layer . . . . . . . . . . . . . . 5
4.3. Link-Local Addresses . . . . . . . . . . . . . . . . . . 7 4.3. Link-Local Addresses . . . . . . . . . . . . . . . . . . 7
4.4. Stateless Autoconfiguration . . . . . . . . . . . . . . . 7 4.4. Stateless Autoconfiguration . . . . . . . . . . . . . . . 7
4.5. Address Mapping . . . . . . . . . . . . . . . . . . . . . 8 4.5. Address Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.5.1. Address Mapping -- Unicast . . . . . . . . . . . . . 8 4.5.1. Address Mapping -- Unicast . . . . . . . . . . . . . 8
4.5.2. Address Mapping -- Multicast . . . . . . . . . . . . 8 4.5.2. Address Mapping -- Multicast . . . . . . . . . . . . 8
4.6. Subnet Structure . . . . . . . . . . . . . . . . . . . . 8 4.6. Subnet Structure . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 10 5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 10
skipping to change at page 2, line 48 skipping to change at page 2, line 48
5.2. MAC Address and Interface ID Generation . . . . . . . . . 11 5.2. MAC Address and Interface ID Generation . . . . . . . . . 11
5.3. Pseudonym Handling . . . . . . . . . . . . . . . . . . . 11 5.3. Pseudonym Handling . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 17 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 17
Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 27 Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 27
Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 27 Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 28
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 . . . 32 become a 802.11-OCB driver . . . 32
Appendix E. Protocol Layering . . . . . . . . . . . . . . . . . 33 Appendix E. Protocol Layering . . . . . . . . . . . . . . . . . 33
Appendix F. Design Considerations . . . . . . . . . . . . . . . 34 Appendix F. Design Considerations . . . . . . . . . . . . . . . 34
Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 34 Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 34
Appendix H. Examples of Packet Formats . . . . . . . . . . . . . 34 Appendix H. Examples of Packet Formats . . . . . . . . . . . . . 34
H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 35 H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 35
H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 38 H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 38
Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 40 Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 40
Appendix J. Neighbor Discovery (ND) Potential Issues in Wireless Appendix J. Neighbor Discovery (ND) Potential Issues in Wireless
skipping to change at page 3, line 32 skipping to change at page 3, line 32
layer. 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] .
[I-D.hinden-6man-rfc2464bis].
o Exceptions due to the OCB nature of 802.11-OCB compared to 802.11. o Exceptions due to the OCB nature of 802.11-OCB compared to 802.11.
This has impacts on security, privacy, subnet structure and This has impacts on security, privacy, subnet structure and
movement detection. For security and privacy recommendations see movement detection. For security and privacy recommendations see
Section 5 and Section 4.4. The subnet structure is described in Section 5 and Section 4.4. The subnet structure is described in
Section 4.6. The movement detection on OCB links is not described Section 4.6. The movement detection on OCB links is not described
in this document. in this document.
In the published literature, many documents describe aspects and In the published literature, many documents describe aspects and
problems related to running IPv6 over 802.11-OCB: problems related to running IPv6 over 802.11-OCB:
skipping to change at page 8, line 42 skipping to change at page 8, line 42
proved to have some performance issues proved to have some performance issues
[I-D.ietf-mboned-ieee802-mcast-problems]. These issues may be [I-D.ietf-mboned-ieee802-mcast-problems]. 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.6. Subnet Structure 4.6. Subnet Structure
A subnet is formed by the external 802.11-OCB interfaces of vehicles A subnet is formed by the external 802.11-OCB interfaces of vehicles
that are in close range (not by their in-vehicle interfaces). This that are in close range (not by their in-vehicle interfaces). This
subnet MUST use at least the link-local prefix and the interfaces subnet MUST use at least the link-local prefix and the interfaces
MUST be assigned IPv6 address(es) of type link-local. MUST be assigned IPv6 address(es) of type link-local. All nodes in
the subnet MUST be able to communicate directly using their link-
local unicast addresses.
The structure of this subnet is ephemeral, in that it is strongly The structure of this subnet is ephemeral, in that it is strongly
influenced by the mobility of vehicles: the hidden terminal effects influenced by the mobility of vehicles: the hidden terminal effects
appear; the 802.11 networks in OCB mode may be considered as 'ad-hoc' appear; the 802.11 networks in OCB mode may be considered as 'ad-hoc'
networks with an addressing model as described in [RFC5889]. On networks with an addressing model as described in [RFC5889]. On
another hand, the structure of the internal subnets in each car is another hand, the structure of the internal subnets in each car is
relatively stable. relatively stable.
As recommended in [RFC5889], when the timing requirements are very As recommended in [RFC5889], when the timing requirements are very
strict (e.g. fast drive through IP-RSU coverage), no on-link subnet strict (e.g. fast drive through IP-RSU coverage), no on-link subnet
skipping to change at page 16, line 15 skipping to change at page 16, line 15
[ETSI-sec-archi] [ETSI-sec-archi]
"ETSI TS 102 940 V1.2.1 (2016-11), ETSI Technical "ETSI TS 102 940 V1.2.1 (2016-11), ETSI Technical
Specification, Intelligent Transport Systems (ITS); Specification, Intelligent Transport Systems (ITS);
Security; ITS communications security architecture and Security; ITS communications security architecture and
security management, November 2016. Downloaded on security management, November 2016. Downloaded on
September 9th, 2017, freely available from ETSI website at September 9th, 2017, freely available from ETSI website at
URL http://www.etsi.org/deliver/ URL http://www.etsi.org/deliver/
etsi_ts/102900_102999/102940/01.02.01_60/ etsi_ts/102900_102999/102940/01.02.01_60/
ts_102940v010201p.pdf". ts_102940v010201p.pdf".
[I-D.hinden-6man-rfc2464bis]
Crawford, M. and R. Hinden, "Transmission of IPv6 Packets
over Ethernet Networks", draft-hinden-6man-rfc2464bis-02
(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-mboned-ieee802-mcast-problems] [I-D.ietf-mboned-ieee802-mcast-problems]
Perkins, C., McBride, M., Stanley, D., Kumari, W., and J. Perkins, C., McBride, M., Stanley, D., Kumari, W., and J.
Zuniga, "Multicast Considerations over IEEE 802 Wireless Zuniga, "Multicast Considerations over IEEE 802 Wireless
skipping to change at page 17, line 36 skipping to change at page 17, line 36
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.
-39: removed a reference to an expired draft trying to update the
IPv6-over-Ethernet spec 'RFC2464bis'; added text in the subnet
structure section saying nodes MUST be able to communicate directly
using their link-local addresses.
-38: removed the word "fe80::/10". -38: removed the word "fe80::/10".
-37: added a section about issues on ND wireless; added the qualifier -37: added a section about issues on ND wireless; added the qualifier
'baseline' to using ND on 802.11-OCB; improved the description of the 'baseline' to using ND on 802.11-OCB; improved the description of the
reference to 802.11-2016 document, with a qualifier about the reference to 802.11-2016 document, with a qualifier about the
difficulty of accessing it, even though it is free. difficulty of accessing it, even though it is free.
-36: removed a phrase about the IID formation and MAC generation, but -36: removed a phrase about the IID formation and MAC generation, but
left in the section 5.2 that describes how it happens. left in the section 5.2 that describes how it happens.
 End of changes. 10 change blocks. 
15 lines changed or deleted 16 lines changed or added

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