[Idr] RFC 7196 on Making Route Flap Damping Usable

rfc-editor@rfc-editor.org Fri, 16 May 2014 22:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15E51A0152; Fri, 16 May 2014 15:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 FReIfLsWNRjt; Fri, 16 May 2014 15:03:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id D5B3C1A00E5; Fri, 16 May 2014 15:03:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id ECAF118000D; Fri, 16 May 2014 15:02:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140516220224.ECAF118000D@rfc-editor.org>
Date: Fri, 16 May 2014 15:02:24 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/gFbwZMJBq1K21gWKYB49Vi0crU0
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
Subject: [Idr] RFC 7196 on Making Route Flap Damping Usable
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2014 22:03:37 -0000

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

        
        RFC 7196

        Title:      Making Route Flap Damping Usable 
        Author:     C. Pelsser, R. Bush,
                    K. Patel, P. Mohapatra,
                    O. Maennel
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2014
        Mailbox:    cristel@iij.ad.jp, 
                    randy@psg.com, 
                    keyupate@cisco.com,
                    mpradosh@yahoo.com, 
                    o@maennel.net
        Pages:      8
        Characters: 15202
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-rfd-usable-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7196.txt

Route Flap Damping (RFD) was first proposed to reduce BGP churn in
routers.  Unfortunately, RFD was found to severely penalize sites for
being well connected because topological richness amplifies the
number of update messages exchanged.  Many operators have turned RFD
off.  Based on experimental measurement, this document recommends
adjusting a few RFD algorithmic constants and limits in order to
reduce the high risks with RFD.  The result is damping a non-trivial
amount of long-term churn without penalizing well-behaved prefixes'
normal convergence process.

This document is a product of the Inter-Domain Routing 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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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