OSPF Out-of-band LSDB resynchronization
draft-ietf-ospf-oob-resync-01
| Document | Type |
Expired Internet-Draft
(ospf WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alex D. Zinin , Abhay Roy , Liem Nguyen | ||
| Last updated | 2001-03-06 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
OSPF is a link-state intra-domain routing protocol used in IP networks. 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. OSPF standard, however, does not allow routers to do so without actually changing the topology view of the network. This memo describes a mechanism to perform such form of out-of-band LSDB synchronization.
Authors
Alex D. Zinin
Abhay Roy
Liem Nguyen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)