Distinguish a link from a node failure using RSVP Hellos extensions
draft-vasseur-mpls-linknode-failure-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Anna Charny , JP Vasseur | ||
| Last updated | 2002-10-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
The aim of this draft is to provide a method to distinguish a link from a node failure using RSVP hello extensions. In a network making use of MPLS Traffic Engineering Fast Reroute as specified in [FAST-REROUTE], efficient use can be made of the network links when protecting against link/node failures. As described in [FACILITY], excess capacity used for bypass tunnels can be shared between bypass tunnels providing protection for mutually exclusive failures of different links or nodes. This results in significant bandwidth savings under the single failure assumption. Making use of the single failure assumption implies the need to distinguish a link from a node failure. However, the mechanisms currently available for failures detection do not always allow to distinguishing a link from a node failure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)