RFC 3623: Graceful OSPF Restart
In plain English — editorial summary, not part of the RFC
This memo documents an enhancement to the OSPF routing protocol, whereby an OSPF router can stay on the forwarding path even as its OSPF software is restarted. This is called "graceful restart" or "non-stop forwarding". A restarting router may not be capable of adjusting its forwarding in a timely manner when the network topology changes. In order to avoid the possible resulting routing loops, the procedure in this memo automatically reverts to a normal OSPF restart when such a topology change is detected, or when one or more of the restarting router's neighbors do not support the enhancements in this memo. Proper network operation during a graceful restart makes assumptions upon the operating environment of the restarting router; these assumptions are also documented.
Document record
- Document ID
- RFC3623
- Published
- November 2003
- Authors
- J. Moy; P. Pillay-Esnault; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2740OSPF for IPv6Obsoleted
December 1999
- RFC 2676QoS Routing Mechanisms and OSPF ExtensionsCurrent
August 1999
- RFC 3630Traffic Engineering (TE) Extensions to OSPF Version 2Updated
October 2003
- RFC 3883Detecting Inactive Neighbors over OSPF Demand Circuits (DC)Current
October 2004
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 3101The OSPF Not-So-Stubby Area (NSSA) OptionCurrent
January 2003
- RFC 4167Graceful OSPF Restart Implementation ReportCurrent
October 2005
- RFC 4202Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?