RFC 8413: Framework for Scheduled Use of Resources
In plain English — editorial summary, not part of the RFC
Time-Scheduled (TS) reservation of Traffic Engineering (TE) resources can be used to provide resource booking for TE Label Switched Paths so as to better guarantee services for customers and to improve the efficiency of network resource usage at any moment in time, including network usage that is planned for the future. This document provides a framework that describes and discusses the architecture for supporting scheduled reservation of TE resources. This document does not describe specific protocols or protocol extensions needed to realize this service.
Document record
- Document ID
- RFC8413
- Published
- July 2018
- Authors
- Y. Zhuang; Q. Wu; H. Chen; A. Farrel
- Status
- INFORMATIONAL
- 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 7399Unanswered Questions in the Path Computation Element ArchitectureCurrent
October 2014
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
- RFC 5623Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
September 2009
- RFC 5521Extensions to the Path Computation Element Communication Protocol (PCEP) for Route ExclusionsCurrent
April 2009
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
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?