Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
Christopher Morrow <morrowc.lists@gmail.com> Fri, 11 November 2011 13:19 UTC
Return-Path: <christopher.morrow@gmail.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 E3F1521F8906 for <sidr@ietfa.amsl.com>; Fri, 11 Nov 2011 05:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.423
X-Spam-Level:
X-Spam-Status: No, score=-103.423 tagged_above=-999 required=5 tests=[AWL=-0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 3XViagFMA9ft for <sidr@ietfa.amsl.com>; Fri, 11 Nov 2011 05:19:41 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6EB21F8888 for <sidr@ietf.org>; Fri, 11 Nov 2011 05:19:41 -0800 (PST)
Received: by ywt34 with SMTP id 34so2298261ywt.31 for <sidr@ietf.org>; Fri, 11 Nov 2011 05:19:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MqavDOL46myB6GdpXzY2AQDSYtwmDTe6y01Jeay37HQ=; b=E5WtrLuImjBeI/IxXFdkP6+eqQ/8BAO0vRjVWeF8pbWIZqx/e89Gia/r5UKprlEztn e7gBxwv/KSiKepiq2hYnrBKCpvSOLlRYQ7pibIgDyN3BowFney8loBe8BXiAvrXq0n5J P1ROHxtjWxxMcCpQwt6IbF75uSI27QMqZQUJY=
MIME-Version: 1.0
Received: by 10.50.184.202 with SMTP id ew10mr12344671igc.48.1321017580783; Fri, 11 Nov 2011 05:19:40 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.231.202.142 with HTTP; Fri, 11 Nov 2011 05:19:40 -0800 (PST)
In-Reply-To: <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> <7309FCBCAE981B43ABBE69B31C8D21391A44964302@EUSAACMS0701.eamcs.ericsson.se>
Date: Fri, 11 Nov 2011 08:19:40 -0500
X-Google-Sender-Auth: H-D5PEwVflKlKEthm2aNZGhkmDU
Message-ID: <CAL9jLaapE2fYHAGWvNLNVovUCk8KscfO=cqg=R2xRcMrJ_J=Hw@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Fri, 11 Nov 2011 13:19:42 -0000
On Thu, Nov 10, 2011 at 1:54 PM, Jakob Heitz <jakob.heitz@ericsson.com> wrote: > Don't forget, BGPSEC sends one prefix per update. > Current traffic is 2 to 3 prefixes per update. There's actually some research on this, I recall the number 'globally' as 1.2 avg packing... but internally, that may be different, of course. -chris >> -----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 >
- [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Shane Amante
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs George, Wes
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Stephen Kent
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Stephen Kent
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Eric Osterweil
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Sriram, Kotikalapudi
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Russ White
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Russ White
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Jakob Heitz
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Sriram, Kotikalapudi
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Eric Osterweil
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Eric Osterweil
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Jakob Heitz
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Brian Dickson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Sriram, Kotikalapudi
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Danny McPherson
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Eric Osterweil
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Brian Dickson
- [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Chris Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Sriram, Kotikalapudi
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Warren Kumari
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Keyur Patel (keyupate)
- [sidr] Another potential DOS attack on RP softwar… Demian Rosenkranz
- Re: [sidr] Another potential DOS attack on RP sof… Tim Bruijnzeels
- Re: [sidr] Another potential DOS attack on RP sof… Jared Mauch
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs George, Wes
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Warren Kumari
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs George, Wes
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs George, Wes
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Stephen Kent
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Roque Gagliano (rogaglia)
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Roque Gagliano (rogaglia)
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs George, Wes
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Christopher Morrow
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Randy Bush
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Montgomery, Douglas
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Montgomery, Douglas
- Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs Sandra Murphy