Re: [sidr] Burstiness of BGP updates

Christopher Morrow <morrowc.lists@gmail.com> Wed, 16 November 2011 06:03 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 61BCD1F0D2F for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 22:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.55
X-Spam-Level:
X-Spam-Status: No, score=-103.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 CTVpw-j6HZvS for <sidr@ietfa.amsl.com>; Tue, 15 Nov 2011 22:03:26 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 117A11F0D29 for <sidr@ietf.org>; Tue, 15 Nov 2011 22:03:23 -0800 (PST)
Received: by iaeo4 with SMTP id o4so160003iae.31 for <sidr@ietf.org>; Tue, 15 Nov 2011 22:03:23 -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; bh=6MIyRbCrItY8vJSur5AQQtbatP3QxKcRTp6bqUinXzA=; b=b6vgCe8dt2XxMXQX3wccZZwdUkbcNvZWj2i2zTP6Kz6UotqY6sTdsHLR3j6Vog+ygF f+eFKCNXMWGMBwMDgYxXISrKu5JkavUN61s4oBUQdfYXU0msFax65DDCekr5pMARAqOY /ohn8CY/AvpjMB3TeuvIPUXQPkhZwB2okNYKU=
MIME-Version: 1.0
Received: by 10.231.5.81 with SMTP id 17mr7154324ibu.31.1321423403661; Tue, 15 Nov 2011 22:03:23 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.231.202.142 with HTTP; Tue, 15 Nov 2011 22:03:23 -0800 (PST)
In-Reply-To: <CAH1iCiq38ViGN_UWr9+AGuOhfvzgbedRk0esrjmk4B6L_Tk+8g@mail.gmail.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> <CAH1iCiqFq7reoMrCBAUOk-PdmZDYoed+ii37xQbgX0nopNgDEw@mail.gmail.com> <CAL9jLaZ+m=P37X+Q3sf5r=RmdDniA+XSYMbQFF8_PZyCq2WtUQ@mail.gmail.com> <CAH1iCiq38ViGN_UWr9+AGuOhfvzgbedRk0esrjmk4B6L_Tk+8g@mail.gmail.com>
Date: Wed, 16 Nov 2011 01:03:23 -0500
X-Google-Sender-Auth: oji7TpbNeCo5G4_u9GLv663jlM8
Message-ID: <CAL9jLabj1Wx=m-zZS1SG6BymBpnaDcLmh6XKkBfJj=31KEjBMA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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 06:03:27 -0000

On Wed, Nov 16, 2011 at 12:56 AM, Brian Dickson
<brian.peter.dickson@gmail.com> wrote:
> On Wed, Nov 16, 2011 at 12:35 AM, Christopher Morrow
> <morrowc.lists@gmail.com> wrote:

>> you may be willing to do same, you may also be willing to do this in
>> the case of internal services routes that you don't actually want
>> externally visible.
>
> Sure - and locally significant signatures/trust-anchors are very
> important for just such an occasion.
> (For any convenient value of "local", it should be noted. City, zip
> code, province, continent, building, whatever.)

yup, agreed.

>>
>> re-announcement is 'harder' since it's not clear if NTT is supposed to
>> be passing cogent aol's routes or not, is it?
>
> Agreed - I can't be specific on exactly when, but expect me to present something
> "real soon now" on a nuts-and-bolts level of how to do this. Maybe a
> month, maybe two.

look forward to it!
I wonder actually if some on-going survey of routing data could help
to inform when a 'leak' happens... I suspect this is what cyclops/etc
are doing (identifying normal 'status' of routes between networks),
I'm not clear on how useful this would be in the end though, my
experience with cyclops/etc haven't been useful so far :(

-chris