Re: [sidr] Burstiness of BGP updates

Shankar K A <shankar.k.a@ericsson.com> Wed, 16 November 2011 05:09 UTC

Return-Path: <shankar.k.a@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 0A6BF21F90BA for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 21:09:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 BGWLLGw3TKcl for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 21:09:31 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 3274A21F8DD9 for <sidr@ietf.org>; Tue, 15 Nov 2011 21:09:31 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-12-4ec3458a1af6
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id E7.B1.09514.A8543CE4; Wed, 16 Nov 2011 06:09:30 +0100 (CET)
Received: from ESESSCMS0358.eemea.ericsson.se ([169.254.1.199]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 16 Nov 2011 06:09:29 +0100
From: Shankar K A <shankar.k.a@ericsson.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>, Russ White <russw@riw.us>
Date: Wed, 16 Nov 2011 06:09:28 +0100
Thread-Topic: [sidr] Burstiness of BGP updates
Thread-Index: AcykGcRG1uCuScnfShCD/Vas5tY7RAAAXqcgAACVgXA=
Message-ID: <E2D346C7800D704DB41ED19D90434DA6320C15DFAE@ESESSCMS0358.eemea.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> <7309FCBCAE981B43ABBE69B31C8D21391A45A20633@EUSAACMS0701.eamcs.ericsson.se> <E2D346C7800D704DB41ED19D90434DA6320C15DF93@ESESSCMS0358.eemea.ericsson.se> <4EC33E88.9090505@riw.us> <7309FCBCAE981B43ABBE69B31C8D21391A45A20649@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391A45A20649@EUSAACMS0701.eamcs.ericsson.se>
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
X-Brightmail-Tracker: AAAAAA==
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 05:09:32 -0000

You cannot use BGP to enable you to send such messages. There could be million other ways to do what you are saying. After this, there is one less chance. That's all.


- Shankar K A 

-----Original Message-----
From: Jakob Heitz 
Sent: Wednesday, November 16, 2011 10:36 AM
To: Russ White; Shankar K A
Cc: sidr@ietf.org
Subject: RE: [sidr] Burstiness of BGP updates

> -----Original Message-----
> From: Russ White [mailto:russw@riw.us]
> Sent: Tuesday, November 15, 2011 8:40 PM
> To: Shankar K A
> Cc: Jakob Heitz; sidr@ietf.org
> Subject: Re: [sidr] Burstiness of BGP updates
> 
> 
> > But strictly speaking, IMO we should only accept signed updates,
> because it's the number of AS that we add in the update that we are 
> protecting.
> > By accepting unsigned update we may accept unprotected path
> information.
> 
> Precisely my point.

What is the value of that?
Does this now allow me to send passwords in the clear on the internet?

--
Jakob Heitz.