< draft-ietf-pce-binding-label-sid-06.txt		draft-ietf-pce-binding-label-sid-07.txt >
	PCE Working Group S. Sivabalan		PCE Working Group S. Sivabalan
	Internet-Draft Ciena Corporation		Internet-Draft Ciena Corporation
	Intended status: Standards Track C. Filsfils		Intended status: Standards Track C. Filsfils
	Expires: August 13, 2021 Cisco Systems, Inc.		Expires: August 24, 2021 Cisco Systems, Inc.
	J. Tantsura		J. Tantsura
	Apstra, Inc.		Apstra, Inc.
	S. Previdi		S. Previdi
	C. Li		C. Li
	Huawei Technologies		Huawei Technologies
	February 9, 2021		February 20, 2021
	Carrying Binding Label/Segment-ID in PCE-based Networks.		Carrying Binding Label/Segment-ID in PCE-based Networks.
	draft-ietf-pce-binding-label-sid-06		draft-ietf-pce-binding-label-sid-07
	Abstract		Abstract
	In order to provide greater scalability, network opacity, and service		In order to provide greater scalability, network opacity, and service
	independence, Segment Routing (SR) utilizes a Binding Segment		independence, Segment Routing (SR) utilizes a Binding Segment
	Identifier (BSID). It is possible to associate a BSID to RSVP-TE		Identifier (BSID). It is possible to associate a BSID to RSVP-TE
	signaled Traffic Engineering Label Switching Path or binding Segment-		signaled Traffic Engineering Label Switching Path or binding Segment-
	ID (SID) to SR Traffic Engineering path. Such a binding label/SID		ID (SID) to SR Traffic Engineering path. Such a binding label/SID
	can be used by an upstream node for steering traffic into the		can be used by an upstream node for steering traffic into the
	appropriate TE path to enforce SR policies. This document proposes		appropriate TE path to enforce SR policies. This document proposes
	skipping to change at page 2, line 7 ¶		skipping to change at page 2, line 7 ¶
	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 August 13, 2021.		This Internet-Draft will expire on August 24, 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 39 ¶		skipping to change at page 2, line 39 ¶
	3.1. SRv6 Endpoint Behavior and SID Structure . . . . . . . . 7		3.1. SRv6 Endpoint Behavior and SID Structure . . . . . . . . 7
	4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	5. Binding SID in SR-ERO . . . . . . . . . . . . . . . . . . . . 10		5. Binding SID in SR-ERO . . . . . . . . . . . . . . . . . . . . 10
	6. Binding SID in SRv6-ERO . . . . . . . . . . . . . . . . . . . 10		6. Binding SID in SRv6-ERO . . . . . . . . . . . . . . . . . . . 10
	7. PCE Allocation of Binding SID . . . . . . . . . . . . . . . . 10		7. PCE Allocation of Binding SID . . . . . . . . . . . . . . . . 10
	8. Implementation Status . . . . . . . . . . . . . . . . . . . . 12		8. Implementation Status . . . . . . . . . . . . . . . . . . . . 12
	8.1. Huawei . . . . . . . . . . . . . . . . . . . . . . . . . 12		8.1. Huawei . . . . . . . . . . . . . . . . . . . . . . . . . 12
	8.2. Cisco . . . . . . . . . . . . . . . . . . . . . . . . . . 13		8.2. Cisco . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 13		9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	10. Manageability Considerations . . . . . . . . . . . . . . . . 13		10. Manageability Considerations . . . . . . . . . . . . . . . . 13
	10.1. Control of Function and Policy . . . . . . . . . . . . . 13		10.1. Control of Function and Policy . . . . . . . . . . . . . 14
	10.2. Information and Data Models . . . . . . . . . . . . . . 14		10.2. Information and Data Models . . . . . . . . . . . . . . 14
	10.3. Liveness Detection and Monitoring . . . . . . . . . . . 14		10.3. Liveness Detection and Monitoring . . . . . . . . . . . 14
	10.4. Verify Correct Operations . . . . . . . . . . . . . . . 14		10.4. Verify Correct Operations . . . . . . . . . . . . . . . 14
	10.5. Requirements On Other Protocols . . . . . . . . . . . . 14		10.5. Requirements On Other Protocols . . . . . . . . . . . . 14
	10.6. Impact On Network Operations . . . . . . . . . . . . . . 14		10.6. Impact On Network Operations . . . . . . . . . . . . . . 14
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	11.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 14		11.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 14
	11.1.1. TE-PATH-BINDING TLV . . . . . . . . . . . . . . . . 14		11.1.1. TE-PATH-BINDING TLV . . . . . . . . . . . . . . . . 15
	11.1.2. Binding SID Flags . . . . . . . . . . . . . . . . . 15
	11.2. LSP Object . . . . . . . . . . . . . . . . . . . . . . . 15		11.2. LSP Object . . . . . . . . . . . . . . . . . . . . . . . 15
	11.3. PCEP Error Type and Value . . . . . . . . . . . . . . . 15		11.3. PCEP Error Type and Value . . . . . . . . . . . . . . . 16
	12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 16		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
	13.1. Normative References . . . . . . . . . . . . . . . . . . 16		13.1. Normative References . . . . . . . . . . . . . . . . . . 16
	13.2. Informative References . . . . . . . . . . . . . . . . . 18		13.2. Informative References . . . . . . . . . . . . . . . . . 18
	Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 19		Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 19
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
	1. Introduction		1. Introduction
	A PCE can compute Traffic Engineering paths (TE paths) through a		A PCE can compute Traffic Engineering paths (TE paths) through a
	skipping to change at page 7, line 6 ¶		skipping to change at page 7, line 6 ¶
	o BT = 2: The binding value is an SRv6 SID with a format of a 16		o BT = 2: The binding value is an SRv6 SID with a format of a 16
	octet IPv6 address, representing the binding SID for SRv6. The		octet IPv6 address, representing the binding SID for SRv6. The
	Length MUST be set to 20.		Length MUST be set to 20.
	o BT = 3: The binding value is a 24 octet field, defined in		o BT = 3: The binding value is a 24 octet field, defined in
	Section 3.1, that contains the SRv6 SID as well as its Behavior		Section 3.1, that contains the SRv6 SID as well as its Behavior
	and Structure. The Length MUST be set to 28.		and Structure. The Length MUST be set to 28.
	Flags: 1 octet of flags. Following flags are defined in the new		Flags: 1 octet of flags. Following flags are defined in the new
	registry "SR Policy Binding SID Flags" as described in		registry "TE-PATH-BINDING TLV Flag field" as described in
	Section 11.1.2:		Section 11.1.1:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	| |I|S|		| |I|S|
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	where:		where:
	o S-Flag: This flag encodes the "Specified-BSID-only" behavior. It		o S-Flag: This flag encodes the "Specified-BSID-only" behavior. It
	is used as described in Section 6.2.3 of		is used as described in Section 6.2.3 of
	[I-D.ietf-spring-segment-routing-policy].		[I-D.ietf-spring-segment-routing-policy].
	o I-Flag: This flag encodes the "Drop Upon Invalid" behavior. It is		o I-Flag: This flag encodes the "Drop Upon Invalid" behavior. It is
	used as described in Section 8.2 of		used as described in Section 8.2 of
	[I-D.ietf-spring-segment-routing-policy].		[I-D.ietf-spring-segment-routing-policy].
			o Unassigned bits MUST be set to 0 while sending and ignored 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 to		Binding Value: A variable-length field, padded with trailing zeros to
	a 4-octet boundary. For the BT as 0, the 20 bits represent the MPLS		a 4-octet boundary. For the BT as 0, the 20 bits represent the MPLS
	label. For the BT as 1, the 32-bits represent the label stack entry		label. For the BT as 1, the 32-bits represent the label stack entry
	as per [RFC5462]. For the BT as 2, the 128-bits represent the SRv6		as per [RFC5462]. For the BT as 2, the 128-bits represent the SRv6
	SID. For the BT as 3, the Binding Value contains SRv6 Endpoint		SID. For the BT as 3, the Binding Value contains SRv6 Endpoint
	Behavior and SID Structure, defined in Section 3.1.		Behavior and SID Structure, defined in Section 3.1.
	3.1. SRv6 Endpoint Behavior and SID Structure		3.1. SRv6 Endpoint Behavior and SID Structure
	skipping to change at page 14, line 36 ¶		skipping to change at page 14, line 41 ¶
	10.6. Impact On Network Operations		10.6. Impact On Network Operations
	Mechanisms defined in [RFC5440], [RFC8231], and [RFC8664] also apply		Mechanisms defined in [RFC5440], [RFC8231], and [RFC8664] also apply
	to PCEP extensions defined in this document. Further, the mechanism		to PCEP extensions defined in this document. Further, the mechanism
	described in this document can help the operator to request control		described in this document can help the operator to request control
	of the LSPs at a particular PCE.		of the LSPs at a particular PCE.
	11. IANA Considerations		11. IANA Considerations
			IANA maintains the "Path Computation Element Protocol (PCEP) Numbers"
			registry. This document requests IANA actions to allocate code
			points for the protocol elements defined in this document.
	11.1. PCEP TLV Type Indicators		11.1. PCEP TLV Type Indicators
	This document defines a new PCEP TLV; IANA is requested to make the		This document defines a new PCEP TLV; IANA is requested to make the
	following allocations from the "PCEP TLV Type Indicators" sub-		following allocations from the "PCEP TLV Type Indicators" subregistry
	registry of the PCEP Numbers registry, as follows:		of the PCEP Numbers registry, as follows:
	Value Name Reference		Value Description Reference
	TBD1 TE-PATH-BINDING This document		TBD1 TE-PATH-BINDING This document
	11.1.1. TE-PATH-BINDING TLV		11.1.1. TE-PATH-BINDING TLV
	IANA is requested to create a sub-registry to manage the value of the		IANA is requested to create a new subregistry "TE-PATH-BINDING TLV BT
	Binding Type field in the TE-PATH-BINDING TLV.		field" to manage the value of the Binding Type field in the TE-PATH-
			BINDING TLV. Initial values for the subregistry are given below.
			New values are assigned by Standards Action [RFC8126].
	Value Description Reference		Value Description Reference
	0 MPLS Label This document		0 MPLS Label This document
	1 MPLS Label Stack This document		1 MPLS Label Stack This document
	Entry		Entry
	2 SRv6 SID This document		2 SRv6 SID This document
	3 SRv6 SID with This document		3 SRv6 SID with This document
	Behavior and		Behavior and
	Structure		Structure
	11.1.2. Binding SID Flags		IANA is requested to create a new subregistry "TE-PATH-BINDING TLV
			Flag field" to manage the Flag field in the TE-PATH-BINDING TLV. New
	IANA is requested to create a sub-registry to manage the value of the		values are to be assigned by Standards Action [RFC8126]. Each bit
	Binding SID Flags field in the TE-PATH-BINDING-TLV. New values are		should be tracked with the following qualities:
	to be assigned by Standards Action [RFC8126]. Each bit should be
	tracked with the following qualities:
	o Bit number (count from 0 as the most significant bit)		o Bit number (count from 0 as the most significant bit)
	o Flag Name		o Description
	o Reference		o Reference
	Bit Description Reference		Bit Description Reference
	7 Specified-BSID-Only This document		7 Specified-BSID-Only This document
	Flag (S-Flag)		Flag (S-Flag)
	6 Drop Upon Invalid This document		6 Drop Upon Invalid This document
	Flag (I-Flag)		Flag (I-Flag)
	skipping to change at page 16, line 5 ¶		skipping to change at page 16, line 12 ¶
	TBD6 PCE-allocated binding This document		TBD6 PCE-allocated binding This document
	label/SID		label/SID
	11.3. PCEP Error Type and Value		11.3. PCEP Error Type and Value
	This document defines a new Error-type and Error-Values for the PCErr		This document defines a new Error-type and Error-Values for the PCErr
	message. IANA is requested to allocate new error-type and error-		message. IANA is requested to allocate new error-type and error-
	values within the "PCEP-ERROR Object Error Types and Values"		values within the "PCEP-ERROR Object Error Types and Values"
	subregistry of the PCEP Numbers registry, as follows:		subregistry of the PCEP Numbers registry, as follows:
	Error-Type Meaning		Error-Type Meaning Error-value Reference
	---------- -------
	TBD2 Binding label/SID failure:
	Error-value = TBD3: Invalid SID		TBD2 Binding label/SID This
	Error-value = TBD4: Unable to allocate		failure document
	the specified		TBD3: Invalid SID This
	label/SID		document
	Error-value = TBD5: Unable to allocate		TBD4: Unable to allocate the This
	label/SID		specified label/SID document
			TBD5: Unable to allocate This
			label/SID document
	12. Acknowledgements		12. Acknowledgements
	We like to thank Milos Fabian, Mrinmoy Das, and Andrew Stone for		We like to thank Milos Fabian, Mrinmoy Das, and Andrew Stone for
	their valuable comments.		their valuable comments.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
End of changes. 17 change blocks.
	31 lines changed or deleted		37 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/