RFC 4167: Graceful OSPF Restart Implementation Report
In plain English — editorial summary, not part of the RFC
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. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4167
- Published
- October 2005
- Authors
- A. Lindem
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 4202Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4203OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4222Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion AvoidanceUpdated
October 2005
- RFC 3883Detecting Inactive Neighbors over OSPF Demand Circuits (DC)Current
October 2004
- RFC 4552Authentication/Confidentiality for OSPFv3Current
June 2006
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 3623Graceful OSPF RestartCurrent
November 2003
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?