Re: [Idr] draft-uttaro-idr-bgp-persistence-00

Robert Raszuk <robert@raszuk.net> Wed, 02 November 2011 13:55 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C30421F8BEF for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 06:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7xZon27cDBL for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 06:55:56 -0700 (PDT)
Received: from mail37.opentransfer.com (mail37.opentransfer.com [76.162.254.37]) by ietfa.amsl.com (Postfix) with SMTP id 6B07021F8BE8 for <idr@ietf.org>; Wed, 2 Nov 2011 06:55:56 -0700 (PDT)
Received: (qmail 23767 invoked by uid 399); 2 Nov 2011 13:55:55 -0000
Received: from unknown (HELO ?192.168.1.52?) (83.31.220.67) by mail37.opentransfer.com with SMTP; 2 Nov 2011 13:55:55 -0000
Message-ID: <4EB14BDD.7040802@raszuk.net>
Date: Wed, 02 Nov 2011 14:55:41 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: bruno.decraene@orange.com
References: <4EA1F0FB.3090100@raszuk.net> <4EA487E4.2040201@raszuk.net><B17A6910EEDD1F45980687268941550FA20750@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EA84254.9000400@raszuk.net> <FE8F6A65A433A744964C65B6EDFDC24002951E94@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <FE8F6A65A433A744964C65B6EDFDC24002951E94@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org, ju1738@att.com
Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
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: Wed, 02 Nov 2011 13:55:57 -0000

Bruno,

> The low chance / probability of the failure of both RR planes is indeed
> a good point. I can also agree that this is expected to be low. I
> disagree that it never happens. E.g. with current BGP error handling,
> the same BGP attribute in "error" would cause both iBGP plane to go
> down. Hopefully work is being done to improve this. But I would not bet
> that this will cover all future cases.

If trigger is due to malformed update why are we so concerned about RRs? 
Wouldn't equally susceptible be also PEs/ASBRs ?

And the cure that those is GR, not persistence ;).

> In such catastrophic cases, some routing is better than no routing.

I don't know about that.

> On a side note, considering that the RR and hence their failure are
> independent and therefore will quite never fail at the same time, is
> questionable. To start with, they process they mostly process the same
> input (BGP updates) and are part of the same network.

I don't think I used the term "never". But with dual or triple vendor 
control plane the probability of RR network wide outage drops 
significantly lower.

Cheers,
R.