Re: [sidr] Burstiness of BGP updates

Russ White <russw@riw.us> Wed, 16 November 2011 03:52 UTC

Return-Path: <russw@riw.us>
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 E242D11E817B for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599]
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 P2yOKt5G71L5 for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:52:41 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id 5825911E8172 for <sidr@ietf.org>; Tue, 15 Nov 2011 19:52:41 -0800 (PST)
Received: from [107.17.45.77] (port=50371) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RQWY9-0000Wu-EL; Tue, 15 Nov 2011 22:52:37 -0500
Message-ID: <4EC3337D.3050704@riw.us>
Date: Tue, 15 Nov 2011 22:52:29 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
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> <7309FCBCAE981B43ABBE69B31C8D21391A45A20633@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391A45A20633@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
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:52:42 -0000

> We are doing it to protect reachability.

Again:

>> 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 not protecting your password in clear text on the internet.

I would challenge you to find any statement of mine where I said this
work is about "protecting your password in clear text on the internet."

"The Internet" is not an abstract collection of "things." It is a set of
reachable destinations. People go to those destinations to transact
business. If people reach the wrong destination, they transact business
with the wrong party. If a "security system," can't protect me from
reaching the wrong destination on a system designed to get me to the
right destination, then the security system is, generally speaking, useless.

I do wish I didn't have to have users connected to the networks I design
and work on --it would really make my life much simpler. But then again,
no users, no network, right? I think we sometimes get so lost in the
theory that we forget what networks are actually _for_.

:-)

Russ

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