Re: [sidr] the need for speed

Eric Osterweil <eosterweil@verisign.com> Thu, 20 December 2012 19:02 UTC

Return-Path: <eosterweil@verisign.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4524A21F84F9 for <sidr@ietfa.amsl.com>; Thu, 20 Dec 2012 11:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.435
X-Spam-Level:
X-Spam-Status: No, score=-4.435 tagged_above=-999 required=5 tests=[AWL=-0.836, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uMdGyEify-5L for <sidr@ietfa.amsl.com>; Thu, 20 Dec 2012 11:02:14 -0800 (PST)
Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id DD23A21F84F5 for <sidr@ietf.org>; Thu, 20 Dec 2012 11:02:12 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUNNgrQX9zBRMNh3rBdM2hSAaBS6EWCo2@postini.com; Thu, 20 Dec 2012 11:02:14 PST
Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id qBKJ22ll026343; Thu, 20 Dec 2012 14:02:02 -0500
Received: from dul1eosterwe-m1.vcorp.ad.vrsn.com ([10.88.29.242]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 20 Dec 2012 14:02:01 -0500
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Eric Osterweil <eosterweil@verisign.com>
In-Reply-To: <931B485F-D061-4C05-8C95-7920995A85CE@verisign.com>
Date: Thu, 20 Dec 2012 14:02:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <536553C9-EADA-4D69-B8C0-38A81BA2A1A2@verisign.com>
References: <m2vcbzqgzx.wl%randy@psg.com> <CAHUKT2CLZsUakDYB=PpyR9zArSxN_KhKC_UFZ5C+=+yUs2NvFA@mail.gmail.com> <CAL9jLaZjPyuFtE8ZQU88iW5p2H8NWAfmzX0z5u7q7wawvem9ZA@mail.gmail.com> <487F9F23-F609-48A2-BE67-6361291BDFCF@ripe.net> <50D34405.8080807@lacnic.net> <22421E49-82E5-4BEE-A3E3-BEE6C8BFEA3C@verisign.com> <50D35892.5080402@lacnic.net> <931B485F-D061-4C05-8C95-7920995A85CE@verisign.com>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1085)
X-OriginalArrivalTime: 20 Dec 2012 19:02:01.0641 (UTC) FILETIME=[7E4BA990:01CDDEE4]
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] the need for speed
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 19:02:45 -0000

On Dec 20, 2012, at 1:53 PM, Eric Osterweil wrote:

> 
> On Dec 20, 2012, at 1:27 PM, Arturo Servin wrote:
> 
>> That's is not true. We have seen some challenges in the current
>> architecture since long ago and some are trying to address them:
>> 
>> https://datatracker.ietf.org/doc/draft-rogaglia-sidr-multiple-publication-points/
>> 
>> https://datatracker.ietf.org/doc/draft-tbruijnzeels-sidr-delta-protocol/
>> 
>> https://datatracker.ietf.org/doc/draft-tbruijnzeels-sidr-validation-local-cache/
> 
> I totally appreciate the efforts behind these design enhancements, and I am trying impugn the work that has clearly gone into them (or the people who did the work).  However, my concern is that without requirements analysis around the core of the architecture that these enhancements speak to, how do you know that you're not just building on a shaky/unstable foundation, or trying to overcome fundamental flaws in its architecture?  We haven't taken the time to outline what bgpsec needs to do in order for us to be protected by it.  Therefore, we can't describe when we've met our goals.

Err... *_not_ trying to impugn sorry. :)

Eric