RFC 8282: Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering
In plain English — editorial summary, not part of the RFC
The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. MPLS and GMPLS networks may be constructed from layered service networks. It is advantageous for overall network efficiency to provide end-to-end traffic engineering across multiple network layers through a process called inter-layer traffic engineering. PCE is a candidate solution for such requirements. The PCE Communication Protocol (PCEP) is designed as a communication protocol between Path Computation Clients (PCCs) and PCEs. This document presents PCEP extensions for inter-layer traffic engineering.
Document record
- Document ID
- RFC8282
- Published
- December 2017
- Authors
- E. Oki; T. Takeda; A. Farrel; F. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8685Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) ArchitectureUpdated
December 2019
- RFC 4258Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON)Current
November 2005
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 8735Scenarios and Simulation Results of PCE in a Native IP NetworkCurrent
February 2020
- RFC 7823Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric ExtensionsCurrent
May 2016
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
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?