rfc9504v3.txt		rfc9504.txt
	skipping to change at line 12 ¶		skipping to change at line 12 ¶
	Internet Engineering Task Force (IETF) Y. Lee		Internet Engineering Task Force (IETF) Y. Lee
	Request for Comments: 9504 Samsung		Request for Comments: 9504 Samsung
	Category: Standards Track H. Zheng		Category: Standards Track H. Zheng
	ISSN: 2070-1721 Huawei Technologies		ISSN: 2070-1721 Huawei Technologies
	O. Gonzalez de Dios		O. Gonzalez de Dios
	Telefonica		Telefonica
	V. Lopez		V. Lopez
	Nokia		Nokia
	Z. Ali		Z. Ali
	Cisco		Cisco
	November 2023		December 2023
	Path Computation Element Communication Protocol (PCEP) Extensions for		Path Computation Element Communication Protocol (PCEP) Extensions for
	Stateful PCE Usage in GMPLS-Controlled Networks		Stateful PCE Usage in GMPLS-Controlled Networks
	Abstract		Abstract
	The Path Computation Element Communication Protocol (PCEP) has been		The Path Computation Element Communication Protocol (PCEP) has been
	extended to support stateful PCE functions where the stateful PCE		extended to support stateful PCE functions where the stateful PCE
	maintains information about paths and resource usage within a		maintains information about paths and resource usage within a
	network; however, these extensions do not cover all requirements for		network; however, these extensions do not cover all requirements for
	skipping to change at line 371 ¶		skipping to change at line 371 ¶
	SWITCH-LAYER: The SWITCH-LAYER definition in Section 3.2 of		SWITCH-LAYER: The SWITCH-LAYER definition in Section 3.2 of
	[RFC8282] is applicable in stateful PCEP messages for GMPLS		[RFC8282] is applicable in stateful PCEP messages for GMPLS
	networks.		networks.
	6.2. New Extensions		6.2. New Extensions
	6.2.1. GMPLS-CAPABILITY TLV in OPEN Object		6.2.1. GMPLS-CAPABILITY TLV in OPEN Object
	In [RFC8779], IANA allocates value 45 (GMPLS-CAPABILITY) from the		In [RFC8779], IANA allocates value 45 (GMPLS-CAPABILITY) from the
	"PCEP TLV Type Indicators" subregistry. This specifcation adds three		"PCEP TLV Type Indicators" subregistry. This specification adds
	flags to the Flag field of this TLV to indicate the Report, Update,		three flags to the Flag field of this TLV to indicate the Report,
	and Initiation capabilities.		Update, and Initiation capabilities.
	R (LSP-REPORT-CAPABILITY (31) -- 1 bit):		R (LSP-REPORT-CAPABILITY (31) -- 1 bit):
	If set to 1 by a PCC, the R flag indicates that the PCC is capable		If set to 1 by a PCC, the R flag indicates that the PCC is capable
	of reporting the current state of a GMPLS LSP whenever there's a		of reporting the current state of a GMPLS LSP whenever there's a
	change to the parameters or operational status of the GMPLS LSP.		change to the parameters or operational status of the GMPLS LSP.
	If set to 1 by a PCE, the R flag indicates that the PCE is		If set to 1 by a PCE, the R flag indicates that the PCE is
	interested in receiving GMPLS LSP State Reports whenever there is		interested in receiving GMPLS LSP State Reports whenever there is
	a parameter or operational status change to the LSP. The LSP-		a parameter or operational status change to the LSP. The LSP-
	REPORT-CAPABILITY flag must be advertised by both a PCC and a PCE		REPORT-CAPABILITY flag must be advertised by both a PCC and a PCE
	for PCRpt messages to be allowed on a PCEP session for GMPLS LSP.		for PCRpt messages to be allowed on a PCEP session for GMPLS LSP.
End of changes. 2 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.