OSPF Out-of-Band Link State Database Resynchronization
RFC 4811, “OSPF Out-of-Band Link State Database Resynchronization”, is an Informational document published in March 2007 by L. Nguyen, A. Roy, A. Zinin. It has since been updated by RFC 9454. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4811 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4810 Long-Term Archive Service Requirements
- RFC 4812 OSPF Restart Signaling
- RFC 4809 Requirements for an IPsec Certificate Management Profile
- RFC 4813 OSPF Link-Local Signaling
- RFC 4808 Key Change Strategies for TCP-MD5
- RFC 4814 Hash and Stuffing: Overlooked Factors in Network Device Benchmarking
- RFC 4807 IPsec Security Policy Database Configuration MIB
- RFC 4815 RObust Header Compression : Corrections and Clarifications to RFC 3095