<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-dong-pce-cc-nrp-01" submissionType="IETF" category="std" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="true" consensus="true">

<front>
<title abbrev="PCECC for NRP">PCEP Extensions for PCE Central Controller (PCECC) based Network Resource Partition (NRP) Instantiation</title><seriesInfo value="draft-dong-pce-cc-nrp-01" stream="IETF" status="standard" name="Internet-Draft"></seriesInfo>
<author initials="J." surname="Dong" fullname="Jie Dong"><organization>Huawei Technologies</organization><address><postal><street></street>
<country>China</country>
</postal><email>jie.dong@huawei.com</email>
</address></author><author initials="P." surname="Yu" fullname="Pingping Yu"><organization>Huawei Technologies</organization><address><postal><street></street>
<country>China</country>
</postal><email>susana.yu@huawei.com</email>
</address></author><author initials="L." surname="Zhang" fullname="Li Zhang"><organization>Huawei Technologies</organization><address><postal><street></street>
<country>China</country>
</postal><email>zhangli344@huawei.com</email>
</address></author><date year="2026" month="November" day="13"></date>
<area>Routing</area>
<workgroup>PCE Working Group</workgroup>

<abstract>
<t>The PCE is a core component of Software-Defined Networking (SDN) systems. A
PCE-based Central Controller (PCECC) can simplify the processing of a
distributed control plane by blending it with elements of SDN without
necessarily completely replacing it.</t>
<t>Network Resource Partitions (NRPs) can be used to provide the required
connectivity and committed resources for network slice services. An NRP is a
subset of the buffer/queuing/scheduling resources and associated policies on
each of a connected set of links in the underlay network.</t>
<t>This document specifies the extensions to Path Computation Element
Communication Protocol (PCEP) to enable PCECC based Network Resource Partition
(NRP) Instantiation.</t>
</abstract>

</front>

<middle>

<section anchor="sec-intro"><name>Introduction</name>
<t><xref target="RFC5440"></xref> describes the Path Computation Element (PCE) Communication Protocol
(PCEP). PCEP enables the communication between a Path Computation Client (PCC)
and a PCE, or between PCE and PCE, for the purpose of computation of
Multi-protocol Label Switching (MPLS) as well as Generalized MPLS (GMPLS)
Traffic Engineering Label Switched Path (TE LSP) characteristics. <xref target="RFC8231"></xref>
specifies a set of extensions to PCEP to enable stateful control of TE LSPs
within and across PCEP sessions in compliance with <xref target="RFC4657"></xref>. It includes
mechanisms to effect LSP State Synchronization between PCCs and PCEs,
delegation of control over LSPs to PCEs, and PCE control of timing and
sequence of path computations within and across PCEP sessions. The model of
operation where LSPs are initiated from the PCE is described in <xref target="RFC8281"></xref>.</t>
<t><xref target="RFC8283"></xref> introduces the architecture for PCE as a central controller (PCECC)
as an extension of the architecture described in <xref target="RFC4655"></xref> and assumes the
continued use of PCEP as the protocol used between PCE and PCC. <xref target="RFC8283"></xref>
further examines the motivations and applicability for PCEP as a Southbound
Interface (SBI), and introduces the implications for the protocol. <xref target="RFC9689"></xref>
describes the use cases for the PCECC architecture.</t>
<t>With the introduction and evolvement of 5G and other network scenarios,
existing or emerging applications or customers may require connectivity
services with additional characteristics. As described in <xref target="RFC9543"></xref>, an IETF
Network Slice enables connectivity service between a set of Service
Demarcation Points (SDPs) with specific Service Level Objectives (SLOs) and
Service Level Expectations (SLEs) over a common underlay network. For the
realization of IETF network slice service, the concept Network Resource
Partition (NRP) is introduced in <xref target="RFC9543"></xref>. A Network Resource Partition (NRP)
is a subset of the buffer/queuing/scheduling resources and associated policies
on each of a connected set of links in the underlay network.</t>
<t>The NRPs and the set of network resources allocated to them can be instantiated
by a central controller. PCECC can be used for the instantiation of NRP in the
underlay network. This document specifies the extensions to Path Computation
Element Communication Protocol (PCEP) to enable PCECC based Network Resource
Partition (NRP) Instantiation.</t>

<section anchor="sec-req-lang"><name>Requirements Language</name>
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, &quot;SHOULD&quot;,
&quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
document are to be interpreted as described in BCP 14 <xref target="RFC2119"></xref> <xref target="RFC8174"></xref>
when, and only when, they appear in all capitals, as shown here.</t>
</section>
</section>

<section anchor="SEC_EXT"><name>PCEP Extensions for NRP Instantiation</name>

<section anchor="sec-pcecc-cap"><name>PCECC Capability Advertisement</name>
<t>During the PCEP initialization phase, PCEP speakers (PCE or PCC) advertise
their support of and willingness to use PCEP extensions for the PCECC. A PCEP
speaker includes the PCECC-CAPABILITY sub-TLV in the PATH-SETUP-TYPE-CAPABILITY
TLV as per <xref target="RFC9050"></xref>. To indicate whether a PCE or PCC supports PCECC based
resource reservation, a new bit (the R bit) in the PCECC-CAPABILITY sub-TLV is
defined.</t>

<ul spacing="compact">
<li>R bit (Resource reservation): If set to '1' by a PCEP speaker, the R flag
indicates that the PCEP speaker supports and is willing to handle the
PCECC-based resource reservation. The bit <bcp14>MUST</bcp14> be set to '1' by both a
PCC and a PCE for PCECC resource reservation and report on a PCEP session.</li>
</ul>
</section>

<section anchor="sec-fec"><name>FEC Object</name>
<t>The FEC Object as defined in
<xref target="I-D.ietf-pce-pcep-extension-pce-controller-sr"></xref> is used to specify the FEC
information of the PCECC instruction.
<xref target="I-D.ietf-pce-pcep-extension-pce-controller-sr"></xref> defines multiple FEC
Object-Types for the instantiation of SR SIDs. In the context of NRP
instantiation, the following FEC Object-Type can be used to identify the link
on which the NRP resource is instantiated.</t>
<figure anchor="SEC2_FIG1" align="center"><name>FEC Object-Types for NRP Instantiation </name>
<artwork align="center"><![CDATA[+-------------+----------------------------------+-----------------+
|     FEC     |           Description            |    Reference    |
| Object-Type |                                  |                 |
+-------------+----------------------------------+-----------------+
|      3      |IPv4 Adjacency                    |                 |
|      4      |IPv6 Global Adjacency             |I-D.ietf-pce-    |
|      5      |Unnumbered Adjacency with         |pcep-ext-        |
|             |IPv4 NodeID                       |pce-ctrl-sr      |
|      6      |IPv6 Linklocal Adjacency          |                 |
+-------------+----------------------------------+-----------------+
]]></artwork>
</figure>
</section>

<section anchor="sec-cci"><name>CCI Object</name>
<t>The Central Controller Instructions (CCI) object is used by the PCE to specify
the instructions to the PCC. A new CCI Object-Type for Resource Reservation is
defined, which <bcp14>MAY</bcp14> be carried within a PCInitiate or PCRpt message for NRP
instantiation and report respectively. The new CCI Object-type is TBA. The
format of this CCI Object-Type is as follows:</t>
<figure anchor="SEC2_FIG2" align="center"><name>CCI Object Type for Resource Reservation </name>
<artwork align="center"><![CDATA[ 0                   1                   2                   3
 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            CC-ID                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|            Flags              |           Reserved            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                          Optional TLVs                        ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>Where:</t>

<ul>
<li><t>CC-ID: A unique identifier for the CCI in PCEP as described in <xref target="RFC9050"></xref>.</t>
</li>
<li><t>Flags: 16-bit flags.  Currently all the flags are reserved for future use.  They MUST be set to zero on transmission and MUST be ignored on receipt.</t>
</li>
<li><t>Reserved: 16-bit reserved field for future use. All the bits <bcp14>MUST</bcp14> be set
to zero on transmission and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
<li><t>Optional TLVs: Used to carry resource reservation related instruction and
information.</t>
</li>
</ul>

<section anchor="sec-nrp-tlv"><name>NRP Instantiation TLV</name>
<t>A new TLV is defined to instruct to instantiate NRP on a specified link. The
format of the NRP Instantiation TLV is as follows:</t>
<figure anchor="SEC2_FIG3" align="center"><name>NRP Instantiation TLV </name>
<artwork align="center"><![CDATA[ 0                   1                   2                   3
 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 = TBD            |       Length (variable)       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|   NRP Type    |   Flags     |E|           Reserved            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             NRP ID                            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                        Optional sub-TLVs                      ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>Where:</t>

<ul>
<li><t>NRP Type: Type of the NRP instantiation. The following type is defined in
this document.</t>

<ul spacing="compact">
<li>Type 1: Queue based partition. In this case, the NRP is instantiated
using a dedicated queue.</li>
</ul></li>
<li><t>Flags: 8-bit flags field. The most significant bit is defined as the E
(Exclusive) bit. When the E bit is set, it indicates that dedicated resource
is allocated to the NRP. The rest of the bits <bcp14>MUST</bcp14> be set to zero on
transmission and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
<li><t>Reserved: 16-bit reserved field for future use. All the bits <bcp14>MUST</bcp14> be set
to zero on transmission and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
<li><t>NRP ID: A 32-bit NRP identifier globally unique within an NRP domain, as
defined in <xref target="I-D.ietf-teas-ns-ip-mpls"></xref>.</t>
</li>
<li><t>Optional sub-TLVs: Used to carry resource information of the NRP.</t>
</li>
</ul>
<t>One or multiple NRP Instantiation TLVs <bcp14>MAY</bcp14> be carried in the CCI Object
with CCI-Type NRP Instantitaion. The NRP ID in each NRP Instantiation TLV
<bcp14>MUST NOT</bcp14> be the same.</t>
</section>

<section anchor="sec-bw-subtlv"><name>Bandwidth Reservation Sub-TLV</name>
<t>When NRP Type is set to 1 (Queue based partition), A new Bandwidth Reservation
sub-TLV is used to describe the bandwidth reserved for the NRP on the link
specified by the corresponding FEC Object.</t>
<figure anchor="SEC2_FIG4" align="center"><name>Bandwidth Reservation sub-TLV </name>
<artwork align="center"><![CDATA[ 0                   1                   2                   3
 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 = TBD            |       Length (variable)       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|            Flags              |         Reserved              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               Committed Information Rate (CIR)                |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                 Peak Information Rate (PIR)                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>Where:</t>

<ul>
<li><t>Flags: 8-bit flags. Currently, the flags field is not used and MUST be set to zero on transmission.</t>
</li>
<li><t>Reserved: 16-bit reserved field for future use. All the bits <bcp14>MUST</bcp14> be set
to zero on transmission and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
<li><t>Committed Information Rate (CIR): Committed bandwidth in 4-byte
unsigned-integer number, the unit is kilobit (kb) per second.</t>
</li>
<li><t>Peak Information Rate (PIR): Peak bandwidth allocated from the link in
4-byte unsigned-integer  number, the unit is kilobit (kb) per second.</t>
</li>
</ul>
<t>The Bandwidth Reservation sub-TLV <bcp14>MUST</bcp14> appear only once in the NRP
Instantiation TLV.</t>
</section>
</section>
</section>

<section anchor="sec-ops"><name>Operations</name>
<t>The general operation of PCECC is specified in <xref target="RFC9050"></xref>. This section
describes the PCECC Operation for NRP Instantiation.</t>
<t>An NRP is instantiated by allocating a subset of network resources on the
network links of PCCs which participate in the NRP. This is achieved by PCE
instructing the PCCs to allocate the required network resources on the
specified links which are part of the NRP.</t>
<t>When both the PCE and PCC have advertised the PCECC capability with N bit set, and the PST set to '2', PCE sends a PCInitiate message to the PCC. The CCI Object-Type MUST be set to Resource Reservation. The FEC Object
<xref target="I-D.ietf-pce-pcep-extension-pce-controller-sr"></xref> is used to identify the link
on which the NRP and the set of resources need to be instantiated.</t>
<t>The LSP Object <bcp14>MUST</bcp14> be present, in which the PLSP-ID <bcp14>MUST</bcp14> be set to the reserved value zero, as the NRP instantiation is not specific to any LSP.
Additionally, the Tunnel Sender Address and Tunnel Endpoint Address MUST be set to the address of the PCC.
The Sybolic Path Name TLV MUST be present, in which the symbolic path name is recommended to be set to a unified name allocated by PCE.</t>
<t>In
the CCI Object, the NRP ID and the amount of resources (e.g., bandwidth) to be
allocated to the NRP are specified.</t>
<t>On receipt of a PCInitiate message for the PCECC NRP instantiation, the PCC
instantiates the NRP and reserves network resources on the specified link for
the NRP, then it responds with a PCRpt message with the PLSP-ID in the LSP
Object set to zero, the CC-ID in the CCI Object identifies the Central
Controller Instruction in the PCInitiate message.</t>

<artwork align="center"><![CDATA[            +---+                                              +---+
            |PCE|                                              |PCC|
            +-+-+                                              +-+-+
              |                                                  |
  PCECC NRP   |-----PCInitiate,PLSP-ID=0,FEC=A,CC-ID=X,<NRP>---->|
Instantiation |<-------- PCRpt,PLSP-ID=0, CC-ID=X ---------------|
              |                                                  |
]]></artwork>
</section>

<section anchor="sec-messages"><name>PCEP Messages</name>
<t>In the context of PCECC based NRP instantiation, the format of PCInitiate message
<xref target="RFC8281"></xref> and PCRpt message <xref target="RFC8231"></xref> are aligned with {{Section 6.1 of !I-D.ietf-pce-pcep-extension-pce-controller-sr}}.</t>
</section>

<section anchor="sec-security"><name>Security Considerations</name>
<t>This document defines a new CCI Object-Type that does not add any new security
concerns beyond those discussed in <xref target="RFC5440"></xref> in itself. For network
deployment in which NRP information is considered sensitive, the operator can
employ suitable PCEP security mechanisms like TCP Authentication Option (TCP-AO)
<xref target="RFC5925"></xref> or Transport Layer Security (TLS) <xref target="RFC8253"></xref>. The procedure based on
TLS is considered a security enhancement and thus is much better suited for the
sensitive information.</t>
</section>

<section anchor="sec-iana"><name>IANA Considerations</name>

<section anchor="sec-iana-pcecc"><name>PCECC-CAPABILITY Sub-TLV</name>
<t>IANA is requested to allocate a new bit for &quot;Resource Reservation&quot; in the
&quot;PCECC-CAPABILITY sub-TLV Flag Field&quot; sub-registry of the &quot;Path Computation
Element Protocol (PCEP) Numbers&quot; registry.</t>
<figure anchor="fig-iana-pcecc" align="center"><name>PCECC-CAPABILITY Sub-TLV Flag Field </name>
<artwork align="center"><![CDATA[   +======+======================+===============+
   | Bit  | Description          | Reference     |
   +======+======================+===============+
   | TBD1 | Resource Reservation | This document |
   +------+----------------------+---------------+
]]></artwork>
</figure>
</section>

<section anchor="sec-iana-objects"><name>PCEP Objects</name>
<t>IANA is requested to assign a new Object-Type for &quot;Resource reservation&quot; under
the CCI Object in the &quot;PCEP Objects&quot; sub-registry of the &quot;Path Computation
Element Protocol (PCEP) Numbers&quot; registry.</t>
<figure anchor="fig-iana-objects" align="center"><name>PCEP Objects Registry </name>
<artwork align="center"><![CDATA[  +====================+======+=======================+===========+
  | Object-Class Value | Name |     Object-Type       | Reference |
  +====================+======+=======================+===========+
  | 44                 | CCI  | TBD2:                 | This      |
  |                    |      | Resource Reservation  | document  |
  +--------------------+------+-----------------------+-----------+
]]></artwork>
</figure>
</section>

<section anchor="sec-iana-tlv"><name>PCEP TLV Type Indicators</name>
<t>IANA is requested to assign a new code point for &quot;NRP Instantiation TLV&quot; in the
&quot;PCEP TLV Type Indicators&quot; sub-registry of the &quot;Path Computation Element
Protocol (PCEP) Numbers&quot; registry.</t>
<t>IANA is requested to assign a new code point for &quot;Bandwidth Reservation&quot; in the
&quot;PCEP TLV Type Indicators&quot; sub-registry of the &quot;Path Computation Element
Protocol (PCEP) Numbers&quot; registry.</t>
<figure anchor="fig-iana-tlv" align="center"><name>PCEP TLV Type Indicators </name>
<artwork align="center"><![CDATA[   +=============+=======================+===============+
   | Value       | Description           | Reference     |
   +=============+=======================+===============+
   | TBD3        | NRP Instantiation     | This document |
   +-------------+-----------------------+---------------+
   | TBD4        | Bandwidth Reservation | This document |
   +--------=----+-----------------------+---------------+
]]></artwork>
</figure>
</section>
</section>

<section anchor="sec-contributors"><name>Contributors</name>
<t>TBD.</t>
</section>

<section anchor="sec-ack"><name>Acknowledgments</name>
<t>The authors would like to thank Dhruv Dhody for his review and valuable comments.</t>
</section>

</middle>

<back>
<references><name>References</name>
<references><name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-pce-pcep-extension-pce-controller-sr.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-teas-ns-ip-mpls.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5440.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8231.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8281.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8283.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9050.xml"/>
</references>
<references><name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4655.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4657.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5925.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8253.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9543.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9689.xml"/>
</references>
</references>

</back>

</rfc>
