draft-ietf-ipwave-ipv6-over-80211ocb-29.txt		draft-ietf-ipwave-ipv6-over-80211ocb-30.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: March 24, 2019 Moulay Ismail University		Expires: March 28, 2019 Moulay Ismail University
	J. Haerri		J. Haerri
	Eurecom		Eurecom
	J. Lee		J. Lee
	Sangmyung University		Sangmyung University
	T. Ernst		T. Ernst
	YoGoKo		YoGoKo
	September 20, 2018		September 24, 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-29		draft-ietf-ipwave-ipv6-over-80211ocb-30
	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 March 24, 2019.		This Internet-Draft will expire on March 28, 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 39 ¶		skipping to change at page 2, line 39 ¶
	4.3.1. Ethernet Adaptation Layer . . . . . . . . . . . . . . 5		4.3.1. Ethernet Adaptation Layer . . . . . . . . . . . . . . 5
	4.4. Link-Local Addresses . . . . . . . . . . . . . . . . . . 7		4.4. Link-Local Addresses . . . . . . . . . . . . . . . . . . 7
	4.5. Address Mapping . . . . . . . . . . . . . . . . . . . . . 7		4.5. Address Mapping . . . . . . . . . . . . . . . . . . . . . 7
	4.5.1. Address Mapping -- Unicast . . . . . . . . . . . . . 7		4.5.1. Address Mapping -- Unicast . . . . . . . . . . . . . 7
	4.5.2. Address Mapping -- Multicast . . . . . . . . . . . . 7		4.5.2. Address Mapping -- Multicast . . . . . . . . . . . . 7
	4.6. Stateless Autoconfiguration . . . . . . . . . . . . . . . 7		4.6. Stateless Autoconfiguration . . . . . . . . . . . . . . . 7
	4.7. Subnet Structure . . . . . . . . . . . . . . . . . . . . 9		4.7. Subnet Structure . . . . . . . . . . . . . . . . . . . . 9
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 10		5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 10
	5.2. MAC Address and Interface ID Generation . . . . . . . . . 11		5.2. MAC Address and Interface ID Generation . . . . . . . . . 11
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		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 . . . . . . . . . . . . . . . . . . . . . . 26
	Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 26		Appendix C. Aspects introduced by the OCB mode to 802.11 . . . . 26
	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 . . . 30		become a 802.11-OCB driver . . . 30
	skipping to change at page 9, line 42 ¶		skipping to change at page 9, line 42 ¶
	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.		802.11-OCB links. The reliability of the ND protocol over 802.11-OCB
			is the reliability of the delivery of ND multicast messages. This
			reliability is the same as the reliability of delivery of ND
			multicast messages over 802.11 links operated with a BSS ID.
	The operation of the Mobile IPv6 protocol over 802.11-OCB links is		The operation of the Mobile IPv6 protocol over 802.11-OCB links is
	different than on other links. The Movement Detection operation		different than on other links. The Movement Detection operation
	(section 11.5.1 of [RFC6275]) can not rely on Neighbor Unreachability		(section 11.5.1 of [RFC6275]) can not rely on Neighbor Unreachability
	Detection operation of the Neighbor Discovery protocol, for the		Detection operation of the Neighbor Discovery protocol, for the
	reason mentioned in the previous paragraph. Also, the 802.11-OCB		reason mentioned in the previous paragraph. Also, the 802.11-OCB
	link layer is not a lower layer that can provide an indication that a		link layer is not a lower layer that can provide an indication that a
	link layer handover has occured. The operation of the Mobile IPv6		link layer handover has occured. The operation of the Mobile IPv6
	protocol over 802.11-OCB is not specified in this document.		protocol over 802.11-OCB is not specified in this document.
	skipping to change at page 17, line 10 ¶		skipping to change at page 17, 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.
			-30: a clarification on the reliability of ND over OCB and over
			802.11.
	-29:		-29:
	o		o
	-28:		-28:
	o Created a new section 'Pseudonym Handling'.		o Created a new section 'Pseudonym Handling'.
	o removed the 'Vehicle ID' appendix.		o removed the 'Vehicle ID' appendix.
End of changes. 7 change blocks.
	6 lines changed or deleted		12 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/