RFC 9757: Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
In plain English — editorial summary, not part of the RFC
This document introduces extensions to the Path Computation Element Communication Protocol (PCEP) to support path computation in Native IP networks through a PCE-based central control mechanism known as Centralized Control Dynamic Routing (CCDR). These extensions empower a PCE to calculate and manage paths specifically for Native IP networks, thereby expanding PCEP's capabilities beyond its past use in MPLS and GMPLS networks. By implementing these extensions, IP network resources can be utilized more efficiently, facilitating the deployment of traffic engineering in Native IP environments.
Document record
- Document ID
- RFC9757
- Published
- March 2025
- Authors
- A. Wang; B. Khasanov; S. Fang; C. Zhu
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8821PCE-Based Traffic Engineering (TE) in Native IP NetworksCurrent
April 2021
- RFC 8735Scenarios and Simulation Results of PCE in a Native IP NetworkCurrent
February 2020
- RFC 9756Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error CodesCurrent
March 2025
- RFC 9753Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) ObjectsCurrent
April 2025
- RFC 9752Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCECurrent
April 2025
- RFC 9764Bidirectional Forwarding Detection (BFD) Encapsulated in Large PacketsCurrent
April 2025
- RFC 9747Unaffiliated Bidirectional Forwarding Detection (BFD) EchoCurrent
March 2025
- RFC 9746BGP EVPN Multihoming Extensions for Split-Horizon FilteringCurrent
March 2025
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?