RFC 9752: Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
In plain English — editorial summary, not part of the RFC
This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) that enable the inclusion of vendor-specific information in stateful Path Computation Element (PCE) operations. These extensions allow vendors to incorporate proprietary data within PCEP messages, facilitating enhanced network optimization and functionality in environments requiring vendor-specific features. The extensions maintain compatibility with existing PCEP implementations and promote interoperability across diverse network deployments. RFC 7470 defines a facility to carry vendor-specific information in stateless PCEP messages. This document extends this capability for the stateful PCEP messages. This document updates RFC 7470 to specify that Enterprise Numbers are managed through the "Private Enterprise Numbers (PENs)" registry.
Document record
- Document ID
- RFC9752
- Published
- April 2025
- Authors
- C. Li; H. Zheng; S. Sivabalan; S. Sidor; Z. Ali
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 7470
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9168Path Computation Element Communication Protocol (PCEP) Extension for Flow SpecificationUpdated
January 2022
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 8664Path Computation Element Communication Protocol (PCEP) Extensions for Segment RoutingUpdated
December 2019
- RFC 8637Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN)Current
July 2019
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 8283An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central ControlCurrent
December 2017
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?