The IESG has received a request from the Path Computation Element WG (pce) to
consider the following document: - 'Carrying SR-Algorithm in Path Computation
Element Communication
   Protocol (PCEP)'
  <draft-ietf-pce-sid-algo-24.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[email protected] mailing lists by 2025-09-25. Exceptionally, comments may
be sent to [email protected] instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document specifies extensions to the Path Computation Element
   Communication Protocol (PCEP) to enhance support for Segment Routing
   (SR) with a focus on the use of Segment Identifiers (SIDs) and SR-
   Algorithms in Traffic Engineering (TE).  The SR-Algorithm associated
   with a SID defines the path computation algorithm used by Interior
   Gateway Protocols (IGPs).  This document introduces extensions in
   three main areas.

   Mechanisms for informing PCEP peers about the SR-Algorithm associated
   with SIDs by encoding this information in Explicit Route Object (ERO)
   and Record Route Object (RRO) subobjects.  This document updates RFC
   8664 and RFC 9603 to allow such extension.

   The document specifies SR-Algorithm constraint, enabling refined path
   computations that can leverage IGP algorithm logic, including
   Flexible Algorithms, and their associated constraints and
   optimization metrics.

   It defines new metric types for the METRIC object required to support
   SR-Algorithm based path computation, but also applicable to Label
   Switched Paths (LSPs) setup using different Path Setup Types.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pce-sid-algo/



No IPR declarations have been submitted directly on this I-D.





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

Reply via email to