Internet-Draft draft-ietf-pce-sr-bidir-path-21.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) Extensions 
for Associated Bidirectional Segment Routing (SR) LSPs
   Authors: Cheng Li
            Mach(Guoyi) Chen
            Weiqiang Cheng
            Rakesh Gandhi
            Quan Xiong
   Name:    draft-ietf-pce-sr-bidir-path-21.txt
   Pages:   18
   Dates:   2026-02-04

Abstract:

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   Segment Routing (SR) can be used to steer packets through a network
   employing the source routing paradigm.  SR can be applied to both
   MPLS (SR-MPLS) and IPv6 (SRv6) data planes.  Stateful PCEP extensions
   for SR allow a PCE to maintain state and to control and initiate SR
   Traffic Engineering (TE) LSPs.

   PCEP supports grouping of two unidirectional MPLS-TE Label Switched
   Paths (LSPs), signaled via RSVP-TE, using association.  This document
   defines PCEP extensions for grouping two unidirectional SR LSPs (one
   in each direction in the network) into a single associated
   bidirectional SR LSP.  The mechanisms defined in this document are
   applicable to both stateless and stateful PCEs for PCE-initiated and
   PCC-initiated LSPs.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-sr-bidir-path/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-bidir-path-21

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sr-bidir-path-21

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


_______________________________________________
Pce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to