Diff: rfc9604v2.txt - rfc9604.txt

	rfc9604v2.txt	rfc9604.txt

	Internet Engineering Task Force (IETF) S. Sivabalan	Internet Engineering Task Force (IETF) S. Sivabalan
	Request for Comments: 9604 Ciena Corporation	Request for Comments: 9604 Ciena Corporation
	Category: Standards Track C. Filsfils	Category: Standards Track C. Filsfils
	ISSN: 2070-1721 Cisco Systems, Inc.	ISSN: 2070-1721 Cisco Systems, Inc.
	J. Tantsura	J. Tantsura
	Nvidia	Nvidia
	S. Previdi	S. Previdi

		C. Li, Ed.
	Huawei Technologies	Huawei Technologies

	李呈 (C. Li), Ed.
	华为技术有限公司 (Huawei Technologies)
	August 2024	August 2024

	Carrying Binding Label/SID in PCE-Based Networks	Carrying Binding Label/SID in PCE-Based Networks

	Abstract	Abstract

	In order to provide greater scalability, network confidentiality, and	In order to provide greater scalability, network confidentiality, and
	service independence, Segment Routing (SR) utilizes a Binding Segment	service independence, Segment Routing (SR) utilizes a Binding Segment
	Identifier (BSID), as described in RFC 8402. It is possible to	Identifier (BSID), as described in RFC 8402. It is possible to
	associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE)	associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE)

	skipping to change at line 237 ¶	skipping to change at line 236 ¶

	binding value: a generic term used for the binding segment as it can	binding value: a generic term used for the binding segment as it can
	be encoded in various formats (as per the Binding Type (BT))	be encoded in various formats (as per the Binding Type (BT))

	LSP: Label Switched Path	LSP: Label Switched Path

	PCC: Path Computation Client	PCC: Path Computation Client

	PCEP: Path Computation Element Communication Protocol	PCEP: Path Computation Element Communication Protocol


	RSVP-TE: Resource ReserVation Protocol Traffic Engineering	RSVP-TE: Resource Reservation Protocol - Traffic Engineering

	SID: Segment Identifier	SID: Segment Identifier

	SR: Segment Routing	SR: Segment Routing

	4. Path Binding TLV	4. Path Binding TLV

	The new optional TLV called "TE-PATH-BINDING TLV" (the format is	The new optional TLV called "TE-PATH-BINDING TLV" (the format is
	shown in Figure 2) is defined to carry the binding label/SID for a TE	shown in Figure 2) is defined to carry the binding label/SID for a TE
	path. This TLV is associated with the LSP object specified in	path. This TLV is associated with the LSP object specified in

	skipping to change at line 325 ¶	skipping to change at line 324 ¶
	requires the removal of the binding value for the LSP. When	requires the removal of the binding value for the LSP. When
	unset, the PCEP peer indicates that the binding value is added	unset, the PCEP peer indicates that the binding value is added
	or retained for the LSP. This flag is used in the PCRpt and	or retained for the LSP. This flag is used in the PCRpt and
	PCUpd messages. It is ignored in other PCEP messages.	PCUpd messages. It is ignored in other PCEP messages.

	- The unassigned flags MUST be set to 0 while sending and ignored	- The unassigned flags MUST be set to 0 while sending and ignored
	on receipt.	on receipt.

	* Reserved: MUST be set to 0 while sending and ignored on receipt.	* Reserved: MUST be set to 0 while sending and ignored on receipt.


	* Binding value: A variable-length field, padded with trailing zeros	* Binding Value: A variable-length field, padded with trailing zeros
	to a 4-octet boundary. When the BT is 0, the 20 bits represent	to a 4-octet boundary. When the BT is 0, the 20 bits represent
	the MPLS label. When the BT is 1, the 32 bits represent the MPLS	the MPLS label. When the BT is 1, the 32 bits represent the MPLS
	label stack entry as per [RFC3032]. When the BT is 2, the 128	label stack entry as per [RFC3032]. When the BT is 2, the 128
	bits represent the SRv6 SID. When the BT is 3, the binding value	bits represent the SRv6 SID. When the BT is 3, the binding value
	also contains the SRv6 Endpoint Behavior and SID Structure,	also contains the SRv6 Endpoint Behavior and SID Structure,
	defined in Section 4.1. In this document, the TE-PATH-BINDING TLV	defined in Section 4.1. In this document, the TE-PATH-BINDING TLV
	is considered to be empty if no binding value is present. Note	is considered to be empty if no binding value is present. Note
	that the length of the TLV would be 4 in such a case.	that the length of the TLV would be 4 in such a case.

	4.1. SRv6 Endpoint Behavior and SID Structure	4.1. SRv6 Endpoint Behavior and SID Structure

	skipping to change at line 366 ¶	skipping to change at line 365 ¶
	The Binding Value consists of:	The Binding Value consists of:

	* SRv6 Binding SID: 16 octets. The 128-bit IPv6 address,	* SRv6 Binding SID: 16 octets. The 128-bit IPv6 address,
	representing the binding SID for SRv6.	representing the binding SID for SRv6.

	* Reserved: 2 octets. It MUST be set to 0 on transmit and ignored	* Reserved: 2 octets. It MUST be set to 0 on transmit and ignored
	on receipt.	on receipt.

	* Endpoint Behavior: 2 octets. The Endpoint Behavior code point for	* Endpoint Behavior: 2 octets. The Endpoint Behavior code point for
	this SRv6 SID as defined by the "SRv6 Endpoint Behaviors" registry	this SRv6 SID as defined by the "SRv6 Endpoint Behaviors" registry

	[RFC8986]. When the field is set with the value 0, the endpoint	[RFC8986]. When the field is set with the value 0, the Endpoint
	behavior is considered unknown.	Behavior is considered unknown.

	* [RFC8986] defines an SRv6 SID as consisting of LOC:FUNCT:ARG,	* [RFC8986] defines an SRv6 SID as consisting of LOC:FUNCT:ARG,
	where a locator (LOC) is encoded in the L most significant bits of	where a locator (LOC) is encoded in the L most significant bits of
	the SID, followed by F bits of function (FUNCT) and A bits of	the SID, followed by F bits of function (FUNCT) and A bits of
	arguments (ARG). A locator may be represented as B:N, where B is	arguments (ARG). A locator may be represented as B:N, where B is
	the SRv6 SID locator block (IPv6 prefix allocated for SRv6 SIDs by	the SRv6 SID locator block (IPv6 prefix allocated for SRv6 SIDs by
	the operator) and N is the identifier of the parent node	the operator) and N is the identifier of the parent node
	instantiating the SID, called "locator node". The following	instantiating the SID, called "locator node". The following
	fields are used to advertise the length of each individual part of	fields are used to advertise the length of each individual part of
	the SRv6 SID:	the SRv6 SID:

	skipping to change at line 1037 ¶	skipping to change at line 1036 ¶
	Huawei Technologies	Huawei Technologies
	Email: stefano@previdi.net	Email: stefano@previdi.net

	Cheng Li (editor)	Cheng Li (editor)
	Huawei Technologies	Huawei Technologies
	Huawei Campus, No. 156 Beiqing Rd.	Huawei Campus, No. 156 Beiqing Rd.
	Beijing	Beijing
	100095	100095
	China	China
	Email: c.l@huawei.com	Email: c.l@huawei.com


	Additional contact information:

	李呈 (editor)
	中国
	100095
	北京
	华为北研所
	华为技术有限公司

End of changes. 6 change blocks.
	6 lines changed or deleted	5 lines changed or added
This html diff was produced by rfcdiff 1.48.