rfc9359v2.txt		rfc9359.txt
	skipping to change at line 60 ¶		skipping to change at line 60 ¶
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction
	2. Conventions		2. Conventions
	2.1. Requirements Language		2.1. Requirements Language
	2.2. Abbreviations		2.2. Abbreviations
	3. IOAM Capabilities Formats		3. IOAM Capabilities Formats
	3.1. IOAM Capabilities Query Container		3.1. IOAM Capabilities Query Container
	3.2. IOAM Capabilities Response Container		3.2. IOAM Capabilities Response Container
	3.2.1. IOAM Pre-Allocated Tracing Capabilities Object		3.2.1. IOAM Pre-allocated Tracing Capabilities Object
	3.2.2. IOAM Incremental Tracing Capabilities Object		3.2.2. IOAM Incremental Tracing Capabilities Object
	3.2.3. IOAM Proof-of-Transit Capabilities Object		3.2.3. IOAM Proof of Transit Capabilities Object
	3.2.4. IOAM Edge-to-Edge Capabilities Object		3.2.4. IOAM Edge-to-Edge Capabilities Object
	3.2.5. IOAM DEX Capabilities Object		3.2.5. IOAM DEX Capabilities Object
	3.2.6. IOAM End-of-Domain Object		3.2.6. IOAM End-of-Domain Object
	4. Operational Guide		4. Operational Guide
	5. IANA Considerations		5. IANA Considerations
	5.1. IOAM SoP Capability Registry		5.1. IOAM SoP Capability Registry
	5.2. IOAM TSF Capability Registry		5.2. IOAM TSF Capability Registry
	6. Security Considerations		6. Security Considerations
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	skipping to change at line 147 ¶		skipping to change at line 147 ¶
	encapsulating node or the IOAM decapsulating node is a host, the		encapsulating node or the IOAM decapsulating node is a host, the
	availability can be an issue. Furthermore, it might be too		availability can be an issue. Furthermore, it might be too
	challenging to reflect enabled IOAM capabilities at the IOAM		challenging to reflect enabled IOAM capabilities at the IOAM
	transit and IOAM decapsulating node if these are controlled by a		transit and IOAM decapsulating node if these are controlled by a
	local policy depending on the identity of the IOAM encapsulating		local policy depending on the identity of the IOAM encapsulating
	node.		node.
	This document specifies formats and objects that can be used in the		This document specifies formats and objects that can be used in the
	extension of echo request/reply mechanisms used in IPv6 (including		extension of echo request/reply mechanisms used in IPv6 (including
	Segment Routing over IPv6 (SRv6) data plane), MPLS (including Segment		Segment Routing over IPv6 (SRv6) data plane), MPLS (including Segment
	Routing over MPLS (SR-MPLS) data plane), SFC, and BIER environments,		Routing over MPLS (SR-MPLS) data plane), Service Function Chain
	which can be used within the IOAM-Domain, allowing the IOAM		(SFC), and Bit Index Explicit Replication (BIER) environments, which
	encapsulating node to discover the enabled IOAM capabilities of each		can be used within the IOAM-Domain, allowing the IOAM encapsulating
	IOAM transit and IOAM decapsulating node.		node to discover the enabled IOAM capabilities of each IOAM transit
			and IOAM decapsulating node.
	The following documents contain references to the echo request/reply		The following documents contain references to the echo request/reply
	mechanisms used in IPv6 (including SRv6), MPLS (including SR-MPLS),		mechanisms used in IPv6 (including SRv6), MPLS (including SR-MPLS),
	SFC, and BIER environments:		SFC, and BIER environments:
	* "Internet Control Message Protocol (ICMPv6) for the Internet		* "Internet Control Message Protocol (ICMPv6) for the Internet
	Protocol Version 6 (IPv6) Specification" [RFC4443]		Protocol Version 6 (IPv6) Specification" [RFC4443]
	* "IPv6 Node Information Queries" [RFC4620]		* "IPv6 Node Information Queries" [RFC4620]
	skipping to change at line 350 ¶		skipping to change at line 351 ¶
	more than once, only if listed with a different Namespace-ID.		more than once, only if listed with a different Namespace-ID.
	Similar to the container, each object has an object header that is		Similar to the container, each object has an object header that is
	used to identify the type and length of the object payload. The		used to identify the type and length of the object payload. The
	object payload MUST be defined such that it falls on a 4-octet		object payload MUST be defined such that it falls on a 4-octet
	boundary.		boundary.
	The length, structure, and definition of the object header depends on		The length, structure, and definition of the object header depends on
	the specific deployment environment.		the specific deployment environment.
	3.2.1. IOAM Pre-Allocated Tracing Capabilities Object		3.2.1. IOAM Pre-allocated Tracing Capabilities Object
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	. .		. .
	. IOAM Pre-Allocated Tracing Capabilities Object Header .		. IOAM Pre-allocated Tracing Capabilities Object Header .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IOAM-Trace-Type | Reserved |W|		| IOAM-Trace-Type | Reserved |W|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Namespace-ID | Ingress_MTU |		| Namespace-ID | Ingress_MTU |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Ingress_if_id (short or wide format) ...... |		| Ingress_if_id (short or wide format) ...... |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 3: IOAM Pre-Allocated Tracing Capabilities Object		Figure 3: IOAM Pre-allocated Tracing Capabilities Object
	When the IOAM Pre-Allocated Tracing Capabilities Object is present in		When the IOAM Pre-allocated Tracing Capabilities Object is present in
	the IOAM Capabilities Response Container, the sending node is an IOAM		the IOAM Capabilities Response Container, the sending node is an IOAM
	transit node, and the IOAM pre-allocated tracing function is enabled		transit node, and the IOAM pre-allocated tracing function is enabled
	at this IOAM transit node.		at this IOAM transit node.
	The IOAM-Trace-Type field has the same definition as what's specified		The IOAM-Trace-Type field has the same definition as what's specified
	in Section 4.4 of [RFC9197].		in Section 4.4 of [RFC9197].
	The Reserved field MUST be zeroed on transmission and ignored on		The Reserved field MUST be zeroed on transmission and ignored on
	receipt.		receipt.
	skipping to change at line 446 ¶		skipping to change at line 447 ¶
	of the ingress interface from which the sending node received the		of the ingress interface from which the sending node received the
	echo request.		echo request.
	The Ingress_if_id field has 16 bits (in short format) or 32 bits (in		The Ingress_if_id field has 16 bits (in short format) or 32 bits (in
	wide format) and specifies the identifier of the ingress interface		wide format) and specifies the identifier of the ingress interface
	from which the sending node received the echo request. If the W-bit		from which the sending node received the echo request. If the W-bit
	is cleared, the Ingress_if_id field has 16 bits; then the 16 bits		is cleared, the Ingress_if_id field has 16 bits; then the 16 bits
	following the Ingress_if_id field are reserved for future use, MUST		following the Ingress_if_id field are reserved for future use, MUST
	be set to zero, and MUST be ignored when non-zero.		be set to zero, and MUST be ignored when non-zero.
	3.2.3. IOAM Proof-of-Transit Capabilities Object		3.2.3. IOAM Proof of Transit Capabilities Object
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	. .		. .
	. IOAM Proof-of-Transit Capabilities Object Header .		. IOAM Proof of Transit Capabilities Object Header .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Namespace-ID | IOAM-POT-Type |SoP| Reserved |		| Namespace-ID | IOAM-POT-Type |SoP| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 5: IOAM Proof-of-Transit Capabilities Object		Figure 5: IOAM Proof of Transit Capabilities Object
	When the IOAM Proof-of-Transit Capabilities Object is present in the		When the IOAM Proof of Transit Capabilities Object is present in the
	IOAM Capabilities Response Container, the sending node is an IOAM		IOAM Capabilities Response Container, the sending node is an IOAM
	transit node and the IOAM Proof of Transit function is enabled at		transit node and the IOAM Proof of Transit function is enabled at
	this IOAM transit node.		this IOAM transit node.
	The Namespace-ID field has the same definition as what's specified in		The Namespace-ID field has the same definition as what's specified in
	Section 4.3 of [RFC9197]. It MUST be one of the Namespace-IDs listed		Section 4.3 of [RFC9197]. It MUST be one of the Namespace-IDs listed
	in the IOAM Capabilities Query Object of the echo request.		in the IOAM Capabilities Query Object of the echo request.
	The IOAM-POT-Type field has the same definition as what's specified		The IOAM-POT-Type field has the same definition as what's specified
	in Section 4.5 of [RFC9197].		in Section 4.5 of [RFC9197].
End of changes. 11 change blocks.
	14 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.48.