[Pce] I-D Action: draft-ietf-pce-controlled-id-space-03.txt

internet-drafts@ietf.org Mon, 20 October 2025 15:21 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176097366011.2054770.16046571066506529313@dt-datatracker-84f8f646b-tg6mn>
Date: Mon, 20 Oct 2025 08:21:00 -0700
Message-ID-Hash: 2KO5OY4QOLLZYYJ6DMBEAUHEIF4DAWKO
CC: pce@ietf.org
Reply-To: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-controlled-id-space-03.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/OxcQW_DO04MIfnVD2lYi7rRjFfc>

Internet-Draft draft-ietf-pce-controlled-id-space-03.txt is now available. It
is a work item of the Path Computation Element (PCE) WG of the IETF.

   Title:   Path Computation Element Communication Protocol (PCEP) extension to advertise the PCE Controlled Identifier Space
   Authors: Cheng Li
            Hang Shi
            Aijun Wang
            Weiqiang Cheng
            Chao Zhou
   Name:    draft-ietf-pce-controlled-id-space-03.txt
   Pages:   19
   Dates:   2025-10-20

Abstract:

   The Path Computation Element Communication Protocol (PCEP) provides a
   mechanism for the Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   The Stateful PCE extensions allow stateful control of Multiprotocol
   Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
   (LSPs) using PCEP.  Furthermore, PCE can be used for computing paths
   in the SR networks.

   Stateful PCE provides active control of MPLS-TE LSPs via PCEP, for a
   model where the PCC delegates control over one or more locally
   configured LSPs to the PCE.  Further, stateful PCE could also create
   and remove PCE-initiated LSPs by itself.  A PCE-based Central
   Controller (PCECC) simplify the processing of a distributed control
   plane by integrating with elements of Software-Defined Networking
   (SDN).

   In some use cases, such as PCECC provisioning or Binding Segment
   Identifier (SID) for Segment Routing (SR) allocation, there are
   requirements for a stateful PCE to make allocation of labels, SIDs,
   etc.  These use cases require PCE to be aware of various identifier
   spaces from where to make allocations on behalf of a PCC.  This
   document defines a generic mechanism by which a PCC can inform the
   PCE of the identifier space set aside for the PCE control via PCEP.
   The identifier could be an MPLS label, a SID, or any other identifier
   that can be allocated and managed by the PCE.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-controlled-id-space/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-pce-controlled-id-space-03

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-controlled-id-space-03

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[Pce] I-D Action: draft-ietf-pce-controlled-id-sp… internet-drafts