RFC 6383: Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TE
In plain English — editorial summary, not part of the RFC
The Resource Reservation Protocol (RSVP) has been extended to support Traffic Engineering (TE) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The protocol enables signaling exchanges to establish Label Switched Paths (LSPs) that traverse nodes and link to provide end-to-end data paths. Each node is programmed with "cross-connect" information as the signaling messages are processed. The cross-connection information instructs the node how to forward data that it receives. End points of an LSP need to know when it is safe to start sending data so that it is not misdelivered, and so that safety issues specific to optical data-plane technology are satisfied. Likewise, all label switching routers along the path of the LSP need to know when to program their data planes relative to sending and receiving control-plane messages. This document clarifies and summarizes the RSVP-TE protocol exchanges with relation to the programming of cross-connects along an LSP for both unidirectional and bidirectional LSPs. This document does not define any new procedures or protocol extensions, and defers completely to the documents that provide normative references. The clarifications set out in this document may also be used to help interpret LSP establishment performance figures for MPLS-TE and GMPLS devices. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6383
- Published
- September 2011
- Authors
- K. Shiomoto; A. Farrel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)Current
July 2015
- RFC 7699Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching RoutersCurrent
November 2015
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 8625Ethernet Traffic Parameters with Availability InformationCurrent
August 2019
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
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?