RFC 7551: RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs)
In plain English — editorial summary, not part of the RFC
This document describes Resource Reservation Protocol (RSVP) extensions to bind two point-to-point unidirectional Label Switched Paths (LSPs) into an associated bidirectional LSP. The association is achieved by defining new Association Types for use in ASSOCIATION and in Extended ASSOCIATION Objects. One of these types enables independent provisioning of the associated bidirectional LSPs on both sides, while the other enables single-sided provisioning. The REVERSE_LSP Object is also defined to enable a single endpoint to trigger creation of the reverse LSP and to specify parameters of the reverse LSP in the single-sided provisioning case.
Document record
- Document ID
- RFC7551
- Published
- May 2015
- Authors
- F. Zhang; R. Jing; R. Gandhi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
- Updated by:
- RFC 8537
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 7552Updates to LDP for IPv6Current
June 2015
- RFC 7555Proxy MPLS Echo RequestCurrent
June 2015
- RFC 7543Covering Prefixes Outbound Route Filter for BGP-4Current
May 2015
- RFC 7537IANA Registries for LSP Ping Code PointsObsoleted
May 2015
- RFC 7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)Current
July 2015
- RFC 7571GMPLS RSVP-TE Extensions for Lock Instruct and LoopbackCurrent
July 2015
- RFC 7524Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)Updated
May 2015
- RFC 7579General Network Element Constraint Encoding for GMPLS-Controlled NetworksCurrent
June 2015
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?