rfc9863xml2.original.xml   rfc9863.xml 
<?xml version="1.0"?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!-- One method to get references from the online citation libraries. <!ENTITY nbsp "&#160;">
There has to be one entity for each item to be referenced. <!ENTITY zwsp "&#8203;">
An alternate method (rfc include) is described in the references. --> <!ENTITY nbhy "&#8209;">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC <!ENTITY wj "&#8288;">
.2119.xml">
<!ENTITY RFC3063 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3063.xml">
<!ENTITY RFC3209 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3209.xml">
<!ENTITY RFC3630 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3630.xml">
<!ENTITY RFC5305 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5305.xml">
<!ENTITY RFC5329 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5329.xml">
<!ENTITY RFC5440 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5440.xml">
<!ENTITY RFC5886 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5886.xml">
<!ENTITY RFC6123 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.6123.xml">
<!ENTITY RFC7308 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.7308.xml">
<!ENTITY RFC7942 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.7942.xml">
<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8174.xml">
<!ENTITY RFC8231 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8231.xml">
<!ENTITY RFC8253 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8253.xml">
<!ENTITY RFC8281 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8281.xml">
<!ENTITY RFC8408 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8408.xml">
<!ENTITY RFC8664 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8664.xml">
<!ENTITY RFC8745 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8745.xml">
<!ENTITY RFC9012 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.9012.xml">
<!ENTITY RFC9256 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.9256.xml">
<!ENTITY RFC9325 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.9325.xml">
]> ]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ie
<?rfc tocdepth="3"?> tf-pce-pcep-color-12" number="9863" updates="" obsoletes="" ipr="trust200902" su
<?rfc tocindent="yes"?> bmissionType="IETF" consensus="true" tocInclude="true" tocDepth="3" symRefs="tru
<?rfc symrefs="yes"?> e" sortRefs="true" version="3" xml:lang="en">
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-pce-pcep-color-12" ipr="trust200902" sub
missionType="IETF" consensus="true">
<front> <front>
<title abbrev="PCEP Color">Path Computation Element Protocol (PCEP) Extensio n for Color</title> <title abbrev="PCEP Color">Path Computation Element Protocol (PCEP) Extensio n for Color</title>
<seriesInfo name="RFC" value="9863"/>
<author initials="B." surname="Rajagopalan" fullname="Balaji Rajagopalan"> <author initials="B." surname="Rajagopalan" fullname="Balaji Rajagopalan">
<organization>Juniper Networks</organization> <organization>Juniper Networks</organization>
<address> <address>
<email>balajir@juniper.net</email> <email>balajir@juniper.net</email>
</address> </address>
</author> </author>
<author initials="V." surname="Beeram" fullname="Vishnu Pavan Beeram"> <author initials="V." surname="Beeram" fullname="Vishnu Pavan Beeram">
<organization>Juniper Networks</organization> <organization>Juniper Networks</organization>
<address> <address>
<email>vbeeram@juniper.net</email> <email>vbeeram@juniper.net</email>
</address> </address>
</author> </author>
<author initials="S." surname="Peng" fullname="Shaofu Peng"> <author initials="S." surname="Peng" fullname="Shaofu Peng">
<organization>ZTE Corporation</organization> <organization>ZTE Corporation</organization>
<address> <address>
<email>peng.shaofu@zte.com.cn</email> <email>peng.shaofu@zte.com.cn</email>
</address> </address>
</author> </author>
<author fullname="Mike Koldychev" initials="M." surname="Koldychev"> <author fullname="Mike Koldychev" initials="M." surname="Koldychev">
<organization>Ciena Corporation</organization> <organization>Ciena Corporation</organization>
<address> <address>
<email>mkoldych@proton.me</email> <email>mkoldych@proton.me</email>
</address> </address>
</author> </author>
<author fullname="Gyan Mishra" initials="G." surname="Mishra"> <author fullname="Gyan Mishra" initials="G." surname="Mishra">
<organization>Verizon Communications Inc.</organization> <organization>Verizon Communications Inc.</organization>
<address> <address>
<email>gyan.s.mishra@verizon.com</email> <email>gyan.s.mishra@verizon.com</email>
</address> </address>
</author> </author>
<date month="September" year="2025"/>
<date year="2025"/> <area>RTG</area>
<workgroup>pce</workgroup>
<area>Routing</area>
<workgroup>PCE Working Group</workgroup>
<keyword>color</keyword> <keyword>color</keyword>
<abstract> <abstract>
<t> <t>
Color is a 32-bit numerical (unsigned integer) attribute used to Color is a 32-bit numerical (unsigned integer) attribute used to
associate a Traffic Engineering (TE) tunnel or policy with an intent associate a Traffic Engineering (TE) tunnel or policy with an intent
or objective. For example, a TE Tunnel constructed to deliver low or objective. For example, a TE Tunnel constructed to deliver low
latency services and whose path is optimized for delay can be tagged latency services and whose path is optimized for delay can be tagged
with a color that represents "low latency." This document specifies with a color that represents "low latency." This document specifies
skipping to change at line 95 skipping to change at line 63
<t> <t>
Color is a 32-bit numerical (unsigned integer) attribute used to Color is a 32-bit numerical (unsigned integer) attribute used to
associate a Traffic Engineering (TE) tunnel or policy with an intent associate a Traffic Engineering (TE) tunnel or policy with an intent
or objective. For example, a TE Tunnel constructed to deliver low or objective. For example, a TE Tunnel constructed to deliver low
latency services and whose path is optimized for delay can be tagged latency services and whose path is optimized for delay can be tagged
with a color that represents "low latency." This document specifies with a color that represents "low latency." This document specifies
extensions to the Path Computation Element Protocol (PCEP) to carry extensions to the Path Computation Element Protocol (PCEP) to carry
the color attribute. the color attribute.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction" anchor='intro'> <section anchor="intro">
<name>Introduction</name>
<t> <t>
A Traffic Engineering (TE) tunnel (<xref target="RFC3209"/>) or Segment Ro A Traffic Engineering (TE) Tunnel <xref target="RFC3209"/> or Segment Rout
uting ing
(SR) policy (<xref target="RFC9256"/>) can be associated (SR) policy <xref target="RFC9256"/> can be associated
with an intent or objective (e.g., low latency) by tagging it with a color . This with an intent or objective (e.g., low latency) by tagging it with a color . This
color attribute is used as a guiding criterion for mapping services onto t he TE color attribute is used as a guiding criterion for mapping services onto t he TE
tunnel (<xref target="RFC9012"/>) or SR policy (<xref target="RFC9256"/>). Tunnel <xref target="RFC9012"/> or SR Policy <xref target="RFC9256"/>.
The term color used in this document must not be interpreted as the 'threa The term "color" used in this document must not be interpreted as the "thr
d color' ead color"
specified in <xref target="RFC3063"/> or the 'resource color' (also referr specified in <xref target="RFC3063"/> or the "resource color" (also referr
ed to as 'link color') ed to as "link color")
specified in <xref target="RFC3630"/>, <xref target="RFC5329"/>, specified in <xref target="RFC3630"/>, <xref target="RFC5329"/>,
<xref target ="RFC5305"/> and <xref target="RFC7308"/>. <xref target="RFC5305"/>, and <xref target="RFC7308"/>.
</t> </t>
<t> <t>
<xref target="RFC8231"/> specifies extensions to the Path Computation Elem ent <xref target="RFC8231"/> specifies extensions to the Path Computation Elem ent
Protocol (PCEP) that enable the deployment of a stateful Path Computation Element Protocol (PCEP) that enable the deployment of a stateful Path Computation Element
(PCE) model. These extensions allow a Path Computation Client (PCC) to del egate (PCE) model. These extensions allow a Path Computation Client (PCC) to del egate
control of the Label Switched Paths (LSPs) associated with its TE Tunnels to a control of the Label Switched Paths (LSPs) associated with its TE Tunnels to a
stateful PCE. <xref target="RFC8281"/> specifies extensions that allow a P CE to stateful PCE. <xref target="RFC8281"/> specifies extensions that allow a P CE to
instantiate and manage PCE-initiated LSPs on a PCC under the stateful PCE model. instantiate and manage PCE-initiated LSPs on a PCC under the stateful PCE model.
<xref target="RFC8664"/> specifies extensions that enable stateful control of SR <xref target="RFC8664"/> specifies extensions that enable stateful control of SR
paths via PCEP. paths via PCEP.
</t> </t>
skipping to change at line 122 skipping to change at line 88
<t> <t>
<xref target="RFC8231"/> specifies extensions to the Path Computation Elem ent <xref target="RFC8231"/> specifies extensions to the Path Computation Elem ent
Protocol (PCEP) that enable the deployment of a stateful Path Computation Element Protocol (PCEP) that enable the deployment of a stateful Path Computation Element
(PCE) model. These extensions allow a Path Computation Client (PCC) to del egate (PCE) model. These extensions allow a Path Computation Client (PCC) to del egate
control of the Label Switched Paths (LSPs) associated with its TE Tunnels to a control of the Label Switched Paths (LSPs) associated with its TE Tunnels to a
stateful PCE. <xref target="RFC8281"/> specifies extensions that allow a P CE to stateful PCE. <xref target="RFC8281"/> specifies extensions that allow a P CE to
instantiate and manage PCE-initiated LSPs on a PCC under the stateful PCE model. instantiate and manage PCE-initiated LSPs on a PCC under the stateful PCE model.
<xref target="RFC8664"/> specifies extensions that enable stateful control of SR <xref target="RFC8664"/> specifies extensions that enable stateful control of SR
paths via PCEP. paths via PCEP.
</t> </t>
<t> <t>
This document introduces extensions to PCEP to allow a color tag This document introduces extensions to PCEP to allow a color tag
to be assigned to any TE path operated under a stateful PCE model to be assigned to any TE path operated under a stateful PCE model
(including those set up using RSVP-TE <xref target="RFC8408"/> or (including those set up using RSVP-TE <xref target="RFC8408"/> or
Segment Routing <xref target ="RFC8664"/>). Segment Routing <xref target="RFC8664"/>).
The only exception where the extensions defined in The only exception where the extensions defined in
this document MUST NOT be used to carry the color attribute is for SR path this document <bcp14>MUST NOT</bcp14> be used to carry the color attribute
s is for SR paths
established using the extensions defined in <xref target="I-D.ietf-pce-seg established using the extensions defined in <xref target="RFC9862"/>.
ment-routing-policy-cp"/>.
For these SR paths, the associated color is already included as part of th e SR For these SR paths, the associated color is already included as part of th e SR
policy identifier encoding. Policy identifier encoding.
</t> </t>
<t> <t>
The mechanism employed by the PCC for mapping services onto a TE path The mechanism employed by the PCC for mapping services onto a TE path
associated with a color attribute is outside the scope of this document, a s associated with a color attribute is outside the scope of this document, a s
is any other use of the color tag. is any other use of the color tag.
</t> </t>
<section>
<section title="Requirements Language"> <name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPT The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
IONAL" in this IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
document are to be interpreted as described in BCP 14 <xref target="RFC21 NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
19"/> <xref target="RFC8174"/> RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
when, and only when, they appear in all capitals, as shown here. "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
</t> be interpreted as
</section> described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
when, and only when, they appear in all capitals, as shown here.
</t>
</section>
</section> </section>
<section>
<section title="Protocol Operation"> <name>Protocol Operation</name>
<t> <t>
When the PCEP session is created, a PCEP (PCE/PCC) speaker sends When the PCEP session is created, a PCEP (PCE/PCC) speaker sends
an Open message with an OPEN object that contains the an Open message with an OPEN object that contains the
STATEFUL-PCE-CAPABILITY TLV, as defined in <xref target="RFC8231"/>. A STATEFUL-PCE-CAPABILITY TLV, as defined in <xref target="RFC8231"/>. A
STATEFUL-PCE-CAPABILITY TLV Flag (See <xref target="Color-Cap"/>) STATEFUL-PCE-CAPABILITY TLV Flag (see <xref target="Color-Cap"/>)
is introduced in this document to enable the PCEP speaker to advertise c olor is introduced in this document to enable the PCEP speaker to advertise c olor
capability. capability.
</t> </t>
<t> <t>
In PCRpt, PCUpd, and PCInitiate messages, the LSP object (<xref target=" In PCRpt, PCUpd, and PCInitiate messages, the LSP object <xref target="R
RFC8231"/>, <xref target="RFC8281"/>) FC8231"/> <xref target="RFC8281"/>
is a mandatory inclusion and is used to carry information specific to th is a mandatory inclusion and is used to carry information specific to th
e target LSP. A TLV called the Color TLV e target LSP. A TLV called the COLOR TLV
(see <xref target="TLV-Format"/>), which MAY be carried in the LSP objec (see <xref target="TLV-Format"/>), which <bcp14>MAY</bcp14> be carried i
t, is n the LSP object, is
introduced in this document to carry the color attribute associated with the LSP. introduced in this document to carry the color attribute associated with the LSP.
Only one COLOR TLV SHOULD be included in the LSP object. If the COLOR T LV appears Only one COLOR TLV <bcp14>SHOULD</bcp14> be included in the LSP object. If the COLOR TLV appears
in the LSP object more than once, only the first occurrence is processed , and any in the LSP object more than once, only the first occurrence is processed , and any
others MUST be ignored. others <bcp14>MUST</bcp14> be ignored.
</t> </t>
<t> <t>
A PCEP speaker that has advertised color capability MUST NOT A PCEP speaker that has advertised color capability <bcp14>MUST NOT</bcp
send Color TLV encoded in the LSP object to a PCEP Peer that has not adv 14>
ertised color send COLOR TLV encoded in the LSP object to a PCEP Peer <xref target="RF
C5440"/> that has not advertised color
capability. A PCEP speaker that advertises both color capability and capability. A PCEP speaker that advertises both color capability and
SR Policy Association capability (<xref target="I-D.ietf-pce-segment-rou SR Policy Association <xref target="RFC9862"/> capability <bcp14>MUST
ting-policy-cp"/>) MUST NOT</bcp14> send COLOR TLV encoded in the LSP object for SR Paths.
NOT send Color TLV encoded in the LSP object for SR Paths. The COLOR TLV is ignored if it shows up in the LSP object of a message t
The Color TLV is ignored if it shows up in the LSP object of a message w hat
hich carries an ASSOCIATION object of type SR Policy Association <xref target
carries an ASSOCIATION object of type SR Policy Association (<xref targe ="RFC9862"/>.
t="I-D.ietf-pce-segment-routing-policy-cp"/>).
The color encoded in the SR Policy Association takes precedence in such a scenario. The color encoded in the SR Policy Association takes precedence in such a scenario.
</t> </t>
<t> <t>
If a PCC is unable to honor a color value passed in a PCUpd If a PCC is unable to honor a color value passed in a PCUpd
or a PCInitiate message, the PCC MUST reject the message or a PCInitiate message, the PCC <bcp14>MUST</bcp14> reject the message
and send a PCErr message with Error-type=19 (Invalid Operation) and send a PCErr message with Error-Type=19 (Invalid Operation)
and error-value=TBD1 (Invalid color). This is expected behavior and Error-value=31 (Invalid color). This is expected behavior
in scenarios where a PCC implementation does not support a color in scenarios where a PCC implementation does not support a color
value of zero for specific path setup types, and it receives that value of zero for specific path setup types, and it receives that
value in the COLOR TLV of a PCUpd or a PCInitiate message. value in the COLOR TLV of a PCUpd or a PCInitiate message.
</t> </t>
<t> <t>
When LSPs that belong to the same TE tunnel are within the When LSPs that belong to the same TE Tunnel are within the
same Path Protection Association Group <xref target="RFC8745"/>, same Path Protection Association Group <xref target="RFC8745"/>,
they are all expected to have the same color attached to them. they are all expected to have the same color attached to them.
If a PCEP speaker If a PCEP speaker
determines inconsistency in the color associated with the LSPs determines inconsistency in the color associated with the LSPs
belonging to the same Path Protection Association Group, it MUST belonging to the same Path Protection Association Group, it <bcp14>MUST< /bcp14>
reject the message carrying the inconsistent color and send a reject the message carrying the inconsistent color and send a
PCErr message with Error-type=19 (Invalid Operation) and PCErr message with Error-Type=19 (Invalid Operation) and
error-value=TBD2 (Inconsistent color). Error-value=32 (Inconsistent color).
</t> </t>
</section> </section>
<section anchor="Proto-Ext">
<section title="Protocol Extensions" anchor="Proto-Ext"> <name>Protocol Extensions</name>
<section title="Color Capability" anchor="Color-Cap"> <section anchor="Color-Cap">
<t> <name>Color Capability</name>
Section 7.1.1 of <xref target="RFC8231"/> defines <t>
<xref target="RFC8231" sectionFormat="of" section="7.1.1"/> defines
STATEFUL-PCE-CAPABILITY TLV flags. The following flag is used to STATEFUL-PCE-CAPABILITY TLV flags. The following flag is used to
indicate if the speaker supports color capability: indicate if the speaker supports color capability:
</t> </t>
<t>
<list> <dl spacing="normal" newline="false">
<t> <dt>C-bit (Bit 20):</dt><dd>A PCE/PCC indicates that it supports the
C-bit (Bit 20): A PCE/PCC indicates that it supports the color capability defined in this document by setting this bit.</dd>
color capability defined in this document by setting </dl>
this bit.
</t> </section>
</list> <section anchor="TLV-Format">
</t> <name>COLOR TLV</name>
</section> <figure anchor="color-tlv">
<section title="Color TLV" anchor="TLV-Format"> <name>COLOR TLV</name>
<figure anchor="color-tlv" title="Color TLV"> <artwork align="left"><![CDATA[
<artwork xml:space="preserve" align="left">
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length=4 | | Type | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Color | | Color |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</artwork> </figure>
</figure>
<t>
Type has the value 67. Length carries a value of 4.
The 'color' field is 4-bytes long, and carries the actual color value
(specified as an unsigned integer). A color value of zero is allowed.
</t>
</section>
</section>
<section title='Security Considerations' anchor='sec-con'> <dl spacing="normal" newline="false">
<dt>Type:</dt><dd>67</dd>
<dt>Length:</dt><dd>4</dd>
<dt>Color:</dt><dd>4-byte field that carries the actual color value
(specified as an unsigned integer). A value of zero is allowed.</dd>
</dl>
</section>
</section>
<section anchor="sec-con">
<name>Security Considerations</name>
<t> <t>
This document defines a TLV for color and a flag for This document defines a TLV for color and a flag for
color capability negotiation, which do not add any security color capability negotiation, which do not add any security
concerns beyond those discussed in <xref target='RFC5440'/>, concerns beyond those discussed in <xref target="RFC5440"/>,
<xref target='RFC8231'/> and <xref target='RFC8281'/>. <xref target="RFC8231"/>, and <xref target="RFC8281"/>.
</t> </t>
<t> <t>
An unauthorized PCE may maliciously associate the LSP with an An unauthorized PCE may maliciously associate the LSP with an
incorrect color. The procedures described in <xref incorrect color. The procedures described in <xref target="RFC8253"/> and
target='RFC8253'/> and <xref target='RFC9325'/> can be used to <xref target="RFC9325"/> can be used to
protect against this attack. protect against this attack.
</t> </t>
</section> </section>
<section anchor="mgmt-con">
<section title='Manageability Considerations' anchor='mgmt-con'> <name>Manageability Considerations</name>
<t> <t>
This section follows the advice and guidance of <xref target='RFC6123'/>. This section follows the advice and guidance of <xref target="RFC6123"/>.
</t> </t>
<section title='Control of Function through Configuration and Policy' anch <section anchor="mgmt-con-cfp">
or='mgmt-con-cfp'> <name>Control of Function through Configuration and Policy</name>
<t> <t>
An implementation supporting this document SHOULD allow the operator An implementation supporting this document <bcp14>SHOULD</bcp14> allow the
to turn on and off the PCEP color capability advertisement (<xref target=' operator
Color-Cap'/>). to turn on and off the PCEP color capability advertisement (<xref target="
An implementation supporting this document SHOULD allow the configuration Color-Cap"/>).
of color assignment to a TE Tunnel or an SR Policy. A PCC MAY have a An implementation supporting this document <bcp14>SHOULD</bcp14> allow the
configuration
of color assignment to a TE Tunnel or an SR Policy. A PCC <bcp14>MAY</bcp1
4> have a
local policy configuration that specifies how the color tag is used. local policy configuration that specifies how the color tag is used.
This policy configuration is outside the scope of this document. This policy configuration is outside the scope of this document.
</t> </t>
</section> </section>
<section title='Information and Data Models' anchor='mgmt-con-idm'> <section anchor="mgmt-con-idm">
<t> <name>Information and Data Models</name>
An implementation supporting this document SHOULD allow the inclusion of c <t>
olor An implementation supporting this document <bcp14>SHOULD</bcp14> allow the
in the data model used to retrieve the operational state of a TE tunnel or inclusion of color
an SR policy. in the data model used to retrieve the operational state of a TE Tunnel or
an SR Policy.
The YANG model in <xref target="I-D.ietf-teas-yang-te"/> could be used to retrieve the The YANG model in <xref target="I-D.ietf-teas-yang-te"/> could be used to retrieve the
operational state of a TE tunnel, and the YANG model in <xref target="I-D. operational state of a TE Tunnel, and the YANG model in <xref target="I-D.
ietf-spring-sr-policy-yang"/> ietf-spring-sr-policy-yang"/>
could be used to retrieve the operational state of an SR policy. could be used to retrieve the operational state of an SR Policy.
</t> </t>
</section> </section>
<section title='Liveness Detection and Monitoring' anchor='mgmt-con-ldm'> <section anchor="mgmt-con-ldm">
<t> <name>Liveness Detection and Monitoring</name>
<t>
The extensions defined in this document do not require any additional The extensions defined in this document do not require any additional
liveness detection and monitoring support. See <xref target='RFC5440'/> a liveness detection and monitoring support. See <xref target="RFC5440"/> a
nd nd
<xref target='RFC5886'/> for more information. <xref target="RFC5886"/> for more information.
</t> </t>
</section> </section>
<section title='Verifying Correct Operation' anchor='mgmt-con-vco'> <section anchor="mgmt-con-vco">
<t> <name>Verifying Correct Operation</name>
The operator MAY retrieve the operational state of TE Paths to verify if t <t>
hey are tagged with the correct intended color. The operator <bcp14>MAY</bcp14> retrieve the operational state of TE Paths
</t> to verify if they are tagged with the correct intended color.
</t>
</section> </section>
<section title='Requirements on Other Protocols' anchor='mgmt-con-prot'> <section anchor="mgmt-con-prot">
<t> <name>Requirements on Other Protocols</name>
<t>
This document places no explicit requirements on other protocols. This document places no explicit requirements on other protocols.
</t> </t>
</section> </section>
<section title='Impact on Network Operation' anchor='mgmt-con-ino'> <section anchor="mgmt-con-ino">
<t> <name>Impact on Network Operation</name>
<t>
The impact on network operations depends on how the color tag is used in t he deployment. This is outside the scope of this document. The impact on network operations depends on how the color tag is used in t he deployment. This is outside the scope of this document.
</t> </t>
</section> </section>
</section> </section>
<section anchor="IANA">
<section anchor="IANA" title="IANA Considerations"> <name>IANA Considerations</name>
<section title="PCEP TLV Type Indicator"> <section>
<t> <name>PCEP TLV Type Indicator</name>
This document introduces a value in the <t>
IANA has assigned a value in the
"PCEP TLV Type Indicators" registry of the "PCEP TLV Type Indicators" registry of the
"Path Computation Element Protocol (PCEP) Numbers" registry group as fo llows: "Path Computation Element Protocol (PCEP) Numbers" registry group as fo llows:
<figure> </t>
<artwork align="left"><![CDATA[
Value Description Reference <table>
---------------------------------------------- <thead><tr><th>Value</th><th>Description</th><th>Reference</th></tr></t
67 Color This document head>
]]></artwork> <tbody><tr><td>67</td><td>Color</td><td>RFC 9863</td></tr></tbody>
</figure> </table>
Note: The code point specified for the TLV Type Indicator
is an early allocation by IANA.
</t>
</section> </section>
<section title="STATEFUL-PCE-CAPABILITY TLV Flag Field"> <section>
<t> <name>STATEFUL-PCE-CAPABILITY TLV Flag Field</name>
This document introduces a bit value in the <t>
IANA has assigned a bit value in the
"STATEFUL-PCE-CAPABILITY TLV Flag Field" registry of the "STATEFUL-PCE-CAPABILITY TLV Flag Field" registry of the
"Path Computation Element Protocol (PCEP) Numbers" registry group as fo llows: "Path Computation Element Protocol (PCEP) Numbers" registry group as fo llows:
<figure> </t>
<artwork align="left"><![CDATA[ <table>
Value Description Reference <thead><tr><th>Value</th><th>Description</th><th>Reference</th></tr></t
---------------------------------------------- head>
20 COLOR-CAPABILITY This document <tbody><tr><td>20</td><td>COLOR-CAPABILITY</td><td>RFC 9863</td></tr></
]]></artwork> tbody>
</figure> </table>
Note: The code point specified for the STATEFUL-PCE-CAPABILITY
TLV Flag is an early allocation by IANA.
</t>
</section> </section>
<section title="PCEP-Error Object"> <section>
<t> <name>PCEP-Error Object</name>
This document introduces two Error-values for Error-Type=19 (Invalid Opera <t>
tion) IANA has assigned two Error-values for Error-Type=19 (Invalid Operation)
within the "PCEP-ERROR Object Error Types and Values" registry of the "Pat h within the "PCEP-ERROR Object Error Types and Values" registry of the "Pat h
Computation Element Protocol (PCEP) Numbers" registry group as follows: Computation Element Protocol (PCEP) Numbers" registry group as follows:
<figure> </t>
<artwork align="left"><![CDATA[
Error- Meaning Error-value Reference <table>
Type <thead>
------------------------------------------------------------------ <tr>
19 Invalid Operation TBD1: Invalid Color This document <th>Error-Type</th>
TBD2: Inconsistent Color This document <th>Meaning</th>
]]></artwork> <th>Error-value</th>
</figure> <th>Reference</th>
</t> </tr>
</thead>
<tbody>
<tr>
<td rowspan="2">19</td>
<td rowspan="2">Invalid Operation</td>
<td>31: Invalid Color</td>
<td>RFC 9863</td>
</tr>
<tr>
<td>32: Inconsistent Color</td>
<td>RFC 9863</td>
</tr>
</tbody>
</table>
</section> </section>
<section title="LSP-ERROR-CODE TLV Error Code Field"> <section>
<t> <name>LSP-ERROR-CODE TLV Error Code Field</name>
An earlier version of this document added an error code in the <t>
A draft version of this document added an error code in the
"LSP-ERROR-CODE TLV Error Code Field" registry of the "LSP-ERROR-CODE TLV Error Code Field" registry of the
"Path Computation Element Protocol (PCEP) Numbers" "Path Computation Element Protocol (PCEP) Numbers"
registry group, which was also early allocated by the IANA. registry group, which was also early allocated by the IANA.
</t> </t>
<t> <t>
IANA is requested to cancel the early allocation made which is not IANA has marked it as deprecated.
needed anymore. As per the instructions from the chairs, please mark </t>
it as deprecated. <table>
</t> <thead><tr><th>Value</th><th>Meaning</th><th>Reference</th></tr></thead
<t> >
<figure> <tbody>
<artwork align="left"><![CDATA[ <tr>
Value Meaning Reference <td>9</td>
------------------------------------------------------ <td>Deprecated (Unsupported Color)</td>
9 Deprecated (Unsupported Color) This document <td>RFC 9863</td>
]]></artwork> </tr>
</figure> </tbody>
</t> </table>
</section> </section>
</section> </section>
<section title="Implementation Status"> </middle>
<t>[Note to the RFC Editor - remove this section before publication, as <back>
well as remove the reference to RFC 7942.]</t>
<t>This section records the status of known implementations of the <displayreference target="I-D.ietf-spring-sr-policy-yang" to="SR-POLICY-YANG
protocol defined by this specification at the time of posting of this "/>
Internet-Draft, and is based on a proposal described in <xref target="RFC7942 <displayreference target="I-D.ietf-teas-yang-te" to="YANG-TE"/>
"/>. <references>
The description of implementations in this section is intended to <name>References</name>
assist the IETF in its decision processes in progressing drafts to <references>
RFCs. Please note that the listing of any individual implementation <name>Normative References</name>
here does not imply endorsement by the IETF. Furthermore, no effort <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
has been spent to verify the information presented here that was 119.xml"/>
supplied by IETF contributors. This is not intended as, and must not <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
be construed to be, a catalog of available implementations or their 174.xml"/>
features. Readers are advised to note that other implementations may <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
exist.</t> 440.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
231.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
253.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
281.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
408.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
664.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
745.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
012.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
325.xml"/>
<t>According to <xref target="RFC7942"/>, "this will allow reviewers and work <reference anchor="RFC9862" target="https://www.rfc-editor.org/info/rfc9
ing groups 862">
to assign due consideration to documents that have the benefit of <front>
running code, which may serve as evidence of valuable experimentation <title>Path Computation Element Communication Protocol (PCEP) Extens
and feedback that have made the implemented protocols more mature. ions for Segment Routing (SR) Policy Candidate Paths</title>
It is up to the individual working groups to use this information as <author initials="M." surname="Koldychev" fullname="Mike Koldychev">
they see fit".</t> <organization>Ciena Corporation</organization>
</author>
<author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
<organization>Ciena Corporation</organization>
</author>
<author initials="S." surname="Sidor" fullname="Samuel Sidor">
<organization>Cisco Systems, Inc.</organization>
</author>
<author initials="C." surname="Barth" fullname="Colby Barth">
<organization>Juniper Networks, Inc.</organization>
</author>
<author initials="S." surname="Peng" fullname="Shuping Peng">
<organization>Huawei Technologies</organization>
</author>
<author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
<organization>Nokia</organization>
</author>
<date month="September" year="2025"/>
</front>
<seriesInfo name="RFC" value="9862"/>
<seriesInfo name="DOI" value="10.17487/RFC9862"/>
</reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
063.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
209.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
630.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
305.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
329.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
886.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
123.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
308.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
256.xml"/>
<t> At the time of publication of this version, there are no known <!-- [I-D.ietf-teas-yang-te]
implementations. Juniper Networks has plans to implement the draft-ietf-teas-yang-te-38
extensions defined in this document.</t> IESG State: I-D Exists as of 07/15/25
</section> -->
<section title='Acknowledgments'> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.
<t> ietf-teas-yang-te.xml"/>
The authors would like to thank Kaliraj Vairavakkalai, Colby <!-- [I-D.ietf-spring-sr-policy-yang]
Barth, Natrajan Venkataraman, Tarek Saad, Dhruv Dhody, Adrian Farrel, draft-ietf-spring-sr-policy-yang-05
Andrew Stone, Diego Achaval, and Narasimha Kommuri for their review and IESG State: I-D Exists as of 07/15/25
suggestions. -->
</t> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.
ietf-spring-sr-policy-yang.xml"/>
</references>
</references>
<section numbered="false">
<name>Acknowledgments</name>
<t>The authors would like to thank <contact fullname="Kaliraj
Vairavakkalai"/>, <contact fullname="Colby Barth"/>, <contact
fullname="Natrajan Venkataraman"/>, <contact fullname="Tarek Saad"/>,
<contact fullname="Dhruv Dhody"/>, <contact fullname="Adrian Farrel"/>,
<contact fullname="Andrew Stone"/>, <contact fullname="Diego Achaval"/>,
and <contact fullname="Narasimha Kommuri"/> for their review and
suggestions.</t>
</section> </section>
<section title='Contributors'> <section numbered="false">
<t>The following people have contributed to this document:</t> <name>Contributors</name>
<author initials="Q." surname="Xiong" fullname="Quan Xiong"> <t>The following people have contributed to this document:</t>
<organization>ZTE Corporation</organization>
<address> <contact fullname="Quan Xiong">
<email>xiong.quan@zte.com.cn</email> <organization>ZTE Corporation</organization>
</address> <address>
</author> <email>xiong.quan@zte.com.cn</email>
</address>
</contact>
</section> </section>
</middle> </back>
<back>
<references title='Normative References'>
&RFC2119;
&RFC8174;
&RFC5440;
&RFC8231;
&RFC8253;
&RFC8281;
&RFC8408;
&RFC8664;
&RFC8745;
&RFC9012;
&RFC9325;
<?rfc include='reference.I-D.ietf-pce-segment-routing-policy-cp.xml'?>
</references>
<references title='Informative References'>
&RFC3063;
&RFC3209;
&RFC3630;
&RFC5305;
&RFC5329;
&RFC5886;
&RFC6123;
&RFC7308;
&RFC7942;
&RFC9256;
<?rfc include='reference.I-D.ietf-teas-yang-te.xml'?>
<?rfc include='reference.I-D.ietf-spring-sr-policy-yang.xml'?>
</references>
</back>
</rfc> </rfc>
 End of changes. 72 change blocks. 
336 lines changed or deleted 347 lines changed or added

This html diff was produced by rfcdiff 1.48.