Implementation and Performance of Flooding-based Fault Notification
draft-rabbat-ccamp-perf-flooding-notification-exp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard Rabbat | ||
| Last updated | 2004-02-06 | ||
| 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 memo presents the observations and results obtained from two test-beds designed to study and evaluate the performance and feasibility of rapid fault notification via flooding. Flooding-based fault notification [2,3] is an alternative to signaling-only notification approaches, which has the advantages of: scalability and the ability to meet bounded recovery-time constraints, if needed. We implemented flooding-based notification at both the transport and packet layers. For optical transport networks the flooding mechanism (e.g. [3]), was realized using enhancements to the Link Management Protocol (LMP), while for packet/MPLS networks the flooding was realized using enhancements to Open Shortest Path First (OSPF). We present experiences and performance measurements from these implementations on FreeBSD/Linux platforms, and also present the protocol enhancements that were made to LMP and OSPF, respectively, to realize the rapid flooding function.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)