RFC 8541 on Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loops

rfc-editor@rfc-editor.org Thu, 21 March 2019 06:08 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 DBF41130F2A; Wed, 20 Mar 2019 23:08:49 -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 N3j74HMaSi66; Wed, 20 Mar 2019 23:08:48 -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 34246130F29; Wed, 20 Mar 2019 23:08:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 748ABB8009D; Wed, 20 Mar 2019 23:08:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8541 on Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loops
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: <20190321060840.748ABB8009D@rfc-editor.org>
Date: Wed, 20 Mar 2019 23:08:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/m80-FXVd1pf1T-HhVGHCxOERRno>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Mar 2019 06:08:50 -0000

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

        
        RFC 8541

        Title:      Impact of Shortest Path First (SPF) Trigger 
                    and Delay Strategies on IGP Micro-loops 
        Author:     S. Litkowski,
                    B. Decraene,
                    M. Horneffer
        Status:     Informational
        Stream:     IETF
        Date:       March 2019
        Mailbox:    stephane.litkowski@orange.com, 
                    bruno.decraene@orange.com, 
                    Martin.Horneffer@telekom.de
        Pages:      15
        Characters: 35212
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-spf-uloop-pb-statement-10.txt

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

        DOI:        10.17487/RFC8541

A micro-loop is a packet-forwarding loop that may occur transiently
among two or more routers in a hop-by-hop packet-forwarding paradigm.

This document analyzes the impact of using different link state IGP
implementations in a single network with respect to micro-loops.  The
analysis is focused on the Shortest Path First (SPF) delay algorithm
but also mentions the impact of SPF trigger strategies.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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