RFC 8800: Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling
In plain English — editorial summary, not part of the RFC
This document introduces a simple mechanism to associate a group of Label Switched Paths (LSPs) via an extension to the Path Computation Element Communication Protocol (PCEP) with the purpose of computing diverse (disjointed) paths for those LSPs. The proposed extension allows a Path Computation Client (PCC) to advertise to a Path Computation Element (PCE) that a particular LSP belongs to a particular Disjoint Association Group; thus, the PCE knows that the LSPs in the same group need to be disjoint from each other.
Document record
- Document ID
- RFC8800
- Published
- July 2020
- Authors
- S. Litkowski; S. Sivabalan; C. Barth; M. Negi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- 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 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 9005Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)Current
March 2021
- RFC 9358Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual NetworksCurrent
February 2023
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 8796RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) TunnelsCurrent
July 2020
- RFC 8795YANG Data Model for Traffic Engineering (TE) TopologiesCurrent
August 2020
- RFC 8810Revision to Capability Codes Registration ProceduresCurrent
August 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?