OSPF Incremental Link State Database Synchronization
draft-retana-ospf-ils-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Alvaro Retana , Acee Lindem | ||
| Last updated | 2013-01-14 (Latest revision 2012-07-13) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-retana-ospf-ils-01.txt
https://www.ietf.org/archive/id/draft-retana-ospf-ils-01.txt
Abstract
The ability of OSPF to transport non-routing information to be used by other applications was defined by the Opaque LSA Option. In order to not impact the convergence of routing information, this document describes a simple process to incrementally synchronize the routing and non-routing information residing in an OSPF link-state database.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)