Fault Notification Protocol for GMPLS-Based Recovery
draft-rabbat-fault-notification-protocol-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard Rabbat | ||
| Last updated | 2004-06-01 | ||
| 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 draft presents a fault notification protocol for use in a GMPLS- based failure recovery scheme. The protocol guarantees recovery path(s) activation in a bounded time in the event of single resource failures. These failures include fiber cut, transponder failure and node failure. Bounded recovery time is achieved by pre-signaling recovery paths whose nodes can be reached within a specific time, based on the physical capabilities of the nodes and the delay characteristics of the control plane. We propose using a flooding protocol for fault notification to allow for per-failure notification and to speed up the recovery process. We justify choices made for the notification method and the messaging required for the protocol. The draft does not mandate a specific implementation of the Fault Notification Protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)