RFC 6689: Usage of the RSVP ASSOCIATION Object
In plain English — editorial summary, not part of the RFC
The Resource Reservation Protocol (RSVP) ASSOCIATION object is defined in the context of GMPLS-controlled label switched paths (LSPs). In this context, the object is used to associate recovery LSPs with the LSP they are protecting. This document reviews how the association is to be provided in the context of GMPLS recovery. No new procedures or mechanisms are defined by this document, and it is strictly informative in nature. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6689
- Published
- July 2012
- Authors
- L. Berger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6387GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)Current
September 2011
- RFC 5852RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport NetworkCurrent
April 2010
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrent
January 2010
- RFC 4873GMPLS Segment RecoveryUpdated
May 2007
- RFC 4872RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) RecoveryUpdated
May 2007
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdated
May 2005
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
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?