RSVP Setup Protection
draft-shen-mpls-rsvp-setup-protection-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yimin Shen , Yuji Kamite , Eric Osborne | ||
| Last updated | 2013-12-30 (Latest revision 2013-06-28) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
RFC 4090 specifies an RSVP facility-backup fast reroute mechanism for protecting LSPs against link and node failures. This document extends the mechanism to provide so-called "setup protection" for LSPs during their initial Path message signaling time. In particular, it enables a router to reroute an LSP via an existing bypass LSP, when there is a failure of the immediate downstream link or node along the desired path. Therefore, it can be used to avoid LSP signaling failure and reduce setup time in such kind of situation, and allow an LSP to be established temporarily over a bypass LSP when an alternative path can only be resolved at a much later time.
Authors
Yimin Shen
Yuji Kamite
Eric Osborne
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)