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

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            J. Dong
Internet-Draft                                                  X. Zhang
Intended status: Informational                       Huawei Technologies
Expires: May 4, 2017                                               Z. Li
                                                            China Mobile
                                                        October 31, 2016

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Dong, et al.               Expires May 4, 2017                  [Page 1]
Internet-Draft     OSPF MaxAge Flush Problem Statement      October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Typical Scenarios of LSA Flushing . . . . . . . . . . . . . .   3
   3.  Consequence of LSA Flushing . . . . . . . . . . . . . . . . .   3
   4.  Requirements on Potential Solutions . . . . . . . . . . . . .   4
     4.1.  Solution for Problem Localization . . . . . . . . . . . .   4
     4.2.  Solution for Impact Mitigation  . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   In OSPF protocol [RFC2328], Link State Updates (LSAs) are exchanged
   in Link State Update (LSU) packets to achieve link state database
   (LSDB) synchronization and consistent route calculation.  OSPF
   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 in the network.  Since the MaxAge LSA may be flushed by any
   OSPF router, usually it would take a long time for troubleshooting
   and could cause huge damage to both the network provider and its
   customers.

Dong, et al.               Expires May 4, 2017                  [Page 2]
Internet-Draft     OSPF MaxAge Flush Problem Statement      October 2016
Show full document text