Protocol Action: 'Making Route Flap Damping Usable' to Proposed Standard (draft-ietf-idr-rfd-usable-04.txt)

The IESG <> Mon, 10 February 2014 18:47 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E3E591A06E9; Mon, 10 Feb 2014 10:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fdPk4LA24k6v; Mon, 10 Feb 2014 10:47:45 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 5507B1A0813; Mon, 10 Feb 2014 10:47:43 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Making Route Flap Damping Usable' to Proposed Standard (draft-ietf-idr-rfd-usable-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 10 Feb 2014 10:47:43 -0800
Cc: idr mailing list <>, idr chair <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 10 Feb 2014 18:47:48 -0000

The IESG has approved the following document:
- 'Making Route Flap Damping Usable'
  (draft-ietf-idr-rfd-usable-04.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:

Technical Summary

   BGP Route Flap damping seeks to reduce the BGP 
   churn in routers. First described in operators forms 
   (RIPE, [ripe178]) and RFC2430 it was harsh 
   penalizing sites for being well-connected because 
   topology riches amplified the number of updates. 
   Therefore, many operators turned it off [ripe378].  
   However, now because new measurements f[plesser2011] 
   indicates a different suppression hold (6000) BGP 
   update rate can be reduced by 19%.  Ripe, a 
   European Operator forum, has endorse these new 
   settings [ripe580].    The Japanese operators have 
   reported their use of the new RFD and their 
   desires for implementation 

Working Group Summary

   WG Group had consensus over the last call.  During 
   the last call, a suggestion for addition features was made.  
   The chairs/WG suggested this would be a follow-on 
   draft rather than an addition to the current draft. 

Document Quality
   Existing implementation of RFD exist in Juniper and 
   Cisco.  Protocol deployments 
   [shishio-grow-isp-rfd-implement-survey] found bugs which 
   have been fixed.  The Japanese operator and RIPE operator 
   community have reviewed these documents, and the 
   Japanese operator community given the response in 

   Shepherd: Susan Hares (WG chair), 
   AD: Stewart Bryant

RFC Editor Note

The title of Table 1 
Default RFD Paramaters of Juniper and Cisco
The default RFD parameters for Cisco and Juniper provided for the information of the reader.