RFC 8745: Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
In plain English — editorial summary, not part of the RFC
An active stateful Path Computation Element (PCE) is capable of computing as well as controlling via Path Computation Element Communication Protocol (PCEP) Multiprotocol Label Switching Traffic Engineering (MPLS-TE) Label Switched Paths (LSPs). Furthermore, it is also possible for an active stateful PCE to create, maintain, and delete LSPs. This document defines the PCEP extension to associate two or more LSPs to provide end-to-end path protection.
Document record
- Document ID
- RFC8745
- Published
- March 2020
- Authors
- H. Ananthakrishnan; S. Sivabalan; C. Barth; I. Minei; M. Negi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- 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 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 9357Label Switched Path (LSP) Object Flag Extension for Stateful PCEUpdated
February 2023
- RFC 7897Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7896Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)Current
June 2016
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?