Fast Reroute Techniques in RSVP-TE
draft-pan-rsvp-fastreroute-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ping Pan | ||
| Last updated | 2001-11-27 | ||
| 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
This document describes the use of RSVP [RSVP, RSVP-TE] to establish backup LSP tunnels for local repair of LSP tunnels. Two methods are presented here. One is to setup one-to-one detour LSPs according to the requirements defined by the head-end users. The other is to setup many-to-one bypass LSP using a single bypass tunnel to backup a set of protected LSPs (making use of label stacking) to reroute both data and control traffic. Both methods can protect both link and node during network failure, and make use of local protection techniques.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)