Skip to main content

OSPF Stub Router Advertisement

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3137.
Authors Alvaro Retana , Danny R. McPherson , Russ White , Alex D. Zinin , Liem Nguyen
Last updated 2015-08-20 (Latest revision 2000-11-27)
Replaces draft-zinin-ospf-stub-adv
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3137 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3137

        Title:      OSPF Stub Router Advertisement
        Author(s):  A. Retana, L. Nguyen, R. White, A. Zinin,
                    D. McPherson 
        Status:     Informational
        Date:       June 2001
        Pages:      5
        Characters: 8140
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ospf-stub-adv-02.txt


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.

This document is a product of the Open Shortest Path First IGP Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.