Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- 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.
- Publication Date
- 2025-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9752- Link
- https://doi.org/10.17487/RFC9752
- Author(s)
- Cheng LiHaomian ZhengSiva SivabalanSamuel SidorZafar Ali
- Keyword(s)
- PCE, Vendor-specific
Latest version of IETF RFC 9752
Document Versions — IETF RFC 9752
-
▶ IETF RFC 9752 (2025-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5511 [Active*]
- IETF RFC 7470 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8231 [Active*]
- IETF RFC 8281 [Active*]
- IETF RFC 8996 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-pce-pcep-yang-30 — PCEP-YANG EXTERNAL
- IETF RFC 2578 [Active*]
- IETF RFC 8051 [Active*]
- IETF RFC 8253 [Active*]
- IETF RFC 9371 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9752.json
Amends:
IETF RFC 7470 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9752, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE. Available at https://doi.org/10.17487/RFC9752
Snippet:
IETF RFC 9752, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE. Available at https://doi.org/10.17487/RFC9752
HTML (ISO 690 compliant)
Preview:
IETF RFC 9752, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE. Available at https://doi.org/10.17487/RFC9752
Snippet:
<span class="citation"><cite>IETF RFC 9752</cite>, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE. Available at <a href="https://doi.org/10.17487/RFC9752" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9752</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9752, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
doi: 10.17487/RFC9752
url: https://doi.org/10.17487/RFC9752
doi: 10.17487/RFC9752
url: https://doi.org/10.17487/RFC9752
Snippet:
<li> <cite id="bib-rfc9752">IETF RFC 9752</cite>, Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE <span class="doi">10.17487/RFC9752</span> </li>