RFC 8405 on Shortest Path First (SPF) Back-Off Delay Algorithm for Link-State IGPs

rfc-editor@rfc-editor.org Tue, 26 June 2018 05:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6CA130EC6; Mon, 25 Jun 2018 22:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uiB66SDlEqtr; Mon, 25 Jun 2018 22:43:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B2CD130E66; Mon, 25 Jun 2018 22:43:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 32ADDB81227; Mon, 25 Jun 2018 22:43:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0MDUgb24gU2hvcnRlc3QgUGF0aCBGaXJzdCAoU1BGKSBCYWNrLU9mZiBEZWxheSBBbGdvcml0aG0gZm9yIExpbmstU3RhdGUgSUdQcw==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180626054336.32ADDB81227@rfc-editor.org>
Date: Mon, 25 Jun 2018 22:43:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/QfKd12N1nco8aVZ7Q7U9rRu9b2s>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 05:43:43 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8405

        Title:      Shortest Path First (SPF) Back-Off Delay 
                    Algorithm for Link-State IGPs 
        Author:     B. Decraene,
                    S. Litkowski,
                    H. Gredler,
                    A. Lindem,
                    P. Francois,
                    C. Bowers
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    bruno.decraene@orange.com, 
                    stephane.litkowski@orange.com, 
                    hannes@rtbrick.com,
                    acee@cisco.com, 
                    pfrpfr@gmail.com,
                    cbowers@juniper.net
        Pages:      14
        Characters: 28446
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-backoff-algo-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8405

        DOI:        10.17487/RFC8405

This document defines a standard algorithm to temporarily postpone or
"back off" link-state IGP Shortest Path First (SPF) computations.
This reduces the computational load and churn on IGP nodes when
multiple temporally close network events trigger multiple SPF
computations.

Having one standard algorithm improves interoperability by reducing
the probability and/or duration of transient forwarding loops during
the IGP convergence when the IGP reacts to multiple temporally close
IGP events.

This document is a product of the Routing Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC