RFC 9059: Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs)
In plain English — editorial summary, not part of the RFC
This document defines Path Computation Element Communication Protocol (PCEP) extensions for grouping two unidirectional MPLS-TE Label Switched Paths (LSPs), one in each direction in the network, into an associated bidirectional LSP. These PCEP extensions can be applied either using a stateful PCE for both PCE-initiated and PCC-initiated LSPs or using a stateless PCE. The PCEP procedures defined are applicable to the LSPs using RSVP-TE for signaling.
Document record
- Document ID
- RFC9059
- Published
- June 2021
- Authors
- R. Gandhi; C. Barth; B. Wen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- 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 8537Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)Current
February 2019
- RFC 9056Deterministic Networking (DetNet) Data Plane: IP over MPLSCurrent
October 2021
- RFC 9062Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)Current
June 2021
- RFC 9055Deterministic Networking (DetNet) Security ConsiderationsCurrent
June 2021
- RFC 9067A YANG Data Model for Routing PolicyCurrent
October 2021
- RFC 9050Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPsUpdated
July 2021
- RFC 9070YANG Data Model for MPLS LDPCurrent
March 2022
- RFC 9047Propagation of ARP/ND Flags in an Ethernet Virtual Private Network (EVPN)Current
June 2021
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?