OSPF Stub Router Advertisement
draft-zinin-ospf-stub-adv-00

Document Type Replaced Internet-Draft (individual)
Last updated 2000-07-25
Replaced by draft-ietf-ospf-stub-adv
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ospf-stub-adv
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-zinin-ospf-stub-adv-00.txt

Abstract

In some cases, it is desirable not to route transit traffic via a specific OSPF router. However, OSPF [RFC2328] does not specify a standard way to accomplish this. This memo describes a backward- compatible technique that may be used by OSPF implementations to advertise unavailability to forward transit traffic or to lower the preference level for the paths through such a router.

Authors

Alex Zinin (azinin@cisco.com)
Alvaro Retana (alvaro@cisco.com)
Liem Nguyen (lhnguyen@cisco.com)
Russ White (riw@cisco.com)
Danny McPherson (danny@arbor.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)