OSPF Stub Router Advertisement
draft-retana-ospf-rfc3137bis-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Alvaro Retana , Liem Nguyen , Russ White , Alex D. Zinin , Danny R. McPherson | ||
Last updated | 2012-10-22 (Latest revision 2011-05-09) | ||
Replaced by | draft-ietf-ospf-rfc3137bis | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ospf-rfc3137bis | |
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 a backward-compatible technique that may be used by OSPF (Open Shortest Path First) implementations to advertise unavailability to forward transit traffic or to lower the preference level for the paths through such a router. In some cases, it is desirable not to route transit traffic via a specific OSPF router. However, OSPF does not specify a standard way to accomplish this.
Authors
Alvaro Retana
Liem Nguyen
Russ White
Alex D. Zinin
Danny R. McPherson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)