Re: [sidr] beacons and bgpsec

George Michaelson <ggm@pobox.com> Wed, 10 August 2011 01:23 UTC

Return-Path: <geeohgeegeeoh@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 6E29C228017 for <sidr@ietfa.amsl.com>; Tue, 9 Aug 2011 18:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level:
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 oHFX2XVfY2pV for <sidr@ietfa.amsl.com>; Tue, 9 Aug 2011 18:23:22 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 76C6F22800E for <sidr@ietf.org>; Tue, 9 Aug 2011 18:23:21 -0700 (PDT)
Received: by yie12 with SMTP id 12so443231yie.31 for <sidr@ietf.org>; Tue, 09 Aug 2011 18:23:50 -0700 (PDT)
Received: by 10.151.102.12 with SMTP id e12mr762352ybm.138.1312939430021; Tue, 09 Aug 2011 18:23:50 -0700 (PDT)
Received: from dynamic201.apnic.net (dynamic201.apnic.net [203.119.42.201]) by mx.google.com with ESMTPS id 16sm2564793ybm.18.2011.08.09.18.23.47 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Aug 2011 18:23:49 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="us-ascii"
From: George Michaelson <ggm@pobox.com>
In-Reply-To: <87D9E106-2A37-4E1E-8C69-7084C199A3FE@tcb.net>
Date: Wed, 10 Aug 2011 11:23:46 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <331AEFBD-6AE5-469E-A11E-E672DC61DCDC@pobox.com>
References: <A37CADA4-F16D-4C01-8D9C-D01001C4EFE4@tcb.net> <21C19DA8-7BF3-4832-8C13-C9A45FE026FB@algebras.org> <87D9E106-2A37-4E1E-8C69-7084C199A3FE@tcb.net>
To: Danny McPherson <danny@tcb.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] beacons and bgpsec
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, 10 Aug 2011 01:23:22 -0000

On 10/08/2011, at 11:19 AM, Danny McPherson wrote:

> 
> On Aug 9, 2011, at 9:15 PM, George Michaelson wrote:
> 
>> 
>> Forgive a peanut gallery observation, but are we defining things as useless which we cannot understand in RPKI, because to admit that we don't understand them in RPKI means making RPKI more complex?
> 
> I'm not talking about RPKI, I'm talking about BGPSEC.  

Ok. S/RPKI/BGPSEC/

> 
> I don't understand your question...

You seemed to be saying "some people are saying beacons wont work"

when you said: "I think Randy successfully convinced me during his talk at the Quebec City WG session that "beacons" at a frequency of 24 hours (or anything in the "hours" range) are pretty much useless and add considerable churn and complexity with little return from a practical attack surface perspective.  "

So, I am asking, are we removing support for beacons in BGPSEC because we don't understand their impact on BGPSEC and they add complexity which makes BGPSEC harder to push uphill.

Its very probably an unfair question. Thats why I called it the peanut gallery.

-G

> 
> -danny
>