OSPFv2 Metric Auto-Decay
draft-giacalone-metric-auto-decay-routing-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Spencer Giacalone | ||
| Last updated | 2001-04-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 memo specifies mechanisms for automatically decaying OSPFv2 [1] metrics and priorities in the event of partial, but critical, system failures (errors) which do not cause interfaces to change state (i.e. they are opaque to transient to data). The mechanisms defined in this document, called metric auto-decay, allow operators to configure OSPFv2 networks to gracefully bypass devices which have incurred these opaque system errors.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)