RFC 8333 on Micro-loop Prevention by Introducing a Local Convergence Delay

rfc-editor@rfc-editor.org Wed, 28 March 2018 23:28 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 8314412895E; Wed, 28 Mar 2018 16:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 oaY8VZtIvdWL; Wed, 28 Mar 2018 16:28:18 -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 ED7E1126CC4; Wed, 28 Mar 2018 16:28:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 44965B812F7; Wed, 28 Mar 2018 16:27:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDgzMzMgb24gTWljcm8tbG9vcCBQcmV2ZW50aW9uIGJ5IEludHJvZHVjaW5nIGEgTG9jYWwgQ29udmVyZ2VuY2UgRGVsYXk=?=
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: <20180328232758.44965B812F7@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:27:58 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/zRvLFgI_65FUbsgCiBB9-dlxCxg>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Mar 2018 23:28:19 -0000

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

        
        RFC 8333

        Title:      Micro-loop Prevention by Introducing a 
                    Local Convergence Delay 
        Author:     S. Litkowski,
                    B. Decraene,
                    C. Filsfils,
                    P. Francois
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    stephane.litkowski@orange.com, 
                    bruno.decraene@orange.com, 
                    cfilsfil@cisco.com,
                    pfrpfr@gmail.com
        Pages:      26
        Characters: 63119
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-uloop-delay-09.txt

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

        DOI:        10.17487/RFC8333

This document describes a mechanism for link-state routing protocols
that prevents local transient forwarding loops in case of link
failure.  This mechanism proposes a two-step convergence by
introducing a delay between the convergence of the node adjacent to
the topology change and the network-wide convergence.

Because this mechanism delays the IGP convergence, it may only be
used for planned maintenance or when Fast Reroute (FRR) protects the
traffic during the time between the link failure and the IGP
convergence.

The mechanism is limited to the link-down event in order to keep the
mechanism simple.

Simulations using real network topologies have been performed and
show that local loops are a significant portion (>50%) of the total
forwarding loops.

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