Re: [sidr] BGPSec scaling (was RE: beacons and bgpsec)

Jakob Heitz <jakob.heitz@ericsson.com> Mon, 12 September 2011 14:42 UTC

Return-Path: <jakob.heitz@ericsson.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 C139821F8B7C for <sidr@ietfa.amsl.com>; Mon, 12 Sep 2011 07:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level:
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EoIHgTl9UKlL for <sidr@ietfa.amsl.com>; Mon, 12 Sep 2011 07:42:51 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2F02421F8B7A for <sidr@ietf.org>; Mon, 12 Sep 2011 07:42:51 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p8CEip6o011966; Mon, 12 Sep 2011 09:44:53 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.158]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 12 Sep 2011 10:44:48 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Randy Bush <randy@psg.com>
Date: Mon, 12 Sep 2011 10:44:53 -0400
Thread-Topic: [sidr] BGPSec scaling (was RE: beacons and bgpsec)
Thread-Index: AcxxWoSMnyGvdWW8RSeU5//2RG6Bew==
Message-ID: <5696904F-7C8E-460B-8533-F5FDBDC06B4D@ericsson.com>
References: <A37CADA4-F16D-4C01-8D9C-D01001C4EFE4@tcb.net> <21C19DA8-7BF3-4832-8C13-C9A45FE026FB@algebras.org> <87D9E106-2A37-4E1E-8C69-7084C199A3FE@tcb.net> <331AEFBD-6AE5-469E-A11E-E672DC61DCDC@pobox.com> <B92913D1-AB82-4D9F-B8A9-F8F4F99713D6@tcb.net> <p06240803ca685bff5443@128.89.89.43> <D6D12861-412E-4A65-B626-B627449981B8@tcb.net> <34E4F50CAFA10349A41E0756550084FB0C2ED5A4@PRVPEXVS04.corp.twcable.com> <7B321CF0-ABE6-4FCD-B755-8099BB63399A@rob.sh> <5E9BE75F-C0A6-4B48-B15F-7E0B80EFE981@ericsson.com> <m2ipp4qxs5.wl%randy@psg.com> <34E4F50CAFA10349A41E0756550084FB0E0D5BDC@PRVPEXVS04.corp.twcable.com> <D4059E53-6EEC-4F66-9E1E-B96675182F22@rob.sh> <m2wrdhvjpe.wl%randy@psg.com> <4E6A2CD0.1010305@riw.us> <m2pqj9vgc8.wl%randy@psg.com> <CAL9jLaYoU-f_6CmmrLkSFyO1oHEZeKeYL8pF+pjF+3DXd0myTg@mail.gmail.com> <m21uvml1yy.wl%randy@psg.com> <m2hb4hkezc.wl%randy@psg.com>
In-Reply-To: <m2hb4hkezc.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] BGPSec scaling (was RE: beacons and bgpsec)
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: Mon, 12 Sep 2011 14:42:51 -0000

10u to validate an incoming prefix.
How long to validate an incoming path?
How long to generate/sign an outgoing path?
To one neighbor? To all neighbors?

--
Jakob Heitz.


On Sep 12, 2011, at 7:33 AM, "Randy Bush" <randy@psg.com> wrote:

>> Q2: Is it well rooted in the historical measurement data for its
>> projections into the future?
>> 
>> Q3: Are additional assumptions made for projecting into the future
>> reasonable? In this instance, are the assumptions regarding the BGPSEC
>> take rate reasonable?
> 
> as humans and as engineers, we are well known for poor predictions of
> the future.  we each have a model and they differ widely.  and if you
> extrapolate, especially with a complex model, i become very suspicious
> of any and all of your data.
> 
> this is why the data i give on rpki-rtr is what we have measured and
> only what we have measured, 10u on a gsr/xr to validate one incoming
> prefix, 4-7 seconds on gsr/xr, 7206/ios, and juniper m7 and m240 to load
> 360k roas built to map the current route views table.  this is from a
> freebsd 8.2 server over both local gige and wan with 63ms rtt, seems to
> make little difference.  we have not yet been able to make finer grained
> measurements,
> 
> you are welcome to extrapolate all you wish.  i do not wish to.  i have
> no idea what the timing would be with twice that many roas.  i would
> guess it would take more time, but i really have no idea, it could be a
> flat constant!
> 
> randy