RFC 8934: PCE Communication Protocol (PCEP) Extensions for Label Switched Path (LSP) Scheduling with Stateful PCE
In plain English — editorial summary, not part of the RFC
This document defines a set of extensions to the stateful PCE Communication Protocol (PCEP) to enable Label Switched Path (LSP) path computation, activation, setup, and deletion based on scheduled time intervals for the LSP and the actual network resource usage in a centralized network environment, as stated in RFC 8413.
Document record
- Document ID
- RFC8934
- Published
- October 2020
- Authors
- H. Chen; Y. Zhuang; Q. Wu; D. Ceccarelli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- 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 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 9353IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)Current
January 2023
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 5441A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched PathsCurrent
April 2009
- RFC 5376Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)Current
November 2008
- RFC 4927Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic EngineeringCurrent
June 2007
- RFC 5468Performance Analysis of Inter-Domain Path Computation MethodologiesCurrent
April 2009
- RFC 8938Deterministic Networking (DetNet) Data Plane FrameworkCurrent
November 2020
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?