OSPF LSA Flushing Problem Statement
draft-dong-ospf-maxage-flush-problem-statement-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jie Dong , Xudong Zhang , Zhenqiang Li | ||
| Last updated | 2017-05-04 (Latest revision 2016-10-31) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 is available in these formats:
Abstract
In OSPF protocol, Link State Advertisements (LSAs) are exchanged in Link State Update (LSU) packets to achieve link state database (LSDB) synchronization and consistent route calculation. OSPF protocol specifies several scenarios in which an LSA is flushed with the LS age field set to MaxAge. In some cases, the flushing of MaxAge LSAs may cause flooding storm of OSPF packets and severely impact the services provided by the network. This document describes the problem of OSPF LSA flushing, and ask for solutions to solve this problem.
Authors
Jie Dong
Xudong Zhang
Zhenqiang Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)