Re: [Idr] draft-jakma-mrai-dep-00 (fwd)

Jeffrey Haas <jhaas@pfrc.org> Wed, 26 November 2008 15:23 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5975828C12D; Wed, 26 Nov 2008 07:23:29 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADD393A69F2 for <idr@core3.amsl.com>; Wed, 26 Nov 2008 07:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22nI6XuZD2EM for <idr@core3.amsl.com>; Wed, 26 Nov 2008 07:23:28 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 042E628C12E for <idr@ietf.org>; Wed, 26 Nov 2008 07:23:27 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id B3FC2244190; Wed, 26 Nov 2008 15:23:25 +0000 (UTC)
Date: Wed, 26 Nov 2008 10:23:25 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Pedro Marques <roque@juniper.net>
Message-ID: <20081126152325.GA19421@slice>
References: <200811252329.mAPNTTM46473@magenta.juniper.net> <20081126001652.GB12535@slice> <200811260140.mAQ1eXM09692@magenta.juniper.net> <20081126042010.GA14608@slice> <2815BD5B-2006-4074-9613-8F5D580E983E@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <2815BD5B-2006-4074-9613-8F5D580E983E@juniper.net>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org
Subject: Re: [Idr] draft-jakma-mrai-dep-00 (fwd)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Tue, Nov 25, 2008 at 10:07:33PM -0800, Pedro Marques wrote:
> The typical example being an SP that acquires a newly preferred peer route 
> which them causes it to send withdrawals to other peers (reachable converts 
> to unreachable).
>
> My understanding is that this behavior has been well document in practical 
> observations of BGP convergence.

That was the example I needed.

Part of the reason why I suggested separate timers is that the above
scenario is within the scope of iBGP convergence.  This means that
within the expcted iBGP MRAI you should be able to safely send
unreachables quicker to your eBGP peers than you'd otherwise be able to
if you were waiting on the (typically longer) eBGP MRAI.

I'd still recommend different timers but I think I've just been
convinced that the withdraw timer should have a lower bound of the iBGP
MRAI value.

> In general my recommendation for MRAI values would be 0 for eBGP and 0 for 
> iBGP. As the draft correctly explains calculating a value that best fits 
> the network is a very tricky business.

And, as long as you're not worrying about route flap dampening, TCP
queue lengths and processing delays is often enough to squelch a lot of
the updates in networks that are "busy enough".

-- Jeff
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr