IETF Logo Mail Archive

Re: [sidr] Burstiness of BGP updates

Jakob Heitz <jakob.heitz@ericsson.com> Wed, 16 November 2011 03:40 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 323931F0CA9 for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level:
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248, 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 73aQpZmk5av8 for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:40:18 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 93C1A1F0C9E for <sidr@ietf.org>; Tue, 15 Nov 2011 19:40:18 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAG3cZQK023302; Tue, 15 Nov 2011 21:38:36 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 15 Nov 2011 22:38:29 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Russ White <russw@riw.us>
Date: Tue, 15 Nov 2011 22:38:27 -0500
Thread-Topic: [sidr] Burstiness of BGP updates
Thread-Index: AcykEGqCWd1q2OPJTTWI4m04Lo8GEwAABryg
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391A45A20633@EUSAACMS0701.eamcs.ericsson.se>
References: <D7A0423E5E193F40BE6E94126930C49308E9E35567@MBCLUSTER.xchange.nist.gov> <7309FCBCAE981B43ABBE69B31C8D21391A45A1F85D@EUSAACMS0701.eamcs.ericsson.se> <m2fwhqeq5i.wl%randy@psg.com> <CCE759E6-BEA6-433B-957A-6559C67BAD52@ericsson.com> <DCC302FAA9FE5F4BBA4DCAD4656937791452387941@PRVPEXVS03.corp.twcable.com> <7309FCBCAE981B43ABBE69B31C8D21391A45A1FE9F@EUSAACMS0701.eamcs.ericsson.se> <DCC302FAA9FE5F4BBA4DCAD4656937791452387978@PRVPEXVS03.corp.twcable.com> <7309FCBCAE981B43ABBE69B31C8D21391A45A1FEC8@EUSAACMS0701.eamcs.ericsson.se> <4EC3125D.4000309@riw.us> <7309FCBCAE981B43ABBE69B31C8D21391A45A2061F@EUSAACMS0701.eamcs.ericsson.se> <4EC329C6.4090600@riw.us> <7309FCBCAE981B43ABBE69B31C8D21391A45A2062E@EUSAACMS0701.eamcs.ericsson.se> <4EC32EBE.6030106@riw.us>
In-Reply-To: <4EC32EBE.6030106@riw.us>
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: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] Burstiness of BGP updates
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: Wed, 16 Nov 2011 03:40:19 -0000

> -----Original Message-----
> From: Russ White [mailto:russw@riw.us]
> Sent: Tuesday, November 15, 2011 7:32 PM
> To: Jakob Heitz
> Cc: sidr@ietf.org
> Subject: Re: [sidr] Burstiness of BGP updates
> 
> 
> > The only utility I can see is in protecting reachability.
> > The only problem I can imagine with installing an unsigned route
> is
> > that the destination becomes unreachable. If it was unreachable to
> > begin with, no harm is done.
> 
> When you're protecting reachability, what are you protecting?
> Whether or not someone can reach something. I assume that the
> "something" you're trying to protect reachability to would/must
> include things where you enter your password.
> 
> Hence, I look at this entire problem a little differently than
> simply trying to enforce a small subset of policies, or as a
> theoretical exercise... If we can't prevent real world consequences
> with this work, then --why are we doing it?

We are doing it to protect reachability.

We are not protecting your password in clear text on the internet.

--
Jakob Heitz. x25475. 510-566-2901

v2.23.0 | Report a Bug | By Email