Usage of The RSVP Association Object
draft-berger-ccamp-assoc-info-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Lou Berger , François Le Faucheur , Ashok Narayanan | ||
Last updated | 2013-05-14 (Latest revision 2010-03-08) | ||
Replaced by | draft-ietf-ccamp-assoc-info | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ccamp-assoc-info | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The RSVP ASSOCIATION object was defined in the context of GMPLS (Generalized Multi-Protocol Label Switching) 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, and this document defines how the ASSOCIATION object can be more generally applied. The document also reviews how the association is to be provided in the context of GMPLS recovery. No new new procedures or mechanisms are defined with respect to GMPLS recovery.
Authors
Lou Berger
François Le Faucheur
Ashok Narayanan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)