RSVP-TE Signaling For GMPLS Restoration LSP
draft-gandhi-ccamp-gmpls-restoration-lsp-04
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Rakesh Gandhi , Zafar Ali , Gabriele Galimberti , Xian Zhang | ||
Last updated | 2014-10-25 (Latest revision 2014-04-23) | ||
Replaced by | draft-ietf-ccamp-gmpls-resource-sharing-proc | ||
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-gmpls-resource-sharing-proc | |
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
In transport networks, there are requirements where Generalized Multi-Protocol Label Switching (GMPLS) end-to-end recovery scheme needs to employ restoration Label Switched Path (LSP) while keeping resources for the working and/or protecting LSPs reserved in the network after the failure. This document reviews how the LSP association is to be provided using Resource Reservation Protocol - Traffic Engineering (RSVP-TE) signaling in the context of GMPLS end-to-end recovery when using restoration LSP where failed LSP is not torn down. No new procedures or mechanisms are defined by this document, and it is strictly informative in nature.
Authors
Rakesh Gandhi
Zafar Ali
Gabriele Galimberti
Xian Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)