RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture
In plain English — editorial summary, not part of the RFC
The Hierarchical Path Computation Element (H-PCE) architecture is defined in RFC 6805. It provides a mechanism to derive an optimum end-to-end path in a multi-domain environment by using a hierarchical relationship between domains to select the optimum sequence of domains and optimum paths across those domains. This document defines extensions to the Path Computation Element Communication Protocol (PCEP) to support H-PCE procedures.
Document record
- Document ID
- RFC8685
- Published
- December 2019
- Authors
- F. Zhang; Q. Zhao; O. Gonzalez de Dios; R. Casellas; D. King
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
- Updated by:
- RFC 9756
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8282Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
December 2017
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 8735Scenarios and Simulation Results of PCE in a Native IP NetworkCurrent
February 2020
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 9256Segment Routing Policy ArchitectureCurrent
July 2022
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 7823Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric ExtensionsCurrent
May 2016
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?