RFC 6780: RSVP ASSOCIATION Object Extensions
In plain English — editorial summary, not part of the RFC
The RSVP ASSOCIATION object was 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 object also has broader applicability as a mechanism to associate RSVP state. This document defines how the ASSOCIATION object can be more generally applied. This document also defines Extended ASSOCIATION objects that, in particular, can be used in the context of the MPLS Transport Profile (MPLS-TP). This document updates RFC 2205, RFC 3209, and RFC 3473. It also generalizes the definition of the Association ID field defined in RFC 4872. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6780
- Published
- October 2012
- Authors
- L. Berger; F. Le Faucheur; A. Narayanan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 6777Label Switched Path (LSP) Data Path Delay Metrics in Generalized MPLS and MPLS Traffic Engineering (MPLS-TE) NetworksCurrent
November 2012
- RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated
November 2012
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 6805The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLSCurrent
November 2012
- RFC 6754Protocol Independent Multicast Equal-Cost Multipath (ECMP) RedirectUpdated
October 2012
- RFC 6807Population Count Extensions to Protocol Independent Multicast (PIM)Current
December 2012
- RFC 6810The Resource Public Key Infrastructure (RPKI) to Router ProtocolUpdated
January 2013
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?