OSPF Stub Router Advertisement
draft-ietf-ospf-rfc3137bis-03

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2013-03-28 (latest revision 2013-01-16)
Replaces draft-retana-ospf-rfc3137bis
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Stewart Bryant
IESG note Abhay Roy (akr@cisco.com) is the document shepherd.
Send notices to ospf-chairs@tools.ietf.org, draft-ietf-ospf-rfc3137bis@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
Network Working Group                                          A. Retana
Internet-Draft                                                 L. Nguyen
Obsoletes: 3137 (if approved)                        Cisco Systems, Inc.
Intended status: Informational                                  A. Zinin
Expires: July 21, 2013                                   Cinarra Systems
                                                                R. White
                                                            D. McPherson
                                                          Verisign, Inc.
                                                        January 17, 2013

                     OSPF Stub Router Advertisement
                     draft-ietf-ospf-rfc3137bis-03

Abstract

   This document 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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 21, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Retana, et al.            Expires July 21, 2013                 [Page 1]
Internet-Draft       OSPF Stub Router Advertisement         January 2013

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  OSPFv3-only Solution  . . . . . . . . . . . . . . . . . . . 4
   3.  Maximum Link Metric . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Deployment Considerations . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   8.  Informative References  . . . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . . . 5
     A.1.  Changes between the -00 and -01 versions. . . . . . . . . . 5
     A.2.  Changes between the -01 and -02 versions. . . . . . . . . . 6
     A.3.  Changes between the -02 and -03 versions. . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Retana, et al.            Expires July 21, 2013                 [Page 2]
Internet-Draft       OSPF Stub Router Advertisement         January 2013

1.  Introduction

   In some situations, it may be advantageous to inform routers in a
   network not to use a specific router as a transit point, but still
   route to it.  Possible situations include the following:

   o  The router is in a critical condition (for example, has very high
      CPU load or does not have enough memory to store all LSAs or build
      the routing table).

   o  Graceful introduction and removal of the router to/from the
      network.

   o  Other (administrative or traffic engineering) reasons.

   Note that the solution introduced in this document does not remove
   the router from the topology view of the network (as could be done by
   just flushing that router's router-LSA), but discourages other
   routers from using it for transit routing, while still routing
   packets to the router's own IP addresses, i.e., the router is
   announced as a stub.

   It must be emphasized that the solution provides real benefits in
   networks designed with at least some level of redundancy so that
   traffic can be routed around the stub router.  Otherwise, traffic
   destined for the networks reachable through such a stub router may
   still be routed through it.
Show full document text