Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs

Jakob Heitz <jakob.heitz@ericsson.com> Thu, 10 November 2011 18:54 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 01AF021F8B7B for <sidr@ietfa.amsl.com>; Thu, 10 Nov 2011 10:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.103
X-Spam-Level:
X-Spam-Status: No, score=-6.103 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 upBALR1a5qvk for <sidr@ietfa.amsl.com>; Thu, 10 Nov 2011 10:54:33 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6128D21F8B7A for <sidr@ietf.org>; Thu, 10 Nov 2011 10:54:33 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAAIsOHV008496; Thu, 10 Nov 2011 12:54:29 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.52]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 10 Nov 2011 13:54:24 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Eric Osterweil <eosterweil@verisign.com>, Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 10 Nov 2011 13:54:23 -0500
Thread-Topic: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
Thread-Index: Acyf2TAtR05Gca8ZRWqamp7nyJ4MrQAAKtLw
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391A44964302@EUSAACMS0701.eamcs.ericsson.se>
References: <CAL9jLaa+L-C7+Gp54BpM8FjAj+EFMabwQB9SsPW0N4QnFEfVGw@mail.gmail.com> <4297E946-980B-43C5-A01F-1F49706BC51E@tcb.net> <p06240808cad5c4d268eb@193.0.26.186> <0364A2AA-0CCF-408A-B5CB-42D7AFCAFB36@tcb.net> <p06240804cad81a9e4485@193.0.26.186> <54CED243-BDDD-45B9-AC5C-C6A97692FBF2@verisign.com> <CAL9jLaZ1GoN-iG4SWocVVhTKp5ppPOgHWcjh1J30GPnfwBPf+A@mail.gmail.com> <D7A0423E5E193F40BE6E94126930C49308E9E3555C@MBCLUSTER.xchange.nist.gov> <92AA1C8B-7CDB-406E-AA83-7C1BCD83CB69@ericsson.com> <D7A0423E5E193F40BE6E94126930C49308EAF8EF67@MBCLUSTER.xchange.nist.gov> <32DF728C-A96A-435D-A54E-7626C2577F04@verisign.com> <CAL9jLabdtEMJKy1eBi8JGxJDWQc2HngHWSHiuRRKc5v-=Ddk2g@mail.gmail.com> <C6A67919-B4AA-4664-A8DC-5503484B2BA8@verisign.com>
In-Reply-To: <C6A67919-B4AA-4664-A8DC-5503484B2BA8@verisign.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 wg list <sidr@ietf.org>
Subject: Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
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, 10 Nov 2011 18:54:34 -0000

Don't forget, BGPSEC sends one prefix per update.
Current traffic is 2 to 3 prefixes per update.

> -----Original Message-----
> From: sidr-bounces@ietf.org [mailto:sidr-bounces@ietf.org] On Behalf
> Of Eric Osterweil
> Sent: Thursday, November 10, 2011 10:46 AM
> To: Christopher Morrow
> Cc: Sriram, Kotikalapudi; sidr wg list
> Subject: Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
> 
> 
> On Nov 10, 2011, at 1:41 PM, Christopher Morrow wrote:
> 
> > On Wed, Nov 9, 2011 at 3:37 PM, Eric Osterweil
> <eosterweil@verisign.com> wrote:
> >> Hey Sriram, Russ, and Jakob,
> >>
> >> Thanks for the #s.  I think I get the general notion that adding
> n updates per day per prefix equals (n * #prefixes)/1. :)  I guess
> my question was kinda vague, sorry.  Upon reexamination, I see that
> I said "overhead" without being specific.  Since we can use the
> updates that are generated today to measure how much (for example)
> bandwidth is already needed, can we calculate how much extra
> bandwidth universal deployment would mean?  Also, perhaps this would
> be most informative in the form of a ratio (i.e. a factor of $x$
> increase).  That way, when people look at events like the one that
> the "General Internet Instability" thread that just happened on
> NANOG refer to, they can gauge the update amplification that was
> seen against what _would_ be seen given bgpsec.  I think this
> actually kind of came up on nanog, so it seems like maybe it would
> be a relevant thing to look at here?
> >
> > is the 'bandwidth' of the bgp protocol in the wire an actual
> concern?
> > (at some point the discussion point came up ~1yr or more ago, but
> was
> > discarded as not relevant given circuit sizes and bandwidth from
> link
> > -> RP/RE/etc, so I'm genuinely curious about this)
> 
> I think it is just a concrete way to relate the amount of data being
> consumed today, to what may be needed tomorrow.  It isn't so much
> that 1 byte = good and 10 bytes = bad.  More that in trying to
> quantitative compare two behaviors, finding a common reference point
> seems like a good start, imho.  I think a meaningful ratio is more
> useful, but it just needs something to compare.
> 
> Eric
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr