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

The IESG <iesg-secretary@ietf.org> Mon, 10 February 2014 18:47 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3E591A06E9; Mon, 10 Feb 2014 10:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 fdPk4LA24k6v; Mon, 10 Feb 2014 10:47:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (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 <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
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: <20140210184743.635.23093.idtracker@ietfa.amsl.com>
Date: Mon, 10 Feb 2014 10:47:43 -0800
Cc: idr mailing list <idr@ietf.org>, idr chair <idr-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=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:
http://datatracker.ietf.org/doc/draft-ietf-idr-rfd-usable/




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 
   [shishio-grow-isp-rfd-implement-survey]. 


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 
   [shishio-grow-isp-rfd-implement-survey]. 
 
Personnel

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

RFC Editor Note

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