OSPF Floodgates
draft-ietf-ospf-floodgates-01
| Document | Type |
Expired Internet-Draft
(ospf WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Patrick W. Murphy | ||
| Last updated | 2001-02-26 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 describes an option to the OSPF Version 2 specification which allows the partial suppression of flooding between neighboring routers. This suppression acts much like a floodgate, opening and closing automatically when triggered by the proper conditions. Two types of flooding suppression are described, 1-Way and 2-Way. The option applies to standard areas, stub areas, and NSSAs. It works over any OSPF interface. Routers with this option configured are backward compatible with routers running an OSPFv2 compliant implementation as defined in RFC 2328, and can be restricted to a subset of the OSPF routing domain. This option is applied only between neighboring OSPF routers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)