RFC 8051: Applicability of a Stateful Path Computation Element (PCE)
In plain English — editorial summary, not part of the RFC
A stateful Path Computation Element (PCE) maintains information about Label Switched Path (LSP) characteristics and resource usage within a network in order to provide traffic-engineering calculations for its associated Path Computation Clients (PCCs). This document describes general considerations for a stateful PCE deployment and examines its applicability and benefits, as well as its challenges and limitations, through a number of use cases. PCE Communication Protocol (PCEP) extensions required for stateful PCE usage are covered in separate documents.
Document record
- Document ID
- RFC8051
- Published
- January 2017
- Authors
- X. Zhang; I. Minei
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8231Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCEUpdated
September 2017
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
September 2017
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9504Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled NetworksUpdated
December 2023
- RFC 2894Router Renumbering for IPv6Current
August 2000
- RFC 8059PIM Join Attributes for Locator/ID Separation Protocol (LISP) EnvironmentsUpdated
January 2017
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?