RFC 4811: OSPF Out-of-Band Link State Database (LSDB) Resynchronization
In plain English — editorial summary, not part of the RFC
OSPF is a link-state intra-domain routing protocol used in IP networks. Link State Database (LSDB) synchronization in OSPF is achieved via two methods -- initial LSDB synchronization when an OSPF router has just been connected to the network and asynchronous flooding that ensures continuous LSDB synchronization in the presence of topology changes after the initial procedure was completed. It may sometime be necessary for OSPF routers to resynchronize their LSDBs. The OSPF standard, however, does not allow routers to do so without actually changing the topology view of the network. This memo describes a vendor-specific mechanism to perform such a form of out-of-band LSDB synchronization. The mechanism described in this document was proposed before Graceful OSPF Restart, as described in RFC 3623, came into existence. It is implemented/supported by at least one major vendor and is currently deployed in the field. The purpose of this document is to capture the details of this mechanism for public use. This mechanism is not an IETF standard. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4811
- Published
- March 2007
- Authors
- L. Nguyen; A. Roy; A. Zinin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 9454
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4812OSPF Restart SignalingCurrent
March 2007
- RFC 4813OSPF Link-Local SignalingObsoleted
March 2007
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- RFC 4915Multi-Topology (MT) Routing in OSPFCurrent
June 2007
- RFC 4940IANA Considerations for OSPFCurrent
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4552Authentication/Confidentiality for OSPFv3Current
June 2006
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?