draft-ietf-ipwave-ipv6-over-80211ocb-11.txt		draft-ietf-ipwave-ipv6-over-80211ocb-12.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: April 19, 2018 Moulay Ismail University		Expires: July 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
	October 16, 2017		December 31, 2017
	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-11.txt		draft-ietf-ipwave-ipv6-over-80211ocb-12.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 April 19, 2018.		This Internet-Draft will expire on July 4, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . 11		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11		7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	9.1. Normative References . . . . . . . . . . . . . . . . . . 12		9.1. Normative References . . . . . . . . . . . . . . . . . . 12
	9.2. Informative References . . . . . . . . . . . . . . . . . 14		9.2. Informative References . . . . . . . . . . . . . . . . . 14
	Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 16		Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 16
	Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 22		Appendix B. 802.11p . . . . . . . . . . . . . . . . . . . . . . 22
	Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 22		Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 22
	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 . . . 26		become a 802.11-OCB driver . . . 27
	Appendix E. EtherType Protocol Discrimination (EPD) . . . . . . 27		Appendix E. EtherType Protocol Discrimination (EPD) . . . . . . 28
	Appendix F. Design Considerations . . . . . . . . . . . . . . . 28		Appendix F. Design Considerations . . . . . . . . . . . . . . . 29
	F.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 28		F.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 29
	F.2. Reliability Requirements . . . . . . . . . . . . . . . . 29		F.2. Reliability Requirements . . . . . . . . . . . . . . . . 29
	F.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 29		F.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 30
	F.4. MAC Address Generation . . . . . . . . . . . . . . . . . 30		F.4. MAC Address Generation . . . . . . . . . . . . . . . . . 31
	Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 31		Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 31
	Appendix H. Implementation Status . . . . . . . . . . . . . . . 31		Appendix H. Implementation Status . . . . . . . . . . . . . . . 31
	H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 32		H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 32
	H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 34		H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 35
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
	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). This involves the layering of IPv6 networking on top of
	the IEEE 802.11 MAC layer, with an LLC layer. Compared to running		the IEEE 802.11 MAC layer, with an LLC layer. Compared to running
	IPv6 over the Ethernet MAC layer, there is no modification expected		IPv6 over the Ethernet MAC layer, there is no modification expected
	to IEEE Std 802.11 MAC and Logical Link sublayers: IPv6 works fine		to IEEE Std 802.11 MAC and Logical Link sublayers: IPv6 works fine
	directly over 802.11-OCB too, with an LLC layer.		directly over 802.11-OCB too, with an LLC layer.
	skipping to change at page 11, line 45 ¶		skipping to change at page 11, line 45 ¶
	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 and William Whyte. Their valuable comments clarified		Margaret Cullen, Erik Kline and William Whyte. Their valuable
	particular issues and generally helped to improve the document.		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 19 ¶		skipping to change at page 15, line 19 ¶
	[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]		[I-D.ietf-tsvwg-ieee-802-11]
	Szigeti, T., Henry, J., and F. Baker, "Diffserv to IEEE		Szigeti, T., Henry, J., and F. Baker, "Diffserv to IEEE
	802.11 Mapping", draft-ietf-tsvwg-ieee-802-11-09 (work in		802.11 Mapping", draft-ietf-tsvwg-ieee-802-11-11 (work in
	progress), September 2017.		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
	skipping to change at page 16, line 33 ¶		skipping to change at page 16, line 33 ¶
	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-11 to draft-ietf-ipwave-
			ipv6-over-80211ocb-12
			o Improved the appendix about "MAC Address Generation" by expressing
			the technique to be an optional suggestion, not a mandatory
			mechanism.
	From draft-ietf-ipwave-ipv6-over-80211ocb-10 to draft-ietf-ipwave-		From draft-ietf-ipwave-ipv6-over-80211ocb-10 to draft-ietf-ipwave-
	ipv6-over-80211ocb-11		ipv6-over-80211ocb-11
	o Shortened the paragraph on forming/terminating 802.11-OCB links.		o Shortened the paragraph on forming/terminating 802.11-OCB links.
	o Moved the draft tsvwg-ieee-802-11 to Informative References.		o Moved the draft tsvwg-ieee-802-11 to Informative References.
	From draft-ietf-ipwave-ipv6-over-80211ocb-09 to draft-ietf-ipwave-		From draft-ietf-ipwave-ipv6-over-80211ocb-09 to draft-ietf-ipwave-
	ipv6-over-80211ocb-10		ipv6-over-80211ocb-10
	skipping to change at page 30, line 31 ¶		skipping to change at page 31, line 11 ¶
	and another stayed constant, external observers would be able to		and another stayed constant, external observers would be able to
	correlate old and new values, and the privacy benefits of		correlate old and new values, and the privacy benefits of
	randomization would be lost.		randomization would be lost.
	The privacy requirements of Non IP safety-critical communications		The privacy requirements of Non IP safety-critical communications
	imply that if a change of pseudonyme occurs, renumbering of all other		imply that if a change of pseudonyme occurs, renumbering of all other
	interfaces shall also occur.		interfaces shall also occur.
	F.4. MAC Address Generation		F.4. MAC Address Generation
	When designing the IPv6 over 802.11-OCB address mapping, we assume		In 802.11-OCB networks, the MAC addresses may change during well
	that the MAC Addresses change during well defined "renumbering		defined renumbering events. A 'randomized' MAC address has the
	events". The 48 bits randomized MAC addresses will have the
	following characteristics:		following characteristics:
	o Bit "Local/Global" set to "locally admninistered".		o Bit "Local/Global" set to "locally admninistered".
	o Bit "Unicast/Multicast" set to "Unicast".		o Bit "Unicast/Multicast" set to "Unicast".
	o 46 remaining bits set to a random value, using a random number		o The 46 remaining bits are set to a random value, using a random
	generator that meets the requirements of [RFC4086].		number generator that meets the requirements of [RFC4086].
	The way to meet the randomization requirements is to retain 46 bits		To meet the randomization requirements for the 46 remaining bits, a
	from the output of a strong hash function, such as SHA256, taking as		hash function may be used. For example, the SHA256 hash function may
	input a 256 bit local secret, the "nominal" MAC Address of the		be used with input a 256 bit local secret, the "nominal" MAC Address
	interface, and a representation of the date and time of the		of the interface, and a representation of the date and time of the
	renumbering event.		renumbering event.
	Appendix G. IEEE 802.11 Messages Transmitted in OCB mode		Appendix G. IEEE 802.11 Messages Transmitted in OCB mode
	For information, at the time of writing, this is the list of IEEE		For information, at the time of writing, this is the list of IEEE
	802.11 messages that may be transmitted in OCB mode, i.e. when		802.11 messages that may be transmitted in OCB mode, i.e. when
	dot11OCBActivated is true in a STA:		dot11OCBActivated is true in a STA:
	o The STA may send management frames of subtype Action and, if the		o The STA may send management frames of subtype Action and, if the
	STA maintains a TSF Timer, subtype Timing Advertisement;		STA maintains a TSF Timer, subtype Timing Advertisement;
End of changes. 13 change blocks.
	25 lines changed or deleted		32 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/