RFC 9826: A YANG Data Model for the Path Computation Element Communication Protocol (PCEP)
In plain English — editorial summary, not part of the RFC
This document defines a YANG data model for the management of the Path Computation Element Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs.
Document record
- Document ID
- RFC9826
- Published
- September 2025
- Authors
- D. Dhody; V. Beeram; J. Hardwick; J. Tantsura
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 108
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9825Extensions to OSPF for Advertising Prefix Administrative TagsCurrent
July 2025
- RFC 9830Advertising Segment Routing Policies in BGPCurrent
September 2025
- RFC 9831Segment Type Extensions for BGP Segment Routing (SR) PolicyCurrent
September 2025
- RFC 9832BGP Classful Transport PlanesCurrent
September 2025
- RFC 9819Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6)Current
July 2025
- RFC 9816Usage and Applicability of BGP Link State (BGP-LS) Shortest Path First (SPF) Routing in Data CentersCurrent
July 2025
- RFC 9815BGP Link State (BGP-LS) Shortest Path First (SPF) RoutingCurrent
July 2025
- RFC 9843IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and ConstraintsUpdated
September 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?