RFC 8733: Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCE
In plain English — editorial summary, not part of the RFC
The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests. Stateful PCE extensions allow stateful control of MPLS-TE Label Switched Paths (LSPs) using PCEP. The auto-bandwidth feature allows automatic and dynamic adjustment of the TE LSP bandwidth reservation based on the volume of traffic flowing through the LSP. This document describes PCEP extensions for auto-bandwidth adjustment when employing an active stateful PCE for both PCE-initiated and PCC-initiated LSPs.
Document record
- Document ID
- RFC8733
- Published
- February 2020
- Authors
- D. Dhody; R. Gandhi; U. Palle; R. Singh; L. Fang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
- Updated by:
- RFC 9756
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8735Scenarios and Simulation Results of PCE in a Native IP NetworkCurrent
February 2020
- RFC 8736PIM Message Type Space Extension and Reserved BitsObsoleted
February 2020
- RFC 8741Ability for a Stateful Path Computation Element (PCE) to Request and Obtain Control of a Label Switched Path (LSP)Current
March 2020
- RFC 8745Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCEUpdated
March 2020
- RFC 8751Hierarchical Stateful Path Computation Element (PCE)Current
March 2020
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
- RFC 8706Restart Signaling for IS-ISCurrent
February 2020
- RFC 8703Dynamic Link Exchange Protocol (DLEP) Link Identifier ExtensionCurrent
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?