RFC 8281: Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
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. The extensions for stateful PCE provide active control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) via PCEP, for a model where the PCC delegates control over one or more locally configured LSPs to the PCE. This document describes the creation and deletion of PCE-initiated LSPs under the stateful PCE model.
Document record
- Document ID
- RFC8281
- Published
- December 2017
- Authors
- E. Crabbe; I. Minei; S. Sivabalan; R. Varga
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
- Updated by:
- RFC 9756
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 8282Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
December 2017
- RFC 8279Multicast Using Bit Index Explicit Replication (BIER)Current
November 2017
- RFC 8283An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central ControlCurrent
December 2017
- RFC 8277Using BGP to Bind MPLS Labels to Address PrefixesCurrent
October 2017
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
- RFC 8271Updates to the Resource Reservation Protocol for Fast Reroute of Traffic Engineering GMPLS Label Switched Paths (LSPs)Current
October 2017
- RFC 8293A Framework for Multicast in Network Virtualization over Layer 3Current
January 2018
- RFC 8294Common YANG Data Types for the Routing AreaCurrent
December 2017
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?