IS-IS Flooding Parameters advertisement
draft-decraene-lsr-isis-flooding-speed-04

Document Type Active Internet-Draft (individual)
Last updated 2020-06-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                                        B. Decraene
Internet-Draft                                                    Orange
Intended status: Standards Track                               C. Bowers
Expires: December 12, 2020                                     Jayesh. J
                                                  Juniper Networks, Inc.
                                                                   T. Li
                                                         Arista Networks
                                                         G. Van de Velde
                                                                   Nokia
                                                           June 10, 2020

                IS-IS Flooding Parameters advertisement
               draft-decraene-lsr-isis-flooding-speed-04

Abstract

   This document proposes a mechanism that can be used to increase the
   speed at which link state information is exchanged between two
   routers when multiple LSPs need to be flooded, such as in case of a
   node failure.  It also reduces the likelihood of overloading the
   router receiving the LSPs, causing LSPs losses and delayed
   retransmission.  This document defines a new TLV to be advertised in
   SNP and/or Hello messages.  This TLV may carry a set of parameters
   indicating the performance capacity to receive LSPs: the number of
   LSPs which can the received back to back, the minimum delay between
   further two consecutive LSPs and the minimum delay before
   retransmission of an LSP.

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 December 12, 2020.

Decraene, et al.        Expires December 12, 2020               [Page 1]
Internet-Draft   IS-IS Flooding Parameters advertisement       June 2020

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Flooding Parameters TLV . . . . . . . . . . . . . . . . . . .   4
     3.1.  InterfaceLSPReceiveWindow sub-TLV . . . . . . . . . . . .   5
     3.2.  minimumInterfaceLSPTransmissionInterval sub-TLV . . . . .   5
     3.3.  minimumLSPTransmissionInterval sub-TLV  . . . . . . . . .   5
   4.  Flow control  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Operation on a point to point interface . . . . . . . . .   6
     4.2.  Faster acknowledgments of LSPs  . . . . . . . . . . . . .   7
     4.3.  Operation on a LAN interface  . . . . . . . . . . . . . .   7
   5.  Congestion control  . . . . . . . . . . . . . . . . . . . . .   8
   6.  Faster loss detection and recovery  . . . . . . . . . . . . .   9
   7.  Interaction with other LSP rate limiting mechanisms . . . . .  10
   8.  Determining values to be advertised in the Flooding
       Parameters TLV  . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     12.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Changes / Author Notes . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   IGP flooding is paramount for Link State IGP as routing computations
   assume that the Link State DataBases (LSDBs) are always in sync
Show full document text