RFC 8741: Ability for a Stateful Path Computation Element (PCE) to Request and Obtain Control of a Label Switched Path (LSP)
In plain English — editorial summary, not part of the RFC
A stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs). When a PCE has stateful control over LSPs, it may send indications to LSP head-ends to modify the attributes (especially the paths) of the LSPs. A Path Computation Client (PCC) that has set up LSPs under local configuration may delegate control of those LSPs to a stateful PCE. There are use cases in which a stateful PCE may wish to obtain control of locally configured LSPs that it is aware of but have not been delegated to the PCE. This document describes an extension to the Path Computation Element Communication Protocol (PCEP) to enable a PCE to make requests for such control.
Document record
- Document ID
- RFC8741
- Published
- March 2020
- Authors
- A. Raghuram; A. Goddard; J. Karthik; S. Sivabalan; M. Negi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8745Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCEUpdated
March 2020
- RFC 8736PIM Message Type Space Extension and Reserved BitsObsoleted
February 2020
- RFC 8735Scenarios and Simulation Results of PCE in a Native IP NetworkCurrent
February 2020
- RFC 8733Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCEUpdated
February 2020
- RFC 8751Hierarchical Stateful Path Computation Element (PCE)Current
March 2020
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
- RFC 8770Host Router Support for OSPFv2Current
April 2020
- RFC 8775PIM Designated Router Load BalancingCurrent
April 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?