LS Flooding Reduction
draft-cc-ospf-flooding-reduction-04

Document Type Active Internet-Draft (individual)
Last updated 2018-09-20
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                                            H. Chen
Internet-Draft                                                  D. Cheng
Intended status: Standards Track                     Huawei Technologies
Expires: March 24, 2019                                           M. Toy
                                                                 Verizon
                                                                 Y. Yang
                                                                     IBM
                                                      September 20, 2018

                         LS Flooding Reduction
                  draft-cc-ospf-flooding-reduction-04

Abstract

   This document proposes an approach to flood link states on a topology
   that is a subgraph of the complete topology per underline physical
   network, so that the amount of flooding traffic in the network is
   greatly reduced, and it would reduce convergence time with a more
   stable and optimized routing environment.  The approach can be
   applied to any network topology in a single area.

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 https://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 March 24, 2019.

Chen, et al.             Expires March 24, 2019                 [Page 1]
Internet-Draft             Flooding Reduction             September 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conventions Used in This Document . . . . . . . . . . . . . .   4
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Flooding Topology . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Construct Flooding Topology . . . . . . . . . . . . . . .   5
     5.2.  Backup for Flooding Topology Split  . . . . . . . . . . .   7
   6.  Extensions to OSPF  . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Extensions for Operations . . . . . . . . . . . . . . . .   8
     6.2.  Extensions for Centralized Mode . . . . . . . . . . . . .   9
       6.2.1.  Message for Flooding Topology . . . . . . . . . . . .   9
       6.2.2.  Encodings for Backup Paths  . . . . . . . . . . . . .  16
       6.2.3.  Message for Incremental Changes . . . . . . . . . . .  24
       6.2.4.  Leaders Selection . . . . . . . . . . . . . . . . . .  25
   7.  Extensions to IS-IS . . . . . . . . . . . . . . . . . . . . .  27
     7.1.  Extensions for Operations . . . . . . . . . . . . . . . .  27
     7.2.  Extensions for Centralized Mode . . . . . . . . . . . . .  27
       7.2.1.  TLV for Flooding Topology . . . . . . . . . . . . . .  27
       7.2.2.  Encodings for Backup Paths  . . . . . . . . . . . . .  28
       7.2.3.  TLVs for Incremental Changes  . . . . . . . . . . . .  29
       7.2.4.  Leaders Selection . . . . . . . . . . . . . . . . . .  30
   8.  Flooding Behavior . . . . . . . . . . . . . . . . . . . . . .  30
     8.1.  Nodes Perform Flooding Reduction without Failure  . . . .  30
       8.1.1.  Receiving an LS . . . . . . . . . . . . . . . . . . .  30
       8.1.2.  Originating an LS . . . . . . . . . . . . . . . . . .  31
       8.1.3.  Establishing Adjacencies  . . . . . . . . . . . . . .  31
     8.2.  An Exception Case . . . . . . . . . . . . . . . . . . . .  32
       8.2.1.  A Critical Failure  . . . . . . . . . . . . . . . . .  32
       8.2.2.  Multiple Failures . . . . . . . . . . . . . . . . . .  32
Show full document text