< draft-li-pce-controlled-id-space-09.txt		draft-li-pce-controlled-id-space-10.txt >
	Network Working Group C. Li		Network Working Group C. Li
	Internet-Draft M. Chen		Internet-Draft M. Chen
	Intended status: Experimental Huawei Technologies		Intended status: Experimental Huawei Technologies
	Expires: February 24, 2022 A. Wang		Expires: August 29, 2022 A. Wang
	China Telecom		China Telecom
	W. Cheng		W. Cheng
	China Mobile		China Mobile
	C. Zhou		C. Zhou
	HPE		HPE
	August 23, 2021		February 25, 2022
	PCE Controlled ID Space		PCE Controlled ID Space
	draft-li-pce-controlled-id-space-09		draft-li-pce-controlled-id-space-10
	Abstract		Abstract
	The Path Computation Element Communication Protocol (PCEP) provides a		The Path Computation Element Communication Protocol (PCEP) provides a
	mechanisms for the Path Computation Elements (PCEs) to perform path		mechanisms for the Path Computation Elements (PCEs) to perform path
	computations in response to Path Computation Clients (PCCs) requests.		computations in response to Path Computation Clients (PCCs) requests.
	The Stateful PCE extensions allow stateful control of Multiprotocol		The Stateful PCE extensions allow stateful control of Multiprotocol
	Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths		Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
	(LSPs) using PCEP. Furthermore, PCE can be used for computing paths		(LSPs) using PCEP. Furthermore, PCE can be used for computing paths
	in the SR networks.		in the SR networks.
	skipping to change at page 2, line 15 ¶		skipping to change at page 2, line 15 ¶
	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 February 24, 2022.		This Internet-Draft will expire on August 29, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 14, line 15 ¶		skipping to change at page 14, line 15 ¶
	[RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An		[RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An
	Architecture for Use of PCE and the PCE Communication		Architecture for Use of PCE and the PCE Communication
	Protocol (PCEP) in a Network with Central Control",		Protocol (PCEP) in a Network with Central Control",
	RFC 8283, DOI 10.17487/RFC8283, December 2017,		RFC 8283, DOI 10.17487/RFC8283, December 2017,
	<https://www.rfc-editor.org/info/rfc8283>.		<https://www.rfc-editor.org/info/rfc8283>.
	[I-D.ietf-pce-segment-routing-ipv6]		[I-D.ietf-pce-segment-routing-ipv6]
	Li, C., Negi, M., Sivabalan, S., Koldychev, M.,		Li, C., Negi, M., Sivabalan, S., Koldychev, M.,
	Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment		Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment
	Routing leveraging the IPv6 data plane", draft-ietf-pce-		Routing leveraging the IPv6 data plane", draft-ietf-pce-
	segment-routing-ipv6-09 (work in progress), May 2021.		segment-routing-ipv6-11 (work in progress), January 2022.
	10.2. Informative References		10.2. Informative References
	[RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation		[RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation
	Element (PCE) Communication Protocol Generic		Element (PCE) Communication Protocol Generic
	Requirements", RFC 4657, DOI 10.17487/RFC4657, September		Requirements", RFC 4657, DOI 10.17487/RFC4657, September
	2006, <https://www.rfc-editor.org/info/rfc4657>.		2006, <https://www.rfc-editor.org/info/rfc4657>.
	[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,		[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
	"Recommendations for Secure Use of Transport Layer		"Recommendations for Secure Use of Transport Layer
	skipping to change at page 15, line 10 ¶		skipping to change at page 15, line 10 ¶
	Procedures and Extensions for Using the PCE as a Central		Procedures and Extensions for Using the PCE as a Central
	Controller (PCECC) of LSPs", RFC 9050,		Controller (PCECC) of LSPs", RFC 9050,
	DOI 10.17487/RFC9050, July 2021,		DOI 10.17487/RFC9050, July 2021,
	<https://www.rfc-editor.org/info/rfc9050>.		<https://www.rfc-editor.org/info/rfc9050>.
	[I-D.ietf-pce-pcep-extension-pce-controller-sr]		[I-D.ietf-pce-pcep-extension-pce-controller-sr]
	Li, Z., Peng, S., Negi, M. S., Zhao, Q., and C. Zhou,		Li, Z., Peng, S., Negi, M. S., Zhao, Q., and C. Zhou,
	"PCEP Procedures and Protocol Extensions for Using PCE as		"PCEP Procedures and Protocol Extensions for Using PCE as
	a Central Controller (PCECC) for Segment Routing (SR) MPLS		a Central Controller (PCECC) for Segment Routing (SR) MPLS
	Segment Identifier (SID) Allocation and Distribution.",		Segment Identifier (SID) Allocation and Distribution.",
	draft-ietf-pce-pcep-extension-pce-controller-sr-02 (work		draft-ietf-pce-pcep-extension-pce-controller-sr-03 (work
	in progress), March 2021.		in progress), September 2021.
	[I-D.ietf-pce-state-sync]		[I-D.ietf-pce-state-sync]
	Litkowski, S., Sivabalan, S., Li, C., and H. Zheng, "Inter		Litkowski, S., Sivabalan, S., Li, C., and H. Zheng, "Inter
	Stateful Path Computation Element (PCE) Communication		Stateful Path Computation Element (PCE) Communication
	Procedures.", draft-ietf-pce-state-sync-00 (work in		Procedures.", draft-ietf-pce-state-sync-01 (work in
	progress), June 2021.		progress), October 2021.
	[I-D.ietf-spring-segment-routing-policy]		[I-D.ietf-spring-segment-routing-policy]
	Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and		Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and
	P. Mattes, "Segment Routing Policy Architecture", draft-		P. Mattes, "Segment Routing Policy Architecture", draft-
	ietf-spring-segment-routing-policy-13 (work in progress),		ietf-spring-segment-routing-policy-18 (work in progress),
	May 2021.		February 2022.
	[I-D.dhody-pce-pcep-extension-pce-controller-srv6]		[I-D.dhody-pce-pcep-extension-pce-controller-srv6]
	Li, Z., Peng, S., Geng, X., and M. Negi, "PCEP Procedures		Li, Z., Peng, S., Geng, X., and M. Negi, "Path Computation
	and Protocol Extensions for Using PCE as a Central		Element Communication Protocol (PCEP) Procedures and
	Controller (PCECC) for SRv6", draft-dhody-pce-pcep-		Extensions for Using the PCE as a Central Controller
	extension-pce-controller-srv6-06 (work in progress),		(PCECC) for SRv6 SID Allocation and Distribution.", draft-
	February 2021.		dhody-pce-pcep-extension-pce-controller-srv6-07 (work in
			progress), August 2021.
	[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,		[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
	D., Matsushima, S., and Z. Li, "Segment Routing over IPv6		D., Matsushima, S., and Z. Li, "Segment Routing over IPv6
	(SRv6) Network Programming", RFC 8986,		(SRv6) Network Programming", RFC 8986,
	DOI 10.17487/RFC8986, February 2021,		DOI 10.17487/RFC8986, February 2021,
	<https://www.rfc-editor.org/info/rfc8986>.		<https://www.rfc-editor.org/info/rfc8986>.
	[I-D.ietf-pce-binding-label-sid]		[I-D.ietf-pce-binding-label-sid]
	Sivabalan, S., Filsfils, C., Tantsura, J., Previdi, S.,		Sivabalan, S., Filsfils, C., Tantsura, J., Previdi, S.,
	and C. L. (editor), "Carrying Binding Label/Segment		and C. L. (editor), "Carrying Binding Label/Segment
	Identifier in PCE-based Networks.", draft-ietf-pce-		Identifier (SID) in PCE-based Networks.", draft-ietf-pce-
	binding-label-sid-10 (work in progress), July 2021.		binding-label-sid-13 (work in progress), February 2022.
	Appendix A. Contributors		Appendix A. Contributors
	Dhruv Dhody		Dhruv Dhody
	Huawei Technologies		Huawei Technologies
	Divyashree Techno Park, Whitefield		Divyashree Techno Park, Whitefield
	Bangalore, Karnataka 560066		Bangalore, Karnataka 560066
	India		India
	EMail: dhruv.ietf@gmail.com		EMail: dhruv.ietf@gmail.com
End of changes. 11 change blocks.
	19 lines changed or deleted		20 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/