draft-ietf-ipwave-ipv6-over-80211ocb-31.txt		draft-ietf-ipwave-ipv6-over-80211ocb-32.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: May 23, 2019 Moulay Ismail University		Expires: June 13, 2019 Moulay Ismail University
	J. Haerri		J. Haerri
	Eurecom		Eurecom
	J. Lee		J. Lee
	Sangmyung University		Sangmyung University
	T. Ernst		T. Ernst
	YoGoKo		YoGoKo
	November 19, 2018		December 10, 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-31		draft-ietf-ipwave-ipv6-over-80211ocb-32
	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 May 23, 2019.		This Internet-Draft will expire on June 13, 2019.
	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 ¶
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 11		5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 11
	5.2. MAC Address and Interface ID Generation . . . . . . . . . 11		5.2. MAC Address and Interface ID Generation . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . 26		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 . . . . 27
	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 . . . 31		become a 802.11-OCB driver . . . 31
	Appendix E. Protocol Layering . . . . . . . . . . . . . . . . . 32		Appendix E. Protocol Layering . . . . . . . . . . . . . . . . . 32
	Appendix F. Design Considerations . . . . . . . . . . . . . . . 33		Appendix F. Design Considerations . . . . . . . . . . . . . . . 33
	Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 33		Appendix G. IEEE 802.11 Messages Transmitted in OCB mode . . . . 33
	Appendix H. Examples of Packet Formats . . . . . . . . . . . . . 33		Appendix H. Examples of Packet Formats . . . . . . . . . . . . . 34
	H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 34		H.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 35
	H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 37		H.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 37
	Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 39		Appendix I. Extra Terminology . . . . . . . . . . . . . . . . . 39
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
	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, Appendix C and Appendix D). This involves the layering		Appendix B, Appendix C and Appendix D). This involves the layering
	of IPv6 networking on top of the IEEE 802.11 MAC layer, with an LLC		of IPv6 networking on top of the IEEE 802.11 MAC layer, with an LLC
	skipping to change at page 10, line 14 ¶		skipping to change at page 10, line 14 ¶
	Additionally, even if the timing requirements are not very strict		Additionally, even if the timing requirements are not very strict
	(e.g. the moving subnet formed by two following vehicles is stable, a		(e.g. the moving subnet formed by two following vehicles is stable, a
	fixed IP-RSU is absent), the subnet is disconnected from the Internet		fixed IP-RSU is absent), the subnet is disconnected from the Internet
	(a default route is absent), and the addressing peers are equally		(a default route is absent), and the addressing peers are equally
	qualified (impossible to determine that some vehicle owns and		qualified (impossible to determine that some vehicle owns and
	distributes addresses to others) the use of link-local addresses is		distributes addresses to others) the use of link-local addresses is
	RECOMMENDED.		RECOMMENDED.
	The Neighbor Discovery protocol (ND) [RFC4861] is used over		The Neighbor Discovery protocol (ND) [RFC4861] is used over
	802.11-OCB links. Due to lack of link-layer acknowledgements in		802.11-OCB links.
	802.11-OCB for both unicast and multicast, we can expect higher
	unicast loss than for 802.11 BSS. The ND retransmissions are
	supposed to handle loss of unicast and/or multicast just as it does
	for other link types.
	Protocols like Mobile IPv6 [RFC6275] and DNAv6 [RFC6059], which		Protocols like Mobile IPv6 [RFC6275] and DNAv6 [RFC6059], which
	depend on timely movement detection, might need additional tuning		depend on timely movement detection, might need additional tuning
	work to handle the lack of link-layer notifications during handover.		work to handle the lack of link-layer notifications during handover.
	This is for further study.		This is for further study.
	5. Security Considerations		5. Security Considerations
	Any security mechanism at the IP layer or above that may be carried		Any security mechanism at the IP layer or above that may be carried
	out for the general case of IPv6 may also be carried out for IPv6		out for the general case of IPv6 may also be carried out for IPv6
	skipping to change at page 17, line 33 ¶		skipping to change at page 17, 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.
			-32: significantly shortened the relevant ND/OCB paragraph. It now
			just states ND is used over OCB, w/o detailing.
	-31: filled in the section titled "Pseudonym Handling"; removed a		-31: filled in the section titled "Pseudonym Handling"; removed a
	'MAY NOT' phrase about possibility of having other prefix than the LL		'MAY NOT' phrase about possibility of having other prefix than the LL
	on the link between cars; shortened and improved the paragraph about		on the link between cars; shortened and improved the paragraph about
	Mobile IPv6, now with DNAv6; improved the ND text about ND		Mobile IPv6, now with DNAv6; improved the ND text about ND
	retransmissions with relationship to packet loss; changed the title		retransmissions with relationship to packet loss; changed the title
	of an appendix from 'EPD' to 'Protocol Layering'; improved the		of an appendix from 'EPD' to 'Protocol Layering'; improved the
	'Aspects introduced by OCB' appendix with a few phrases about the		'Aspects introduced by OCB' appendix with a few phrases about the
	channel use and references.		channel use and references.
	-30: a clarification on the reliability of ND over OCB and over		-30: a clarification on the reliability of ND over OCB and over
End of changes. 8 change blocks.
	12 lines changed or deleted		11 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/