OSPF LSA Flushing Problem Statement
draft-dong-ospf-maxage-flush-problem-statement-01

Document Type Expired Internet-Draft (individual)
Last updated 2017-05-04 (latest revision 2016-10-31)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
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-dong-ospf-maxage-flush-problem-statement-01.txt

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 (jie.dong@huawei.com)
Xudong Zhang (zhangxudong@huawei.com)
Zhenqiang Li (li_zhenqiang@hotmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)