Extensions to LMP for Flooding-based Fault Notification
draft-soumiya-lmp-fault-notification-ext-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Toshio Soumiya , Richard Rabbat | ||
| Last updated | 2004-01-07 | ||
| 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 describes extensions to the Link Management Protocol (LMP) for use in flooding-based fault notification in optical networks. We focus on networks that use a common control plane (e.g, Generalized Multi-Protocol Label Switching or GMPLS). These extensions implement the Fault Notification Protocol, a flooding-based approach to notifying faults to nodes in the network. We motivate the use of LMP extensions for flooding, define message formats and explain the communication messages that occur using LMP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)