RFC 9358: Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual Networks
In plain English — editorial summary, not part of the RFC
This document describes how to extend the Path Computation Element Communication Protocol (PCEP) association mechanism introduced by RFC 8697 to further associate sets of Label Switched Paths (LSPs) with a higher-level structure such as a Virtual Network (VN) requested by a customer or application. This extended association mechanism can be used to facilitate control of a VN using the PCE architecture.
Document record
- Document ID
- RFC9358
- Published
- February 2023
- Authors
- Y. Lee; H. Zheng; D. Ceccarelli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9005Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)Current
March 2021
- RFC 8800Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint SignalingUpdated
July 2020
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 9357Label Switched Path (LSP) Object Flag Extension for Stateful PCEUpdated
February 2023
- RFC 9356Advertising Layer 2 Bundle Member Link Attributes in OSPFCurrent
January 2023
- RFC 9355OSPF Bidirectional Forwarding Detection (BFD) Strict-ModeCurrent
February 2023
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?