rfc9830v3.txt		rfc9830.txt
	skipping to change at line 77 ¶		skipping to change at line 77 ¶
	2. SR Policy Encoding		2. SR Policy Encoding
	2.1. SR Policy SAFI and NLRI		2.1. SR Policy SAFI and NLRI
	2.2. SR Policy and Tunnel Encapsulation Attribute		2.2. SR Policy and Tunnel Encapsulation Attribute
	2.3. Applicability of Tunnel Encapsulation Attribute Sub-TLVs		2.3. Applicability of Tunnel Encapsulation Attribute Sub-TLVs
	2.4. SR Policy Sub-TLVs		2.4. SR Policy Sub-TLVs
	2.4.1. Preference Sub-TLV		2.4.1. Preference Sub-TLV
	2.4.2. Binding SID Sub-TLV		2.4.2. Binding SID Sub-TLV
	2.4.3. SRv6 Binding SID Sub-TLV		2.4.3. SRv6 Binding SID Sub-TLV
	2.4.4. Segment List Sub-TLV		2.4.4. Segment List Sub-TLV
	2.4.5. Explicit NULL Label Policy Sub-TLV		2.4.5. Explicit NULL Label Policy Sub-TLV
	2.4.6. Policy Priority Sub-TLV		2.4.6. SR Policy Priority Sub-TLV
	2.4.7. Policy Candidate Path Name Sub-TLV		2.4.7. SR Policy Candidate Path Name Sub-TLV
	2.4.8. Policy Name Sub-TLV		2.4.8. SR Policy Name Sub-TLV
	3. Color Extended Community		3. Color Extended Community
	4. SR Policy Operations		4. SR Policy Operations
	4.1. Advertisement of SR Policies		4.1. Advertisement of SR Policies
	4.2. Reception of an SR Policy NLRI		4.2. Reception of an SR Policy NLRI
	4.2.1. Validation of an SR Policy NLRI		4.2.1. Validation of an SR Policy NLRI
	4.2.2. Eligibility for Local Use of an SR Policy NLRI		4.2.2. Eligibility for Local Use of an SR Policy NLRI
	4.2.3. Propagation of an SR Policy		4.2.3. Propagation of an SR Policy
	5. Error Handling and Fault Management		5. Error Handling and Fault Management
	6. IANA Considerations		6. IANA Considerations
	6.1. Subsequent Address Family Identifiers (SAFI) Parameters		6.1. Subsequent Address Family Identifiers (SAFI) Parameters
	skipping to change at line 263 ¶		skipping to change at line 263 ¶
	The SR Policy SAFI with code point 73 is introduced in this document.		The SR Policy SAFI with code point 73 is introduced in this document.
	The AFI used MUST be IPv4(1) or IPv6(2).		The AFI used MUST be IPv4(1) or IPv6(2).
	The SR Policy SAFI uses the NLRI format defined as follows:		The SR Policy SAFI uses the NLRI format defined as follows:
	+------------------+		+------------------+
	| NLRI Length | 1 octet		| NLRI Length | 1 octet
	+------------------+		+------------------+
	| Distinguisher | 4 octets		| Distinguisher | 4 octets
	+------------------+		+------------------+
	| Policy Color | 4 octets		| Color | 4 octets
	+------------------+		+------------------+
	| Endpoint | 4 or 16 octets		| Endpoint | 4 or 16 octets
	+------------------+		+------------------+
	Figure 1: SR Policy SAFI Format		Figure 1: SR Policy SAFI Format
	Where:		Where:
	NLRI Length: 1 octet indicating the length expressed in bits as		NLRI Length: 1 octet indicating the length expressed in bits as
	defined in [RFC4760]. When AFI = 1, the value MUST be 96; when		defined in [RFC4760]. When AFI = 1, the value MUST be 96; when
	skipping to change at line 289 ¶		skipping to change at line 289 ¶
	unique NLRIs the following situations:		unique NLRIs the following situations:
	* to differentiate multiple CPs of the same SR Policy		* to differentiate multiple CPs of the same SR Policy
	* to differentiate CPs meant for different headends but having		* to differentiate CPs meant for different headends but having
	the same Color and Endpoint		the same Color and Endpoint
	The distinguisher is the discriminator of the SR Policy CP as		The distinguisher is the discriminator of the SR Policy CP as
	specified in Section 2.5 of [RFC9256].		specified in Section 2.5 of [RFC9256].
	Policy Color: 4 octets that carry an unsigned non-zero integer value		Color: 4 octets that carry an unsigned non-zero integer value
	indicating the Color of the SR Policy as specified in Section 2.1		indicating the Color of the SR Policy as specified in Section 2.1
	of [RFC9256]. The Color is used to match the Color of the		of [RFC9256]. The Color is used to match the Color of the
	destination prefixes to steer traffic into the SR Policy as		destination prefixes to steer traffic into the SR Policy as
	specified in Section 8 of [RFC9256].		specified in Section 8 of [RFC9256].
	Endpoint: a value that identifies the Endpoint of an SR Policy. The		Endpoint: a value that identifies the Endpoint of an SR Policy. The
	Endpoint may represent a single node or a set of nodes (e.g., an		Endpoint may represent a single node or a set of nodes (e.g., an
	anycast address). The Endpoint is an IPv4 (4-octet) address or an		anycast address). The Endpoint is an IPv4 (4-octet) address or an
	IPv6 (16-octet) address according to the AFI of the NLRI. The		IPv6 (16-octet) address according to the AFI of the NLRI. The
	address can be either unicast or an unspecified address (0.0.0.0		address can be either unicast or an unspecified address (0.0.0.0
	skipping to change at line 371 ¶		skipping to change at line 371 ¶
	Encapsulation Attribute defined in [RFC9012] using a Tunnel Type		Encapsulation Attribute defined in [RFC9012] using a Tunnel Type
	called the "SR Policy" type with code point 15. The use of the SR		called the "SR Policy" type with code point 15. The use of the SR
	Policy Tunnel Type is applicable only for the AFI/SAFI pairs of		Policy Tunnel Type is applicable only for the AFI/SAFI pairs of
	(1/73, 2/73). This document specifies the use of the Tunnel		(1/73, 2/73). This document specifies the use of the Tunnel
	Encapsulation Attribute with the SR Policy Tunnel Type and the use of		Encapsulation Attribute with the SR Policy Tunnel Type and the use of
	any other Tunnel Type with the SR Policy SAFI MUST be considered		any other Tunnel Type with the SR Policy SAFI MUST be considered
	malformed and handled by the "treat-as-withdraw" strategy [RFC7606].		malformed and handled by the "treat-as-withdraw" strategy [RFC7606].
	The SR Policy Encoding structure is as follows:		The SR Policy Encoding structure is as follows:
	SR Policy SAFI NLRI: <Distinguisher, Policy-Color, Endpoint>		SR Policy SAFI NLRI: <Distinguisher, Color, Endpoint>
	Attributes:		Attributes:
	Tunnel Encapsulation Attribute (23)		Tunnel Encapsulation Attribute (23)
	Tunnel Type: SR Policy (15)		Tunnel Type: SR Policy (15)
	Binding SID		Binding SID
	Preference		Preference
	Priority		Priority
	Policy Name		SR Policy Name
	Policy Candidate Path Name		SR Policy Candidate Path Name
	Explicit NULL Label Policy (ENLP)		Explicit NULL Label Policy (ENLP)
	Segment List		Segment List
	Weight		Weight
	Segment		Segment
	Segment		Segment
	...		...
	...		...
	Figure 2: SR Policy Encoding		Figure 2: SR Policy Encoding
	Where:		Where:
	* The SR Policy SAFI NLRI is defined in Section 2.1.		* The SR Policy SAFI NLRI is defined in Section 2.1.
	* The Tunnel Encapsulation Attribute is defined in [RFC9012].		* The Tunnel Encapsulation Attribute is defined in [RFC9012].
	* The Tunnel Type is set to 15.		* The Tunnel Type is set to 15.
	* Preference, Binding SID, Priority, Policy Name, Policy Candidate		* Preference, Binding SID, Priority, SR Policy Name, SR Policy
	Path Name, ENLP, Segment-List, Weight, and Segment sub-TLVs are		Candidate Path Name, ENLP, Segment-List, Weight, and Segment sub-
	defined in Section 2.4.		TLVs are defined in Section 2.4.
	* Additional sub-TLVs may be defined in the future.		* Additional sub-TLVs may be defined in the future.
	A Tunnel Encapsulation Attribute MUST NOT contain more than one TLV		A Tunnel Encapsulation Attribute MUST NOT contain more than one TLV
	of type "SR Policy"; such updates MUST be considered malformed and		of type "SR Policy"; such updates MUST be considered malformed and
	handled by the "treat-as-withdraw" strategy [RFC7606].		handled by the "treat-as-withdraw" strategy [RFC7606].
	BGP does not need to perform the validation of the tunnel (i.e., SR		BGP does not need to perform the validation of the tunnel (i.e., SR
	Policy) itself as indicated in Section 6 of [RFC9012]. The		Policy) itself as indicated in Section 6 of [RFC9012]. The
	validation of the SR Policy information that is advertised using the		validation of the SR Policy information that is advertised using the
	skipping to change at line 432 ¶		skipping to change at line 432 ¶
	Similarly, any other sub-TLVs, including those specified in		Similarly, any other sub-TLVs, including those specified in
	[RFC9012], that do not have explicitly defined applicability to the		[RFC9012], that do not have explicitly defined applicability to the
	SR Policy SAFI MUST be ignored by the BGP speaker and MAY be removed		SR Policy SAFI MUST be ignored by the BGP speaker and MAY be removed
	from the Tunnel Encapsulation Attribute during propagation.		from the Tunnel Encapsulation Attribute during propagation.
	2.4. SR Policy Sub-TLVs		2.4. SR Policy Sub-TLVs
	This section specifies the sub-TLVs defined for encoding the		This section specifies the sub-TLVs defined for encoding the
	information about the SR Policy Candidate Path.		information about the SR Policy Candidate Path.
	Preference, Binding SID, SRv6 Binding SID, Segment-List, Priority,		Preference, Binding SID, SRv6 Binding SID, Segment-List, Priority, SR
	Policy Name, Policy Candidate Path Name, and Explicit NULL Label		Policy Name, SR Policy Candidate Path Name, and Explicit NULL Label
	Policy are all optional sub-TLVs introduced for the BGP Tunnel		Policy are all optional sub-TLVs introduced for the BGP Tunnel
	Encapsulation Attribute [RFC9012] being defined in this section.		Encapsulation Attribute [RFC9012] being defined in this section.
	Weight and Segment are sub-TLVs of the Segment-List sub-TLV mentioned		Weight and Segment are sub-TLVs of the Segment-List sub-TLV mentioned
	above.		above.
	An early draft version of this document included only the Binding SID		An early draft version of this document included only the Binding SID
	sub-TLV that could be used for both SR-MPLS and SRv6 BSIDs. The SRv6		sub-TLV that could be used for both SR-MPLS and SRv6 BSIDs. The SRv6
	Binding SID TLV was introduced in later versions to support the		Binding SID TLV was introduced in later versions to support the
	advertisement of additional SRv6 capabilities without affecting		advertisement of additional SRv6 capabilities without affecting
	skipping to change at line 1035 ¶		skipping to change at line 1035 ¶
	This field can have one of the values as specified in		This field can have one of the values as specified in
	Section 6.10. The ENLP unassigned values may be used for future		Section 6.10. The ENLP unassigned values may be used for future
	extensions. Implementations adhering to this document MUST ignore		extensions. Implementations adhering to this document MUST ignore
	the ENLP sub-TLV with unrecognized values (viz. other than 1		the ENLP sub-TLV with unrecognized values (viz. other than 1
	through 4). The behavior signaled in this sub-TLV MAY be		through 4). The behavior signaled in this sub-TLV MAY be
	overridden by local configuration by the network operator based on		overridden by local configuration by the network operator based on
	their deployment requirements. Section 4.1 of [RFC9256] describes		their deployment requirements. Section 4.1 of [RFC9256] describes
	the behavior on the headend for the handling of the Explicit NULL		the behavior on the headend for the handling of the Explicit NULL
	label.		label.
	2.4.6. Policy Priority Sub-TLV		2.4.6. SR Policy Priority Sub-TLV
	An operator MAY set the Policy Priority sub-TLV to indicate the order		An operator MAY set the SR Policy Priority sub-TLV to indicate the
	in which the SR policies are recomputed upon topological change. The		order in which the SR policies are recomputed upon topological
	contents of this sub-TLV are used by the SRPM as described in		change. The contents of this sub-TLV are used by the SRPM as
	Section 2.12 of [RFC9256].		described in Section 2.12 of [RFC9256].
	The Priority sub-TLV is OPTIONAL; it MUST NOT appear more than once		The Priority sub-TLV is OPTIONAL; it MUST NOT appear more than once
	in the SR Policy encoding.		in the SR Policy encoding.
	The Priority sub-TLV has the following format:		The Priority sub-TLV has the following format:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length | Priority | RESERVED |		| Type | Length | Priority | RESERVED |
	skipping to change at line 1068 ¶		skipping to change at line 1068 ¶
	Length: Specifies the length of the value field (i.e., not including		Length: Specifies the length of the value field (i.e., not including
	Type and Length fields) in terms of octets. The value MUST be 2.		Type and Length fields) in terms of octets. The value MUST be 2.
	Priority: A 1-octet value indicating the priority as specified in		Priority: A 1-octet value indicating the priority as specified in
	Section 2.12 of [RFC9256].		Section 2.12 of [RFC9256].
	RESERVED: 1 octet of reserved bits. This field MUST be set to zero		RESERVED: 1 octet of reserved bits. This field MUST be set to zero
	on transmission and MUST be ignored on receipt.		on transmission and MUST be ignored on receipt.
	2.4.7. Policy Candidate Path Name Sub-TLV		2.4.7. SR Policy Candidate Path Name Sub-TLV
	An operator MAY set the Policy Candidate Path Name sub-TLV to attach		An operator MAY set the SR Policy Candidate Path Name sub-TLV to
	a symbolic name to the SR Policy CP.		attach a symbolic name to the SR Policy CP.
	Usage of the Policy Candidate Path Name sub-TLV is described in		Usage of the SR Policy Candidate Path Name sub-TLV is described in
	Section 2.6 of [RFC9256].		Section 2.6 of [RFC9256].
	The Policy Candidate Path Name sub-TLV may exceed 255 bytes in length		The SR Policy Candidate Path Name sub-TLV may exceed 255 bytes in
	due to a long name. A 2-octet length is thus required. According to		length due to a long name. A 2-octet length is thus required.
	Section 2 of [RFC9012], the sub-TLV type defines the size of the		According to Section 2 of [RFC9012], the sub-TLV type defines the
	Length field. Therefore, for the Policy Candidate Path Name sub-TLV,		size of the Length field. Therefore, for the SR Policy Candidate
	a code point of 128 or higher is used.		Path Name sub-TLV, a code point of 128 or higher is used.
	It is RECOMMENDED that the size of the symbolic name for the CP be		It is RECOMMENDED that the size of the symbolic name for the CP be
	limited to 255 bytes. Implementations MAY choose to truncate long		limited to 255 bytes. Implementations MAY choose to truncate long
	names to 255 bytes when signaling via BGP.		names to 255 bytes when signaling via BGP.
	The Policy Candidate Path Name sub-TLV is OPTIONAL; it MUST NOT		The SR Policy Candidate Path Name sub-TLV is OPTIONAL; it MUST NOT
	appear more than once in the SR Policy encoding.		appear more than once in the SR Policy encoding.
	The Policy Candidate Path Name sub-TLV has the following format:		The SR Policy Candidate Path Name sub-TLV has the following format:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length | RESERVED |		| Type | Length | RESERVED |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	// Policy Candidate Path Name //		// SR Policy Candidate Path Name //
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 17: Policy Candidate Path Name Sub-TLV		Figure 17: SR Policy Candidate Path Name Sub-TLV
	Where:		Where:
	Type: 129		Type: 129
	Length: Specifies the length of the value field (i.e., not including		Length: Specifies the length of the value field (i.e., not including
	Type and Length fields) in terms of octets. The value is		Type and Length fields) in terms of octets. The value is
	variable.		variable.
	RESERVED: 1 octet of reserved bits. This field MUST be set to zero		RESERVED: 1 octet of reserved bits. This field MUST be set to zero
	on transmission and MUST be ignored on receipt.		on transmission and MUST be ignored on receipt.
	Policy Candidate Path Name: Symbolic name for the SR Policy CP		SR Policy Candidate Path Name: Symbolic name for the SR Policy CP
	without a NULL terminator with encoding as specified in		without a NULL terminator with encoding as specified in
	Section 2.6 of [RFC9256].		Section 2.6 of [RFC9256].
	2.4.8. Policy Name Sub-TLV		2.4.8. SR Policy Name Sub-TLV
	An operator MAY set the Policy Name sub-TLV to associate a symbolic		An operator MAY set the SR Policy Name sub-TLV to associate a
	name with the SR Policy for which the CP is being advertised via the		symbolic name with the SR Policy for which the CP is being advertised
	SR Policy NLRI.		via the SR Policy NLRI.
	Usage of the Policy Name sub-TLV is described in Section 2.1 of		Usage of the SR Policy Name sub-TLV is described in Section 2.1 of
	[RFC9256].		[RFC9256].
	The Policy Name sub-TLV may exceed 255 bytes in length due to a long		The SR Policy Name sub-TLV may exceed 255 bytes in length due to a
	policy name. A 2-octet length is thus required. According to		long SR Policy name. A 2-octet length is thus required. According
	Section 2 of [RFC9012], the sub-TLV type defines the size of the		to Section 2 of [RFC9012], the sub-TLV type defines the size of the
	Length field. Therefore, for the Policy Name sub-TLV, a code point		Length field. Therefore, for the SR Policy Name sub-TLV, a code
	of 128 or higher is used.		point of 128 or higher is used.
	It is RECOMMENDED that the size of the symbolic name for the SR		It is RECOMMENDED that the size of the symbolic name for the SR
	Policy be limited to 255 bytes. Implementations MAY choose to		Policy be limited to 255 bytes. Implementations MAY choose to
	truncate long names to 255 bytes when signaling via BGP.		truncate long names to 255 bytes when signaling via BGP.
	The Policy Name sub-TLV is OPTIONAL; it MUST NOT appear more than		The SR Policy Name sub-TLV is OPTIONAL; it MUST NOT appear more than
	once in the SR Policy encoding.		once in the SR Policy encoding.
	The Policy Name sub-TLV has the following format:		The SR Policy Name sub-TLV has the following format:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length | RESERVED |		| Type | Length | RESERVED |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	// Policy Name //		// SR Policy Name //
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 18: Policy Name Sub-TLV		Figure 18: SR Policy Name Sub-TLV
	Where:		Where:
	Type: 130		Type: 130
	Length: Specifies the length of the value field (i.e., not including		Length: Specifies the length of the value field (i.e., not including
	Type and Length fields) in terms of octets. The value is		Type and Length fields) in terms of octets. The value is
	variable.		variable.
	RESERVED: 1 octet of reserved bits. This field MUST be set to zero		RESERVED: 1 octet of reserved bits. This field MUST be set to zero
	on transmission and MUST be ignored on receipt.		on transmission and MUST be ignored on receipt.
	Policy Name: Symbolic name for the SR Policy without a NULL		SR Policy Name: Symbolic name for the SR Policy without a NULL
	terminator with encoding as specified in Section 2.1 of [RFC9256].		terminator with encoding as specified in Section 2.1 of [RFC9256].
	3. Color Extended Community		3. Color Extended Community
	The Color Extended Community [RFC9012] is used to steer traffic		The Color Extended Community [RFC9012] is used to steer traffic
	corresponding to BGP routes into an SR Policy with matching Color		corresponding to BGP routes into an SR Policy with matching Color
	value. The Color Extended Community MAY be carried in any BGP UPDATE		value. The Color Extended Community MAY be carried in any BGP UPDATE
	message whose AFI/SAFI is 1/1 (IPv4 Unicast), 2/1 (IPv6 Unicast), 1/4		message whose AFI/SAFI is 1/1 (IPv4 Unicast), 2/1 (IPv6 Unicast), 1/4
	(IPv4 Labeled Unicast), 2/4 (IPv6 Labeled Unicast), 1/128 (VPN-IPv4		(IPv4 Labeled Unicast), 2/4 (IPv6 Labeled Unicast), 1/128 (VPN-IPv4
	Labeled Unicast), 2/128 (VPN-IPv6 Labeled Unicast), or 25/70		Labeled Unicast), 2/128 (VPN-IPv6 Labeled Unicast), or 25/70
	skipping to change at line 1480 ¶		skipping to change at line 1480 ¶
	| 13 | Binding SID sub-TLV | RFC 9830 | IETF |		| 13 | Binding SID sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 14 | ENLP sub-TLV | RFC 9830 | IETF |		| 14 | ENLP sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 15 | Priority sub-TLV | RFC 9830 | IETF |		| 15 | Priority sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 20 | SRv6 Binding SID sub-TLV | RFC 9830 | IETF |		| 20 | SRv6 Binding SID sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 128 | Segment List sub-TLV | RFC 9830 | IETF |		| 128 | Segment List sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 129 | Policy Candidate Path | RFC 9830 | IETF |		| 129 | SR Policy Candidate Path | RFC 9830 | IETF |
	| | Name sub-TLV | | |		| | Name sub-TLV | | |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	| 130 | Policy Name sub-TLV | RFC 9830 | IETF |		| 130 | SR Policy Name sub-TLV | RFC 9830 | IETF |
	+-------+--------------------------+-----------+-------------------+		+-------+--------------------------+-----------+-------------------+
	Table 3: BGP Tunnel Encapsulation Attribute Sub-TLV Code Points		Table 3: BGP Tunnel Encapsulation Attribute Sub-TLV Code Points
	6.4. Color Extended Community Flags		6.4. Color Extended Community Flags
	This document defines the use of 2 bits in the "Color Extended		This document defines the use of 2 bits in the "Color Extended
	Community Flags" registry under the "Border Gateway Protocol (BGP)		Community Flags" registry under the "Border Gateway Protocol (BGP)
	Tunnel Encapsulation" registry group.		Tunnel Encapsulation" registry group.
End of changes. 29 change blocks.
	49 lines changed or deleted		49 lines changed or added
This html diff was produced by rfcdiff 1.48.