rfc9488v2.txt		rfc9488.txt
	skipping to change at line 58 ¶		skipping to change at line 58 ¶
	in the Revised BSD License.		in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction
	2. Requirements Language		2. Requirements Language
	3. Terminology		3. Terminology
	4. Motivation		4. Motivation
	4.1. Implementation Differences		4.1. Implementation Differences
	4.2. SLA Enforcement		4.2. SLA Enforcement
	5. Protection Enforcement Flag (E flag)		5. Protection Enforcement Flag (E Flag)
	5.1. Backwards Compatibility		5.1. Backwards Compatibility
	6. Security Considerations		6. Security Considerations
	7. IANA Considerations		7. IANA Considerations
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	8.2. Informative References		8.2. Informative References
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	skipping to change at line 124 ¶		skipping to change at line 124 ¶
	3. Terminology		3. Terminology
	This document uses the following terminology:		This document uses the following terminology:
	PROTECTION MANDATORY: The path MUST have protection eligibility on		PROTECTION MANDATORY: The path MUST have protection eligibility on
	all links.		all links.
	UNPROTECTED MANDATORY: The path MUST NOT have protection eligibility		UNPROTECTED MANDATORY: The path MUST NOT have protection eligibility
	on all links.		on all links.
	PROTECTION PREFERRED:		PROTECTION PREFERRED: The path should have protection eligibility on
	The path should have protection eligibility on all links but might		all links but might contain links that do not have protection
	contain links that do not have protection eligibility.		eligibility.
	UNPROTECTED PREFERRED:		UNPROTECTED PREFERRED: The path should not have protection
	The path should not have protection eligibility on all links but		eligibility on all links but might contain links that have
	might contain links that have protection eligibility.		protection eligibility.
	PCC:		PCC: Path Computation Client. Any client application requesting a
	Path Computation Client. Any client application requesting a path		path computation to be performed by a Path Computation Element.
	computation to be performed by a Path Computation Element.
	PCE:		PCE: Path Computation Element. An entity (component, application,
	Path Computation Element. An entity (component, application, or		or network node) that is capable of computing a network path or
	network node) that is capable of computing a network path or route		route based on a network graph and applying computational
	based on a network graph and applying computational constraints.		constraints.
	PCEP: Path Computation Element Communication Protocol		PCEP: Path Computation Element Communication Protocol
	LSPA: LSP Attributes object [RFC5440]		LSPA: LSP Attributes object [RFC5440]
	4. Motivation		4. Motivation
	4.1. Implementation Differences		4.1. Implementation Differences
	As defined in [RFC5440], the mechanism to signal protection		As defined in [RFC5440], the mechanism to signal protection
	skipping to change at line 214 ¶		skipping to change at line 213 ¶
	choose a protected or unprotected instruction associated with a		choose a protected or unprotected instruction associated with a
	resource, ensuring consistent PCE behavior across different		resource, ensuring consistent PCE behavior across different
	implementations.		implementations.
	When used with Segment Routing, an adjacency may have both a		When used with Segment Routing, an adjacency may have both a
	protected SID and an unprotected SID. If the UNPROTECTED PREFERRED		protected SID and an unprotected SID. If the UNPROTECTED PREFERRED
	option is selected, the PCE chooses the unprotected SID.		option is selected, the PCE chooses the unprotected SID.
	Alternatively, if the PROTECTED PREFERRED option is selected, the PCE		Alternatively, if the PROTECTED PREFERRED option is selected, the PCE
	chooses the protected SID.		chooses the protected SID.
	5. Protection Enforcement Flag (E flag)		5. Protection Enforcement Flag (E Flag)
	Section 7.11 of [RFC5440] describes the encoding of the Local		Section 7.11 of [RFC5440] describes the encoding of the Local
	Protection Desired (L) flag. The Protection Enforcement (E) flag,		Protection Desired (L) flag. The Protection Enforcement (E) flag,
	which extends the L flag, is specified below.		which extends the L flag, is specified below.
	+=====+==========================+===========+		+=====+==========================+===========+
	| Bit | Description | Reference |		| Bit | Description | Reference |
	+=====+==========================+===========+		+=====+==========================+===========+
	| 6 | Protection Enforcement | RFC 9488 |		| 6 | Protection Enforcement | RFC 9488 |
	+-----+--------------------------+-----------+		+-----+--------------------------+-----------+
	skipping to change at line 250 ¶		skipping to change at line 249 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Include-all |		| Include-all |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Setup Prio | Holding Prio | Flags |E|L| Reserved |		| Setup Prio | Holding Prio | Flags |E|L| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	// Optional TLVs //		// Optional TLVs //
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Flags (8 bits)		Flags (8 bits):
	L (Local Protection Desired): This flag is defined in [RFC5440]		L (Local Protection Desired): This flag is defined in [RFC5440]
	and further updated by this document. When set to 1,		and further updated by this document. When set to 1,
	protection is desired. When set to 0, protection is not		protection is desired. When set to 0, protection is not
	desired. The enforcement of the protection is identified via		desired. The enforcement of the protection is identified via
	the E flag.		the E flag.
	E (Protection Enforcement):		E (Protection Enforcement): This flag controls the strictness
	This flag controls the strictness with which the PCE must apply		with which the PCE must apply the L flag. When set to 1, the
	the L flag. When set to 1, the value of the L flag needs to be		value of the L flag needs to be respected during resource
	respected during resource selection by the PCE. When the E		selection by the PCE. When the E flag is set to 0, an attempt
	flag is set to 0, an attempt to respect the value of the L flag		to respect the value of the L flag is made; however, the PCE
	is made; however, the PCE could relax or ignore the L flag when		could relax or ignore the L flag when computing a path. The
	computing a path. The statements below indicate preference		statements below indicate preference when the E flag is set to
	when the E flag is set to 0 in combination with the L flag		0 in combination with the L flag value.
	value.
	When both the L flag and E flag are set to 1, then the PCE MUST		When both the L flag and E flag are set to 1, then the PCE MUST
	consider the protection eligibility as a PROTECTION MANDATORY		consider the protection eligibility as a PROTECTION MANDATORY
	constraint.		constraint.
	When the L flag is set to 1 and the E flag is set to 0, then the PCE		When the L flag is set to 1 and the E flag is set to 0, then the PCE
	MUST consider the protection eligibility as a PROTECTION PREFERRED		MUST consider the protection eligibility as a PROTECTION PREFERRED
	constraint.		constraint.
	When both the L flag and E flag are set to 0, then the PCE SHOULD		When both the L flag and E flag are set to 0, then the PCE SHOULD
End of changes. 8 change blocks.
	25 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.48.