datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Graceful OSPF Restart Implementation Report
RFC 4167

Document type: RFC - Informational (October 2005)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4167 (Informational)
Responsible AD: Alex Zinin
Send notices to: acee@redback.com, rohit@utstar.com

Network Working Group                                          A. Lindem
Request for Comments: 4167                            Cisco Systems, Inc
Category: Informational                                     October 2005

              Graceful OSPF Restart Implementation Report

Status of This Memo

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

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   Graceful OSPF Restart, as specified in RFC 3623, provides a mechanism
   whereby an OSPF router can stay on the forwarding path even as its
   OSPF software is restarted.  This document provides an implementation
   report for this extension to the base OSPF protocol.

Table of Contents

   1. Overview ........................................................2
   2. Implementation Experience .......................................2
      2.1. Implementation Differences .................................2
   3. MIB Reference ...................................................3
   4. Authentication Mechanisms .......................................3
   5. List of Implementations .........................................3
   6. Test Scenarios ..................................................3
   7. Operational Experience ..........................................4
   8. Security Considerations .........................................4
   9. Normative References ............................................4
   10. Informative References .........................................4
   11. Acknowledgments ................................................5

Lindem                       Informational                      [Page 1]
RFC 4167      Graceful OSPF Restart Implementation Report   October 2005

1.  Overview

   Today, many Internet routers implement a separation of control and
   forwarding functions.  Certain processors are dedicated to control
   and management tasks such as OSPF routing, while other processors
   perform the data forwarding tasks.  This separation creates the
   possibility of maintaining a router's data forwarding capability
   while the router's control software is restarted/reloaded.  For the
   OSPF protocol [OSPF], the protocol mechanisms necessary to accomplish
   this are described in Graceful OSPF Restart [GRACE].

   This document satisfies the RFC 1264 [CRITERIA] requirement for a
   report on implementation experience for Graceful OSPF Restart.
   Section 2 of this document contains the results of an implementation
   survey.  It also documents implementation differences between the
   vendors responding to the survey.  Section 3 contains a MIB
   reference.  Section 4 provide an authentication reference.  Section 5
   simply refers to the implementations listed in section 2.  Section 6
   includes a minimal set of test scenarios.  Finally, section 7
   includes a disclaimer with respect to operational experience.

2.  Implementation Experience

   Eleven vendors have implemented graceful OSPF and have completed the
   implementation survey.  These include Redback, Juniper, Motorola
   Computer Group (formerly Netplane Systems), Mahi Networks, Nexthop
   technologies, Force10 Networks, Procket, Alcatel, Laurel Networks,
   DCL (Data Connection Limited), and Ericsson.  All have implemented
   restart from the perspective of both a restarting and helper router.
   All but one vendor implemented both planned and unplanned restart.
   All implementations are original.  Seven successfully tested
   interoperability with Juniper.  Juniper successfully tested
   interoperability with Force10 Networks.  One vendor tested with John
   Moy's GNU Public License implementation [OSPFD].  Two vendors had not
   tested interoperability at the time of the survey.

2.1.  Implementation Differences

   The first difference was whether strict LSA checking was implemented
   and, if so, whether it was configurable.  In the context of graceful
   OSPF restart, strict LSA checking indicates whether a changed LSA
   will result in the termination of graceful restart by a helping
   router.  Four vendors made it configurable (three defaulted it to
   enabled and one to disabled), another made it a compile option
   (shipping with strict LSA checking disabled), another didn't
   implement it at all, and five implemented strict LSA checking with no
   configuration option to disable it.

Lindem                       Informational                      [Page 2]
RFC 4167      Graceful OSPF Restart Implementation Report   October 2005

   The second was whether a received grace LSA would be taken to apply

[include full document text]