< draft-pthubert-detnet-ipv6-hbh-01.txt		draft-pthubert-detnet-ipv6-hbh-02.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 9 June 2021
	Expires: 10 December 2021		Expires: 11 December 2021
	IPv6 Hop-by-Hop Options for DetNet		IPv6 Hop-by-Hop Options for DetNet
	draft-pthubert-detnet-ipv6-hbh-01		draft-pthubert-detnet-ipv6-hbh-02
	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
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 10 December 2021.		This Internet-Draft will expire on 11 December 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Simplified BSD License text
	as described in Section 4.e of the Trust Legal Provisions and are		as described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. The DetNet Options . . . . . . . . . . . . . . . . . . . . . 4		3. The DetNet Options . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Sequencing Option . . . . . . . . . . . . . . . . . . . . 4		3.1. DetNet Sequencing Option . . . . . . . . . . . . . . . . 4
	3.2. RPL Packet Information . . . . . . . . . . . . . . . . . 6		3.2. RPL Packet Information . . . . . . . . . . . . . . . . . 6
	3.3. DetNet Local Path Option . . . . . . . . . . . . . . . . 7		3.3. DetNet Local Path Option . . . . . . . . . . . . . . . . 7
	3.4. DetNet Global Path Option . . . . . . . . . . . . . . . . 7		3.4. DetNet Global Path Option . . . . . . . . . . . . . . . . 7
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 8		4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		5.1. New Subregistry for the Sequencing Type . . . . . . . . . 8
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		5.2. New Hop-by-Hop Options . . . . . . . . . . . . . . . . . 9
	7.1. Normative References . . . . . . . . . . . . . . . . . . 8		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
	7.2. Informative References . . . . . . . . . . . . . . . . . 9		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10		7.1. Normative References . . . . . . . . . . . . . . . . . . 9
			7.2. Informative References . . . . . . . . . . . . . . . . . 10
			Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	Section 2 of the Deterministic Networking Problem Statement		Section 2 of the Deterministic Networking Problem Statement
	[DetNet-PS] introduces the concept of Deterministic Networking		[DetNet-PS] introduces the concept of Deterministic Networking
	(DetNet) to the IETF. DetNet extends the reach of lower layer		(DetNet) to the IETF. DetNet extends the reach of lower layer
	technologies such as Time-Sensitive Networking (TSN) [IEEE 802.1 TSN]		technologies such as Time-Sensitive Networking (TSN) [IEEE 802.1 TSN]
	and Timeslotted Channel Hopping (TSCH) [IEEE Std. 802.15.4] over IPv6		and Timeslotted Channel Hopping (TSCH) [IEEE Std. 802.15.4] over IPv6
	and MPLS [RFC8938].		and MPLS [RFC8938].
	skipping to change at page 3, line 43 ¶		skipping to change at page 3, line 34 ¶
	an unknown option. Combined, these capabilities enable a larger use		an unknown option. Combined, these capabilities enable a larger use
	of the header beyond the boundaries of a limited domain, as		of the header beyond the boundaries of a limited domain, as
	examplified by the change of behavior of the RPL data plane, that was		examplified by the change of behavior of the RPL data plane, that was
	changed to allow a packet with a RPL option to escape the RPL domain		changed to allow a packet with a RPL option to escape the RPL domain
	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 Hop-by-Hop Options to transport the information that is
	relevant to DetNet, making it independant of the transport and		relevant to DetNet.
	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		This document introduces new Hop-by-Hop options that can signal
	DetNet path and sequencing information to the intermediate relays;		DetNet path and sequencing information to the intermediate relays in
	with this method, the DetNet infoirmation is available early in the		an abstract form that is independent of the transport layer.
	packet and in an abstract form that is independant of the transport		Transported in IPv6 HbH Options, the DetNet information is available
	layer.		early in the header chain of the packet and presented and added as
			part of a service instance encapsulation by the Ingress of the DetNet
			path and accessed by the intermediate DetNet relay nodes.
	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"
	[6TiSCH-ARCHI].		[6TiSCH-ARCHI].
	3. The DetNet Options		3. The DetNet Options
	This document defines a number of IPv6 options to be placed in a HbH		This document defines a number of IPv6 options to be placed in a HbH
	Options Header; the format of these options follow the generic		Options Header; the format of these options follow the generic
	definition in section 4.2 of [IPv6].		definition in section 4.2 of [IPv6].
	3.1. Sequencing Option		3.1. DetNet Sequencing Option
	A typical packet sequence can be expressed uniquely as a wrapping		A typical packet sequence can be expressed uniquely as a wrapping
	counter, represented as an unsigned integer in the option. In that		counter, represented as an unsigned integer in the option. In that
	case, the size of the representation MUST be large enough to cover		case, the size of the representation MUST be large enough to cover at
	several times the upper bound on out-of-order packet delivery in		least 3 times the upper bound on out-of-order packet delivery in
	terms of number of packets.		terms of number of packets.
	This specification also allows to use a time stamp for the packet		This specification also allows to use a time stamp for the packet
	sequencing following the recommendations in [RFC8877]. This can be		sequencing following the recommendations in [RFC8877]. This can be
	accomplished by utilizing the Precision Time Protocol (PTP) format		accomplished by utilizing the Precision Time Protocol (PTP) format
	defined in IEEE Std. 1588 [IEEE Std. 1588] or Network Time Protocol		defined in IEEE Std. 1588 [IEEE Std. 1588] or Network Time Protocol
	(NTP) [RFC5905] formats. In that case, the timestamp resolution at		(NTP) [RFC5905] formats. In that case, the timestamp resolution at
	the node that builds the option MUST be fine enough to ensure that		the origin node that builds the option MUST be fine enough to ensure
	two consecutive packets are never stamped with the same value.		that two consecutive packets are never stamped with the same value.
			There is no requirement for this particular stamping function that
			the sense of time at the origin node is synchronized with the rest of
			the DetNet network.
	This specification also allows for an hybrid model with a coarse		This specification also allows for an hybrid model with a coarse
	grained packet sequence within a coarse grained time stamp. In that		grained packet sequence within a coarse grained time stamp. In that
	case, both a time stamp option and a wrapping counter options are		case, both a time stamp option and a wrapping counter options are
	found, and the counter is used to compare packets with the same time		found, and the counter is used to compare packets with the same time
	stamp.		stamp and ignored otherwise In that case, the size of the
			representation of the counter MUST be large enough to cover at least
			3 times the number of packets that may be sent with the same value of
			time stamp.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Option Type | Opt Data Len | Seq. Type | Reserved |		| Option Type | Opt Data Len | Seq. Type | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	. .		. .
	. Sequencing Information (variable Size) .		. Sequencing Information (variable Size) .
	. .		. .
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: Sequencing Option Format		Figure 1: Sequencing Option Format
	Sequencing Option fields:		Sequencing Option fields:
	Option Type: 8-bit identifier of the type of option. Value TBD by		Option Type: 8-bit identifier of the type of option. Value TBD by
	IANA.		IANA.
			Opt Data Len: 8-bit length of the option data.
			Reserved: 8-bit field, set to 0 and ignored on reception.
	Sequence Type: 8-bit identifier of the type of sequencing		Sequence Type: 8-bit identifier of the type of sequencing
	information. Value to be confirmed by IANA.		information. Value to be confirmed by IANA.
	+=======+============+===============+===========================+		+=======+==========+===============+===========================+
	| Seq. | Sequencing | Commin Name | Sequencing |		| Seq. | Category | Common Name | Sequencing Information |
	| Type | Type | | Information Format |		| Type | | | Format |
	| Value | | | |		| Value | | | |
	+=======+============+===============+===========================+		+=======+==========+===============+===========================+
	| 1 | Wrapping | Basic | 32-bit unsigned |		| 1 | Wrapping | Basic | 32-bit unsigned integer |
	| | Counter | Sequence | integer |		| | Counter | Sequence | |
	| | | Counter | |		| | | Counter | |
	+-------+============+---------------+---------------------------+		+-------+==========+---------------+---------------------------+
	| 2 | Wrapping | Zero-avoiding | 32-bit unsigned |		| 2 | Wrapping | Zero-avoiding | 32-bit unsigned integer, |
	| | Counter | Sequence | integer, wraps to 1 |		| | Counter | Sequence | wraps to 1 |
	| | | Counter | |		| | | Counter | |
	+-------+============+---------------+---------------------------+		+-------+==========+---------------+---------------------------+
	| 3 | Wrapping | RPL Sequence | 8-bit RPL sequence, |		| 3 | Wrapping | RPL Sequence | 8-bit RPL sequence, see |
	| | Counter | Counter | see section 7. of |		| | Counter | Counter | section 7. of [RFC6550] |
	| | | | [RFC6550] |		+-------+==========+---------------+---------------------------+
	+-------+============+---------------+---------------------------+		| 11 | Time | Fractional | NTP 64-bit Timestamp |
	| 11 | Time Stamp | Fractional | NTP 64-bit Timestamp |		| | Stamp | NTP | Format, see section |
	| | | NTP | Format, see section |		| | | | 4.2.1. of [RFC8877] |
	| | | | 4.2.1. of [RFC8877] |		+-------+==========+---------------+---------------------------+
	+-------+============+---------------+---------------------------+		| 12 | Time | Short NTP | NTP 32-bit Timestamp |
	| 12 | Time Stamp | Short NTP | NTP 32-bit Timestamp |		| | Stamp | | Format, see section |
	| | | | Format, see section |		| | | | 4.2.2. of [RFC8877] |
	| | | | 4.2.2. of [RFC8877] |		+-------+==========+---------------+---------------------------+
	+-------+============+---------------+---------------------------+		| 13 | Time | PTP | PTP 80-bit Timestamp |
	| 13 | Time Stamp | PTP | PTP 80-bit Timestamp |		| | Stamp | | Format, see [IEEE Std. |
	| | | | Format, see [IEEE |		| | | | 1588] |
	| | | | Std. 1588] |		+-------+==========+---------------+---------------------------+
	+-------+============+---------------+---------------------------+		| 14 | Time | Short PTP | PTP 64-bit Truncated |
	| 14 | Time Stamp | Short PTP | PTP 64-bit Truncated |		| | Stamp | | Timestamp Format, see |
	| | | | Timestamp Format, |		| | | | section 4.3. of [RFC8877] |
	| | | | see section 4.3. of |		+-------+==========+---------------+---------------------------+
	| | | | [RFC8877] |
	+-------+============+---------------+---------------------------+
	Table 1: Sequence Type values (suggested)		Table 1: Sequence Type values (suggested)
			Sequencing Information: Variable size, as indicated in Table 1.
	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
	Option [RFC6553] with a RPLInstanceID used as TrackID. This		Option [RFC6553] with a RPLInstanceID used as TrackID. This
	specification reuses the RPL option as a method to signal a DetNet		specification reuses the RPL option as a method to signal a DetNet
	path. In that case, the Projected-Route 'P' flag [RPL-PDAO] MUST be		path. In that case, the Projected-Route 'P' flag [RPL-PDAO] MUST be
	set to 1, and the O, R, F flags, as well as the Sender Rank field,		set to 1, and the O, R, F flags, as well as the Sender Rank field,
	MUST be set to 0 by the originator, forwarded as-is, and ignored on		MUST be set to 0 by the originator, forwarded as-is, and ignored on
	reception.		reception.
	3.3. DetNet Local Path Option		3.3. DetNet Local Path Option
	This specification also allows for an hybrid model with a coarse		In complement to the RPL option, this specification defines a
	grained packet sequence within a coarse grained time stamp. In that		protocol-independent Local Path Identifier, which is also taken from
	case, both a time stamp option and a wrapping counter options are		a namespace indicated by the IPv6 source address of the packet.
	found, and the counter is used to compare packets with the same time
	stamp.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Option Type | Opt Data Len | Local Path ID |		| Option Type | Opt Data Len | Local Path ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: DetNet Local Path Option Format		Figure 2: DetNet Local Path Option Format
	Sequencing Option fields:		Sequencing Option fields:
	skipping to change at page 7, line 34 ¶		skipping to change at page 7, line 32 ¶
	IANA.		IANA.
	Opt Data Len: 8-bit length of the option data, set to 2.		Opt Data Len: 8-bit length of the option data, set to 2.
	Local Path ID: 16-bit identifier of the DetNet Path, taken from a		Local Path ID: 16-bit identifier of the DetNet Path, taken from a
	local namespace associated with the IPv6 source address of the		local namespace associated with the IPv6 source address of the
	packet.		packet.
	3.4. DetNet Global Path Option		3.4. DetNet Global Path Option
	This specification also allows for an hybrid model with a coarse		The DetNet Global Path Option transports a global path identifier
	grained packet sequence within a coarse grained time stamp. In that		which is taken from a namespace indicated by the Origin Autonomous
	case, both a time stamp option and a wrapping counter options are		System (AS). When the DetNet path is contained within a single AS,
	found, and the counter is used to compare packets with the same time		the Origin Autonomous System field can be left to 0 indicating local
	stamp.		AS.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Option Type | Opt Data Len | Origin Autonomous System |		| Option Type | Opt Data Len | Origin Autonomous System |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Global Path ID |		| Global Path ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 3: DetNet Glocal Path Option Format		Figure 3: DetNet Glocal Path Option Format
	skipping to change at page 8, line 20 ¶		skipping to change at page 8, line 19 ¶
	Global Path ID: 32-bit identifier of the DetNet Path, taken from a		Global Path ID: 32-bit identifier of the DetNet Path, taken from a
	local namespace associated with the origin AS of the DetNet path.		local namespace associated with the origin AS of the DetNet path.
	The value of 0 signals a DetNet path that is constrained within		The value of 0 signals a DetNet path that is constrained within
	the local AS or the local administrative DetNet domain.		the local AS or the local administrative DetNet domain.
	4. Security Considerations		4. Security Considerations
	5. IANA Considerations		5. IANA Considerations
	This document has no IANA actions.		5.1. New Subregistry for the Sequencing Type
			This specification creates a new Subregistry for the "Sequencing Type
			of the Sequencing Option" under the "Internet Protocol Version 6
			(IPv6) Parameters" registry.
			* Possible values are 8-bit unsigned integers (0..255).
			* Registration procedure is "IETF Review" [RFC8126].
			* Initial allocation is as Suggested in Table 2:
			+-----------------+--------------------------------+-----------+
			| Suggested Value | Meaning | Reference |
			+-----------------+--------------------------------+-----------+
			| 1 | Basic Sequence Counter | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 2 | Zero-avoiding Sequence Counter | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 3 | RPL Sequence Counter | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 11 | Fractional NTP time stamp | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 12 | Short NTP time stamp | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 13 | PTP time stamp | THIS RFC |
			+-----------------+--------------------------------+-----------+
			| 14 | Short PTP time stamp | THIS RFC |
			+-----------------+--------------------------------+-----------+
			Table 2: Sequence Type values
			5.2. New Hop-by-Hop Options
			This specification updates the "Destination Options and Hop-by-Hop
			Options" under the "Internet Protocol Version 6 (IPv6) Parameters"
			registry with the (suggested) values below:
			+------+-----+-----+-------+---------------------------+-----------+
			| Hexa | act | chg | rest | Description | Reference |
			+------+-----+-----+-------+---------------------------+-----------+
			| 0x12 | 00 | 0 | 10010 | DetNet Sequencing Option | THIS RFC |
			+------+-----+-----+-------+---------------------------+-----------+
			| 0x13 | 00 | 0 | 10011 | DetNet Local Path Option | THIS RFC |
			+------+-----+-----+-------+---------------------------+-----------+
			| 0x14 | 00 | 0 | 10100 | DetNet Global Path Option | THIS RFC |
			+------+-----+-----+-------+---------------------------+-----------+
			Table 3: DetNet Hop-by-Hop Options
	6. Acknowledgments		6. Acknowledgments
	TBD		TBD
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6		[IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", STD 86, RFC 8200,		(IPv6) Specification", STD 86, RFC 8200,
	DOI 10.17487/RFC8200, July 2017,		DOI 10.17487/RFC8200, July 2017,
	<https://www.rfc-editor.org/info/rfc8200>.		<https://www.rfc-editor.org/info/rfc8200>.
			[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
			Writing an IANA Considerations Section in RFCs", BCP 26,
			RFC 8126, DOI 10.17487/RFC8126, June 2017,
			<https://www.rfc-editor.org/info/rfc8126>.
	[RFC8877] Mizrahi, T., Fabini, J., and A. Morton, "Guidelines for		[RFC8877] Mizrahi, T., Fabini, J., and A. Morton, "Guidelines for
	Defining Packet Timestamps", RFC 8877,		Defining Packet Timestamps", RFC 8877,
	DOI 10.17487/RFC8877, September 2020,		DOI 10.17487/RFC8877, September 2020,
	<https://www.rfc-editor.org/info/rfc8877>.		<https://www.rfc-editor.org/info/rfc8877>.
	[HbH-PROCESS]		[HbH-PROCESS]
	Hinden, R. M. and G. Fairhurst, "IPv6 Hop-by-Hop Options		Hinden, R. M. and G. Fairhurst, "IPv6 Hop-by-Hop Options
	Processing Procedures", Work in Progress, Internet-Draft,		Processing Procedures", Work in Progress, Internet-Draft,
	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-
End of changes. 19 change blocks.
	69 lines changed or deleted		133 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/