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

   Title:   Update to Automatic Bandwidth Adjustment Procedure of Stateful PCE 
for MPLS-TE and SR-TE LSPs
   Authors: Shuping Peng
            Dhruv Dhody
            Rakesh Gandhi
   Name:    draft-ietf-pce-stateful-pce-autobw-update-03.txt
   Pages:   10
   Dates:   2025-11-05

Abstract:

   The Stateful PCE extensions allow Stateful control of Traffic
   Engineering (TE) LSPs using PCEP for RSVP-TE and Segment Routing (SR)
   (for both MPLS and IPv6 Data planes) for both PCE-Initiated and PCC-
   Initiated LSPs.

   Extensions to the Path Computation Element Communication Protocol
   (PCEP) for MPLS-TE Label Switched Path (LSP) Automatic Bandwidth
   Adjustments with Stateful PCE are defined in RFC 8733.  It defines
   the AUTO-BANDWIDTH-ATTRIBUTES TLV and a set of sub-TLVs for each of
   the attributes.  The sub-TLVs are included if there is a change since
   the last information sent in the PCEP message.  However, it lacks a
   mechanism to remove an attribute identified by the sub-TLV
   explicitly.

   This document updates RFC 8733 by defining the behaviour to remove an
   attribute explicitly.

   In addition, this document updates RFC 8733 by applying the PCEP
   extensions to SR-TE LSPs (for both MPLS and IPv6 Data planes), in
   addition to MPLS-TE LSPs.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-autobw-update/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-pce-stateful-pce-autobw-update-03.html

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

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