rfc9013v5.txt		rfc9013.txt
	skipping to change at line 185 ¶		skipping to change at line 185 ¶
	Tunnel Parameter Sub-Type (2 octets): Each sub-type defines a		Tunnel Parameter Sub-Type (2 octets): Each sub-type defines a
	parameter of the Tunnel Sub-TLV. Sub-types are registered in the		parameter of the Tunnel Sub-TLV. Sub-types are registered in the
	IANA registry "OSPF Tunnel Parameter Sub-TLVs" (see Section 7.2).		IANA registry "OSPF Tunnel Parameter Sub-TLVs" (see Section 7.2).
	Tunnel Parameter Length (2 octets): Unsigned 16-bit integer		Tunnel Parameter Length (2 octets): Unsigned 16-bit integer
	indicating the total number of octets of the Tunnel Parameter		indicating the total number of octets of the Tunnel Parameter
	Value field.		Value field.
	Tunnel Parameter Value (variable): Encodings of the Value field		Tunnel Parameter Value (variable): Encodings of the Value field
	depend on the Sub-TLV type. The following subsections define the		depend on the sub-TLV type. The following subsections define the
	encoding in detail.		encoding in detail.
	Any unknown Tunnel Parameter sub-type MUST be ignored and skipped		Any unknown Tunnel Parameter sub-type MUST be ignored and skipped
	upon receipt. When a reserved value (see Section 7.2) is seen in an		upon receipt. When a reserved value (see Section 7.2) is seen in an
	LSA, it MUST be treated as an invalid Tunnel Parameter Sub-TLV. When		LSA, it MUST be treated as an invalid Tunnel Parameter Sub-TLV. When
	a Tunnel Parameter Value has an incorrect syntax or semantics, it		a Tunnel Parameter Value has an incorrect syntax or semantics, it
	MUST be treated as an invalid Tunnel Parameter Sub-TLV. If a Tunnel		MUST be treated as an invalid Tunnel Parameter Sub-TLV. If a Tunnel
	Parameter Sub-TLV is invalid, its Tunnel Sub-TLV MUST be ignored.		Parameter Sub-TLV is invalid, its Tunnel Sub-TLV MUST be ignored.
	However, other Tunnel Sub-TLVs MUST be considered.		However, other Tunnel Sub-TLVs MUST be considered.
	5.1. Encapsulation Sub-TLV		5.1. Encapsulation Sub-TLV
	This Sub-TLV type is 1. The syntax, semantics, and usage of its		This sub-TLV type is 1. The syntax, semantics, and usage of its
	Value field are defined in Section 3.2 ("Encapsulation Sub-TLVs for		Value field are defined in Section 3.2 ("Encapsulation Sub-TLVs for
	Particular Tunnel Types") of [RFC9012].		Particular Tunnel Types") of [RFC9012].
	5.2. Protocol Type Sub-TLV		5.2. Protocol Type Sub-TLV
	This Sub-TLV type is 2. The syntax, semantics, and usage of its		This sub-TLV type is 2. The syntax, semantics, and usage of its
	Value field are defined in Section 3.4.1 ("Protocol Type Sub-TLV") of		Value field are defined in Section 3.4.1 ("Protocol Type Sub-TLV") of
	[RFC9012].		[RFC9012].
	5.3. Tunnel Egress Endpoint Sub-TLV		5.3. Tunnel Egress Endpoint Sub-TLV
	The Tunnel Egress Endpoint Sub-TLV specifies the address of the		The Tunnel Egress Endpoint Sub-TLV specifies the address of the
	egress endpoint of the tunnel -- that is, the address of the router		egress endpoint of the tunnel -- that is, the address of the router
	that will decapsulate the payload.		that will decapsulate the payload.
	This Sub-TLV type is 3. It MUST be present once and only once in a		This sub-TLV type is 3. It MUST be present once and only once in a
	given Tunnel Sub-TLV. The Value field contains two subfields:		given Tunnel Sub-TLV. The Value field contains two subfields:
	* a two-octet Address Family subfield		* a two-octet Address Family subfield
	* an Address subfield, whose length depends upon the Address Family		* an Address subfield, whose length depends upon the Address Family
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Family | Address ~		| Address Family | Address ~
	skipping to change at line 250 ¶		skipping to change at line 250 ¶
	MUST contain the value 6.		MUST contain the value 6.
	If the Address Family subfield contains the value for IPv6, the		If the Address Family subfield contains the value for IPv6, the
	address subfield MUST contain an IPv6 address (a /128 IPv6 prefix).		address subfield MUST contain an IPv6 address (a /128 IPv6 prefix).
	In this case, the Length field of the Tunnel Egress Endpoint Sub-TLV		In this case, the Length field of the Tunnel Egress Endpoint Sub-TLV
	MUST contain the value 18 (0x12). IPv6 link-local addresses are not		MUST contain the value 18 (0x12). IPv6 link-local addresses are not
	valid values of the IP address field.		valid values of the IP address field.
	5.4. Color Sub-TLV		5.4. Color Sub-TLV
	This Sub-TLV type is 4. It may appear zero or more times in a given		This sub-TLV type is 4. It may appear zero or more times in a given
	Tunnel Sub-TLV. The Value field is a 4-octet opaque unsigned		Tunnel Sub-TLV. The Value field is a 4-octet opaque unsigned
	integer.		integer.
	The color value is user-defined and configured locally on the		The color value is user-defined and configured locally on the
	advertising routers. It may be used by service providers to define		advertising routers. It may be used by service providers to define
	policies on the tunnel encapsulator routers, for example, to control		policies on the tunnel encapsulator routers, for example, to control
	the selection of the tunnel to use.		the selection of the tunnel to use.
	This color value can be referenced by BGP routes carrying the Color		This color value can be referenced by BGP routes carrying the Color
	Extended Community [RFC9012]. If the tunnel is used to reach the BGP		Extended Community [RFC9012]. If the tunnel is used to reach the BGP
	next hop of BGP routes, then attaching a Color Extended Community to		next hop of BGP routes, then attaching a Color Extended Community to
	those routes expresses the willingness of the BGP speaker to use a		those routes expresses the willingness of the BGP speaker to use a
	tunnel of the same color.		tunnel of the same color.
	5.5. Load-Balancing Block Sub-TLV		5.5. Load-Balancing Block Sub-TLV
	This Sub-TLV type is 5. The syntax, semantics, and usage of its		This sub-TLV type is 5. The syntax, semantics, and usage of its
	Value field are defined in [RFC5640].		Value field are defined in [RFC5640].
	5.6. DS Field Sub-TLV		5.6. DS Field Sub-TLV
	This Sub-TLV type is 6. The syntax, semantics, and usage of its		This sub-TLV type is 6. The syntax, semantics, and usage of its
	Value field are defined in Section 3.3.1 ("DS Field") of [RFC9012].		Value field are defined in Section 3.3.1 ("DS Field") of [RFC9012].
	5.7. UDP Destination Port Sub-TLV		5.7. UDP Destination Port Sub-TLV
	This Sub-TLV type is 7. The syntax, semantics, and usage of its		This sub-TLV type is 7. The syntax, semantics, and usage of its
	Value field are defined in Section 3.3.2 ("UDP Destination Port") of		Value field are defined in Section 3.3.2 ("UDP Destination Port") of
	[RFC9012].		[RFC9012].
	6. Operation		6. Operation
	The advertisement of a Tunnel Encapsulations Sub-TLV indicates that		The advertisement of a Tunnel Encapsulations Sub-TLV indicates that
	the advertising router supports a particular tunnel decapsulation		the advertising router supports a particular tunnel decapsulation
	along with the parameters to be used for the tunnel. The decision to		along with the parameters to be used for the tunnel. The decision to
	use that tunnel is driven by the capability of the tunnel		use that tunnel is driven by the capability of the tunnel
	encapsulator router to support the encapsulation type and the policy		encapsulator router to support the encapsulation type and the policy
End of changes. 8 change blocks.
	8 lines changed or deleted		8 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/