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

<bruno.decraene@orange.com> Wed, 02 November 2011 17:22 UTC

Return-Path: <bruno.decraene@orange.com>
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 1AE5C11E811C for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 10:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level:
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 uyjSFxRw6KoP for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 10:22:07 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 58A2F11E8111 for <idr@ietf.org>; Wed, 2 Nov 2011 10:22:07 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id DC02C9B0003; Wed, 2 Nov 2011 18:23:08 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id D33018F0001; Wed, 2 Nov 2011 18:23:08 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Wed, 2 Nov 2011 18:22:07 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 02 Nov 2011 18:22:05 +0100
Message-ID: <FE8F6A65A433A744964C65B6EDFDC24002951FD2@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <4EB17893.1060706@raszuk.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] draft-uttaro-idr-bgp-persistence-00
Thread-Index: AcyZgd5Z8CiW9mTGQTSshB0NSEvAUgAAMOCA
References: <4EA1F0FB.3090100@raszuk.net> <4EA487E4.2040201@raszuk.net><B17A6910EEDD1F45980687268941550FA20750@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EA84254.9000400@raszuk.net> <FE8F6A65A433A744964C65B6EDFDC24002951E94@ftrdmel0.rd.francetelecom.fr> <4EB14BDD.7040802@raszuk.net> <FE8F6A65A433A744964C65B6EDFDC24002951F8C@ftrdmel0.rd.francetelecom.fr> <4EB17893.1060706@raszuk.net>
From: bruno.decraene@orange.com
To: robert@raszuk.net
X-OriginalArrivalTime: 02 Nov 2011 17:22:07.0084 (UTC) FILETIME=[F23E5AC0:01CC9983]
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
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 17:22:08 -0000

>> Sure. But given the small number of RR boxes, and the high
requirements
>> on these boxes, it's harder to justify a two or three vendor
sourcing.
>
>I would think just the very opposite. Small number of RRs and their
high
>requirements IMHO fully justify more then one vendor sourcing.

Somehow we disagree on this. 
Regarding the small number of RR, if you need 10 RR, it's hard to go to
the buying, testing, integration and ops teams asking for a new vendor
for 5 only boxes.
Regarding dual sourcing, to keep redundancy, you would need to restrict
yourself to the smaller intersection of features and performance. This
can be limiting.


>Of course fun starts where it is hard to find such diverse RRs with all
>required feature sets.

My point. Both features and scale.

> Those concerned about such issues are looking
>actively in solving the problem fundamentally at it's roots and not
>cover it with yet another curtain.

Dual sourcing helps but does not guaranty that both RR will never fail.
You said it yourself. So this does not solve the fundamental problem.

However, again, given the low probability of double failure, it's harder
to justify work on this.

>Cheers,
>R.