IETF Logo Mail Archive

Re: [sidr] Burstiness of BGP updates

Shankar K A <shankar.k.a@ericsson.com> Wed, 16 November 2011 04:50 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 53A951F0CC1 for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 20:50:43 -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 fRyekaTKzTVk for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 20:50:42 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9141F0CB1 for <sidr@ietf.org>; Tue, 15 Nov 2011 20:50:42 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-f6-4ec34121b721
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id ED.EF.09514.12143CE4; Wed, 16 Nov 2011 05:50:41 +0100 (CET)
Received: from ESESSCMS0358.eemea.ericsson.se ([169.254.1.199]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Wed, 16 Nov 2011 05:50:41 +0100
From: Shankar K A <shankar.k.a@ericsson.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Date: Wed, 16 Nov 2011 05:50:39 +0100
Thread-Topic: [sidr] Burstiness of BGP updates
Thread-Index: AcykGcmiNrUtVPDFTp+42gEt07QD3wAALTrQ
Message-ID: <E2D346C7800D704DB41ED19D90434DA6320C15DFA4@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> <CAL9jLaZZ6=ASKP+U4uix31w4SrBNviOdLQDMqi4eczGv975noA@mail.gmail.com>
In-Reply-To: <CAL9jLaZZ6=ASKP+U4uix31w4SrBNviOdLQDMqi4eczGv975noA@mail.gmail.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
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 04:50:43 -0000

I agree that we cannot force this. However, it should be ok if we can specify these policies as best practices or recommendations.

- Shankar K A

-----Original Message-----
From: christopher.morrow@gmail.com [mailto:christopher.morrow@gmail.com] On Behalf Of Christopher Morrow
Sent: Wednesday, November 16, 2011 10:10 AM
To: Shankar K A
Cc: Jakob Heitz; Russ White; sidr@ietf.org
Subject: Re: [sidr] Burstiness of BGP updates

On Tue, Nov 15, 2011 at 11:06 PM, Shankar K A <shankar.k.a@ericsson.com> wrote:
> I would prefer signed updated over unsigned updates as Jakob suggested.
> 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.
>

it really is, or was, the intent to permit operators of networks to decide this on their own. They MAY want to prefer unsigned/unknown/notfound/naked prefixes for certain things. It's really not up to us to say, is it? we can SUGGEST that they SHOULD prefer signed over unsigned, but in the end of the day it's on them.

v2.23.0 | Report a Bug | By Email