RFC 9005: Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)
In plain English — editorial summary, not part of the RFC
This document introduces a simple mechanism to associate policies with a group of Label Switched Paths (LSPs) via an extension to the Path Computation Element Communication Protocol (PCEP). The extension allows a PCEP speaker to advertise to a PCEP peer that a particular LSP belongs to a particular Policy Association Group (PAG).
Document record
- Document ID
- RFC9005
- Published
- March 2021
- Authors
- S. Litkowski; S. Sivabalan; J. Tantsura; J. Hardwick; C. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
- RFC 8800Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint SignalingUpdated
July 2020
- RFC 9305Locator/ID Separation Protocol (LISP) Generic Protocol ExtensionCurrent
October 2022
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 9358Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual NetworksCurrent
February 2023
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1477IDPR as a Proposed StandardCurrent
July 1993
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?