draft-ietf-ipwave-ipv6-over-80211ocb-35.txt		draft-ietf-ipwave-ipv6-over-80211ocb-36.txt
	skipping to change at page 1, line 17 ¶		skipping to change at page 1, line 17 ¶
	J. Haerri		J. Haerri
	Eurecom		Eurecom
	J. Lee		J. Lee
	Sangmyung University		Sangmyung University
	T. Ernst		T. Ernst
	YoGoKo		YoGoKo
	April 8, 2019		April 8, 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-35		draft-ietf-ipwave-ipv6-over-80211ocb-36
	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 2, line 38 ¶		skipping to change at page 2, line 38 ¶
	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
	5.1.1. Privacy Risks of Meaningful info in Interface IDs . . 10		5.1.1. Privacy Risks of Meaningful info in Interface IDs . . 10
	5.2. MAC Address and Interface ID Generation . . . . . . . . . 11		5.2. MAC Address and Interface ID Generation . . . . . . . . . 10
	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 . . . . 27
	skipping to change at page 7, line 17 ¶		skipping to change at page 7, line 17 ¶
	There are several types of IPv6 addresses [RFC4291], [RFC4193], that		There are several types of IPv6 addresses [RFC4291], [RFC4193], that
	MAY be assigned to an 802.11-OCB interface. Among these types of		MAY be assigned to an 802.11-OCB interface. Among these types of
	addresses only the IPv6 link-local addresses MAY be formed using an		addresses only the IPv6 link-local addresses MAY be formed using an
	EUI-64 identifier, in particular during transition time.		EUI-64 identifier, in particular during transition time.
	If the IPv6 link-local address is formed using an EUI-64 identifier,		If the IPv6 link-local address is formed using an EUI-64 identifier,
	then the mechanism of forming that address is the same mechanism as		then the mechanism of forming that address is the same mechanism as
	used to form an IPv6 link-local address on Ethernet links. This		used to form an IPv6 link-local address on Ethernet links. This
	mechanism is described in section 5 of [RFC2464].		mechanism is described in section 5 of [RFC2464].
	For privacy, the link-local address MAY be formed according to the
	mechanisms described in Section 5.2.
	4.4. Stateless Autoconfiguration		4.4. Stateless Autoconfiguration
	There are several types of IPv6 addresses [RFC4291], [RFC4193], that		There are several types of IPv6 addresses [RFC4291], [RFC4193], that
	MAY be assigned to an 802.11-OCB interface. This section describes		MAY be assigned to an 802.11-OCB interface. This section describes
	the formation of Interface Identifiers for IPv6 addresses of type		the formation of Interface Identifiers for IPv6 addresses of type
	'Global' or 'Unique Local'. For Interface Identifiers for IPv6		'Global' or 'Unique Local'. For Interface Identifiers for IPv6
	address of type 'Link-Local' see Section 4.3.		address of type 'Link-Local' see Section 4.3.
	The Interface Identifier for an 802.11-OCB interface is formed using		The Interface Identifier for an 802.11-OCB interface is formed using
	the same rules as the Interface Identifier for an Ethernet interface;		the same rules as the Interface Identifier for an Ethernet interface;
	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.
			-36: removed a phrase about the IID formation and MAC generation, but
			left in the section 5.2 that describes how it happens.
	-35: addressing the the intarea review: clarified a small apparent		-35: addressing the the intarea review: clarified a small apparent
	contradiction between two parts of text that use the old MAC-based		contradiction between two parts of text that use the old MAC-based
	IIDs (clarified by using qualifiers from each other: transition time,		IIDs (clarified by using qualifiers from each other: transition time,
	and ll addresses); sequenced closer the LL and Stateless Autoconf		and ll addresses); sequenced closer the LL and Stateless Autoconf
	sections, instead of spacing them; shortened the paragraph of Opaque		sections, instead of spacing them; shortened the paragraph of Opaque
	IIDs; moved the privacy risks of in-clear IIDs in the security		IIDs; moved the privacy risks of in-clear IIDs in the security
	section; removed a short phrase duplicating the idea of privacy		section; removed a short phrase duplicating the idea of privacy
	risks; added third time a reference to the 802.11-2016 document; used		risks; added third time a reference to the 802.11-2016 document; used
	'the hidden terminal' text; updated the Terminology section with new		'the hidden terminal' text; updated the Terminology section with new
	BCP-14 text 'MUST' to include RFC8174.		BCP-14 text 'MUST' to include RFC8174.
End of changes. 4 change blocks.
	5 lines changed or deleted		5 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/