< draft-pthubert-detnet-ipv6-hbh-00.txt		draft-pthubert-detnet-ipv6-hbh-01.txt >
	DetNet P. Thubert, Ed.		DetNet P. Thubert, Ed.
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track 8 June 2021		Intended status: Standards Track 8 June 2021
	Expires: 10 December 2021		Expires: 10 December 2021
	IPv6 Hop-by-Hop Options for DetNet		IPv6 Hop-by-Hop Options for DetNet
	draft-pthubert-detnet-ipv6-hbh-00		draft-pthubert-detnet-ipv6-hbh-01
	Abstract		Abstract
	RFC 8938, the Deterministic Networking Data Plane Framework relies on		RFC 8938, the Deterministic Networking Data Plane Framework relies on
	the 6-tuple to identify an IPv6 flow. But the full DetNet operations		the 6-tuple to identify an IPv6 flow. But the full DetNet operations
	require also the capabilities to signal meta-information such as a		require also the capabilities to signal meta-information such as a
	sequence within that flow, and to transport different types of		sequence within that flow, and to transport different types of
	packets along the same path with the same treatment, e.g.,		packets along the same path with the same treatment, e.g.,
	Operations, Administration, and Maintenance packets and/or multiple		Operations, Administration, and Maintenance packets and/or multiple
	flows with fate and resource sharing. This document introduces new		flows with fate and resource sharing. This document introduces new
	Hop-by-Hop header option that can signal that information to the		Hop-by-Hop header options that can signal that information to the
	intermediate relays.		intermediate relays.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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-
	skipping to change at page 3, line 47 ¶		skipping to change at page 3, line 47 ¶
	in the larger Internet [RFC9008].		in the larger Internet [RFC9008].
	"IPv6 Hop-by-Hop Options Processing Procedures" [HbH-PROCESS] further		"IPv6 Hop-by-Hop Options Processing Procedures" [HbH-PROCESS] further
	specifies the procedures for how IPv6 Hop-by-Hop options are		specifies the procedures for how IPv6 Hop-by-Hop options are
	processed to make their processing even more practical and increase		processed to make their processing even more practical and increase
	their use in the Internet. In that context, it makes sense to		their use in the Internet. In that context, it makes sense to
	consider the Hop-by-Hop Options to transport the information that is		consider the Hop-by-Hop Options to transport the information that is
	relevant to DetNet, making it independant of the transport and		relevant to DetNet, making it independant of the transport and
	placing it early in the header chain.		placing it early in the header chain.
	The "Deterministic Networking Data Plane Framework" [RFC8938]relies		The "Deterministic Networking Data Plane Framework" [RFC8938] relies
	on the 6-tuple to identify an IPv6 flow. But the full DetNet		on the 6-tuple to identify an IPv6 flow. But the full DetNet
	*operations require also the capabilities to signal meta-information		*operations require also the capabilities to signal meta-information
	such as a sequence within that flow, and to transport different types		such as a sequence within that flow, and to transport different types
	of packets along the same path with the same treatment. For		of packets along the same path with the same treatment. For
	instance, it is required that Operations, Administration, and		instance, it is required that Operations, Administration, and
	Maintenance (OAM) [RFC6291] packets and/or multiple flows share the		Maintenance (OAM) [RFC6291] packets and/or multiple flows share the
	same fate and resource sharing over the same Track or the same		same fate and resource sharing over the same Track or the same
	Traffic Engineered (TE) [RFC3272] DetNet path.		Traffic Engineered (TE) [RFC3272] DetNet path.
	This document introduces new Hop-by-Hop options that can signal path		This document introduces new Hop-by-Hop options that can signal
	and sequencing information to the intermediate relays early in the		DetNet path and sequencing information to the intermediate relays;
	packet and independantly of the transport layer.		with this method, the DetNet infoirmation is available early in the
			packet and in an abstract form that is independant of the transport
			layer.
	2. Terminology		2. Terminology
	Timestamp semantics and timestamp formats used in this document are		Timestamp semantics and timestamp formats used in this document are
	defined in "Guidelines for Defining Packet Timestamps" [RFC8877].		defined in "Guidelines for Defining Packet Timestamps" [RFC8877].
	The Deterministic Networking terms used in this document are defined		The Deterministic Networking terms used in this document are defined
	in the "Deterministic Networking Architecture" [DetNet-ARCHI].		in the "Deterministic Networking Architecture" [DetNet-ARCHI].
	The terms Track and TrackID are defined in the "6TiSCH Architecture"		The terms Track and TrackID are defined in the "6TiSCH Architecture"
	skipping to change at page 6, line 34 ¶		skipping to change at page 6, line 34 ¶
	| | | | 4.2.1. of [RFC8877] |		| | | | 4.2.1. of [RFC8877] |
	+-------+============+---------------+---------------------------+		+-------+============+---------------+---------------------------+
	| 12 | Time Stamp | Short NTP | NTP 32-bit Timestamp |		| 12 | Time Stamp | Short NTP | NTP 32-bit Timestamp |
	| | | | Format, see section |		| | | | Format, see section |
	| | | | 4.2.2. of [RFC8877] |		| | | | 4.2.2. of [RFC8877] |
	+-------+============+---------------+---------------------------+		+-------+============+---------------+---------------------------+
	| 13 | Time Stamp | PTP | PTP 80-bit Timestamp |		| 13 | Time Stamp | PTP | PTP 80-bit Timestamp |
	| | | | Format, see [IEEE |		| | | | Format, see [IEEE |
	| | | | Std. 1588] |		| | | | Std. 1588] |
	+-------+============+---------------+---------------------------+		+-------+============+---------------+---------------------------+
	| 13 | Time Stamp | Short PTP | PTP 64-bit Truncated |		| 14 | Time Stamp | Short PTP | PTP 64-bit Truncated |
	| | | | Timestamp Format, |		| | | | Timestamp Format, |
	| | | | see section 4.3. of |		| | | | see section 4.3. of |
	| | | | [RFC8877] |		| | | | [RFC8877] |
	+-------+============+---------------+---------------------------+		+-------+============+---------------+---------------------------+
	Table 1: Sequence Type values (suggested)		Table 1: Sequence Type values (suggested)
	3.2. RPL Packet Information		3.2. RPL Packet Information
	6TiSCH [6TiSCH-ARCHI] and RAW [RAW-ARCHI] signal a Track using a RPL		6TiSCH [6TiSCH-ARCHI] and RAW [RAW-ARCHI] signal a Track using a RPL
	skipping to change at page 9, line 5 ¶		skipping to change at page 9, line 5 ¶
	draft-hinden-6man-hbh-processing-00, 3 December 2020,		draft-hinden-6man-hbh-processing-00, 3 December 2020,
	<https://tools.ietf.org/html/draft-hinden-6man-hbh-		<https://tools.ietf.org/html/draft-hinden-6man-hbh-
	processing-00>.		processing-00>.
	[DetNet-ARCHI]		[DetNet-ARCHI]
	Finn, N., Thubert, P., Varga, B., and J. Farkas,		Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", RFC 8655,		"Deterministic Networking Architecture", RFC 8655,
	DOI 10.17487/RFC8655, October 2019,		DOI 10.17487/RFC8655, October 2019,
	<https://www.rfc-editor.org/info/rfc8655>.		<https://www.rfc-editor.org/info/rfc8655>.
	7.2. Informative References		[6TiSCH-ARCHI]
			Thubert, P., Ed., "An Architecture for IPv6 over the Time-
	[RPL-PDAO] Thubert, P., Jadhav, R. A., and M. Gillmore, "Root		Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH)",
	initiated routing state in RPL", Work in Progress,		RFC 9030, DOI 10.17487/RFC9030, May 2021,
	Internet-Draft, draft-ietf-roll-dao-projection-16, 15		<https://www.rfc-editor.org/info/rfc9030>.
	January 2021, <https://tools.ietf.org/html/draft-ietf-
	roll-dao-projection-16>.
	[RAW-ARCHI]		[RAW-ARCHI]
	Thubert, P., Papadopoulos, G. Z., and R. Buddenberg,		Thubert, P., Papadopoulos, G. Z., and R. Buddenberg,
	"Reliable and Available Wireless Architecture/Framework",		"Reliable and Available Wireless Architecture/Framework",
	Work in Progress, Internet-Draft, draft-pthubert-raw-		Work in Progress, Internet-Draft, draft-pthubert-raw-
	architecture-05, 15 November 2020,		architecture-05, 15 November 2020,
	<https://tools.ietf.org/html/draft-pthubert-raw-		<https://tools.ietf.org/html/draft-pthubert-raw-
	architecture-05>.		architecture-05>.
			7.2. Informative References
			[RPL-PDAO] Thubert, P., Jadhav, R. A., and M. Gillmore, "Root
			initiated routing state in RPL", Work in Progress,
			Internet-Draft, draft-ietf-roll-dao-projection-16, 15
			January 2021, <https://tools.ietf.org/html/draft-ietf-
			roll-dao-projection-16>.
	[RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu,		[RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu,
	D., and S. Mansfield, "Guidelines for the Use of the "OAM"		D., and S. Mansfield, "Guidelines for the Use of the "OAM"
	Acronym in the IETF", BCP 161, RFC 6291,		Acronym in the IETF", BCP 161, RFC 6291,
	DOI 10.17487/RFC6291, June 2011,		DOI 10.17487/RFC6291, June 2011,
	<https://www.rfc-editor.org/info/rfc6291>.		<https://www.rfc-editor.org/info/rfc6291>.
	[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,		[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
	"Network Time Protocol Version 4: Protocol and Algorithms		"Network Time Protocol Version 4: Protocol and Algorithms
	Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,		Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
	<https://www.rfc-editor.org/info/rfc5905>.		<https://www.rfc-editor.org/info/rfc5905>.
	skipping to change at page 10, line 11 ¶		skipping to change at page 10, line 16 ¶
	Finn, N. and P. Thubert, "Deterministic Networking Problem		Finn, N. and P. Thubert, "Deterministic Networking Problem
	Statement", RFC 8557, DOI 10.17487/RFC8557, May 2019,		Statement", RFC 8557, DOI 10.17487/RFC8557, May 2019,
	<https://www.rfc-editor.org/info/rfc8557>.		<https://www.rfc-editor.org/info/rfc8557>.
	[RFC9008] Robles, M.I., Richardson, M., and P. Thubert, "Using RPI		[RFC9008] Robles, M.I., Richardson, M., and P. Thubert, "Using RPI
	Option Type, Routing Header for Source Routes, and IPv6-		Option Type, Routing Header for Source Routes, and IPv6-
	in-IPv6 Encapsulation in the RPL Data Plane", RFC 9008,		in-IPv6 Encapsulation in the RPL Data Plane", RFC 9008,
	DOI 10.17487/RFC9008, April 2021,		DOI 10.17487/RFC9008, April 2021,
	<https://www.rfc-editor.org/info/rfc9008>.		<https://www.rfc-editor.org/info/rfc9008>.
	[6TiSCH-ARCHI]
	Thubert, P., Ed., "An Architecture for IPv6 over the Time-
	Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH)",
	RFC 9030, DOI 10.17487/RFC9030, May 2021,
	<https://www.rfc-editor.org/info/rfc9030>.
	[RFC3272] Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X.		[RFC3272] Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X.
	Xiao, "Overview and Principles of Internet Traffic		Xiao, "Overview and Principles of Internet Traffic
	Engineering", RFC 3272, DOI 10.17487/RFC3272, May 2002,		Engineering", RFC 3272, DOI 10.17487/RFC3272, May 2002,
	<https://www.rfc-editor.org/info/rfc3272>.		<https://www.rfc-editor.org/info/rfc3272>.
	[RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S.		[RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S.
	Bryant, "Deterministic Networking (DetNet) Data Plane		Bryant, "Deterministic Networking (DetNet) Data Plane
	Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020,		Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020,
	<https://www.rfc-editor.org/info/rfc8938>.		<https://www.rfc-editor.org/info/rfc8938>.
End of changes. 8 change blocks.
	20 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/