Re: [sidr] BGPSEC Threat Model ID

Christopher Morrow <morrowc.lists@gmail.com> Fri, 04 November 2011 21:08 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 979DB11E8082 for <sidr@ietfa.amsl.com>; Fri, 4 Nov 2011 14:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.534
X-Spam-Level:
X-Spam-Status: No, score=-103.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 uqAUgma73O2o for <sidr@ietfa.amsl.com>; Fri, 4 Nov 2011 14:08:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2A11D21F8AF7 for <sidr@ietf.org>; Fri, 4 Nov 2011 14:08:36 -0700 (PDT)
Received: by iaeo4 with SMTP id o4so3893589iae.31 for <sidr@ietf.org>; Fri, 04 Nov 2011 14:08:35 -0700 (PDT)
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 :content-transfer-encoding; bh=WqBlaKABpdJ+lbWU6dvF1rMVJ2wLdE0YD+Z6vPy31No=; b=H8C4U1VlMLwUWEeKA2bKgcjr76tj1qffIqrKliAQh/7QrBsoG6TMproQlJwJ82DhLt 8OVEr5aSIPrVPnjVRAUtrfnAGXWngvTK2ccBPPqfbUJgd25NqDY93we+MZGJG6NKG2UG QuFRRExOANG/N8Wi+DTgfMgU+uHAsKrxlFo54=
MIME-Version: 1.0
Received: by 10.231.41.4 with SMTP id m4mr4205199ibe.44.1320440915834; Fri, 04 Nov 2011 14:08:35 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.231.202.142 with HTTP; Fri, 4 Nov 2011 14:08:35 -0700 (PDT)
In-Reply-To: <53FA9B4A-552C-4998-8F69-592A0F5AA13B@verisign.com>
References: <E96517DD-BAC7-4DD8-B345-562F71788C6A@tcb.net> <p06240807cad42f85eb7d@193.0.26.186> <32744.216.168.239.87.1320175657.squirrel@webmail.tcb.net> <p06240801cad6ab773279@193.0.26.186> <D9A38669-883D-4090-9F95-BC5C63220950@tcb.net> <p06240801cad800485596@193.0.26.186> <EEBF68E0-FAD9-4AF3-B81B-78760D200D9B@tcb.net> <p06240808cad85ff73d61@193.0.26.186> <080F8FFF-D2C7-4414-B53A-233F88D2009F@vpnc.org> <CAFU7BATC-6DUDNuadakwSa5wj0ryy0=49=XveBXD5Wv=5JL-ag@mail.gmail.com> <m2aa8c489s.wl%randy@psg.com> <53FA9B4A-552C-4998-8F69-592A0F5AA13B@verisign.com>
Date: Fri, 04 Nov 2011 17:08:35 -0400
X-Google-Sender-Auth: uzgXNX7OvzBxhgXhaoD8zrhTB8U
Message-ID: <CAL9jLaZVbL=BKxDUg1H6bNZEm+LsXme6Z=7AKJ+G85kV=+2GPA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Eric Osterweil <eosterweil@verisign.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] BGPSEC Threat Model ID
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: Fri, 04 Nov 2011 21:08:36 -0000

On Fri, Nov 4, 2011 at 3:05 PM, Eric Osterweil <eosterweil@verisign.com> wrote:
>> you are correct, BGPsec tries to secure the BGP protocol against abuse,
>> not protect the internet.  the latter is a very worthy goal but a bit
>> nebulous.  of course an internet draft or two might clarify that.
>
> This seems like a very pedantic distinction.  Having an AS' traffic routed through an invalid path seems like a BGP protocol abuse to me.  So, in that language, it seems to me that this issue is in scope (i.e. if the path is to be protected, then subverting it is an abuse).
>

oops, also, still not randy, but... there are lots of ways to bend
traffic in the wrong direction and still keep bgp data 'the same'. I'm
not sure fixing traffic paths is doable in BGP.

Do you see a way to do this in BGP?

-chris