Re: [sidr] draft-sriram-bgpsec-design-choices-00 -- IXP and Route Server

"Chris Hall" <chris.hall@highwayman.com> Sun, 10 July 2011 16:47 UTC

Return-Path: <chris.hall@highwayman.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 2390321F8593 for <sidr@ietfa.amsl.com>; Sun, 10 Jul 2011 09:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k6c7FAntSBUM for <sidr@ietfa.amsl.com>; Sun, 10 Jul 2011 09:47:01 -0700 (PDT)
Received: from anchor-post-2.mail.demon.net (anchor-post-2.mail.demon.net [195.173.77.133]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2C221F857D for <sidr@ietf.org>; Sun, 10 Jul 2011 09:47:01 -0700 (PDT)
Received: from [80.177.246.162] (helo=hestia.halldom.com) by anchor-post-2.mail.demon.net with esmtp (Exim 4.69) id 1Qfx9o-00031U-mD; Sun, 10 Jul 2011 16:47:01 +0000
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION) by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from <chris.hall@highwayman.com>) id 1Qfx9n-0008Ng-D8; Sun, 10 Jul 2011 17:46:59 +0100
From: Chris Hall <chris.hall@highwayman.com>
To: "'Sriram, Kotikalapudi'" <kotikalapudi.sriram@nist.gov>
References: <012601cc3d54$8f07c4e0$ad174ea0$@highwayman.com> <m2y609kptw.wl%randy@psg.com> <014001cc3d74$319571c0$94c05540$@highwayman.com> <m2pqlklw3v.wl%randy@psg.com> <014a01cc3d7f$6312f730$2938e590$@highwayman.com> <m2oc14ljh7.wl%randy@psg.com> <017d01cc3da0$9f8cd390$dea67ab0$@highwayman.com> <Pine.WNT.4.64.1107081506110.1536@SMURPHY-LT.columbia.ads.sparta.com> <D7A0423E5E193F40BE6E94126930C4930879E9BDD3@MBCLUSTER.xchange.nist.gov>, <01ab01cc3e1b$db54d230$91fe7690$@highwayman.com> <D7A0423E5E193F40BE6E94126930C4930877FE8A5C@MBCLUSTER.xchange.nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C4930877FE8A5C@MBCLUSTER.xchange.nist.gov>
Date: Sun, 10 Jul 2011 17:46:54 +0100
Organization: Highwayman
Message-ID: <01f101cc3f20$fc7485e0$f55d91a0$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLnVxnGjNWVOyUsj5rn4Yr0eH1c1gL48hq9AYUdEa8CIAtBeALePpAvAmnYtsEBdZrX2AJHVOEeAiwqzkIBlx5YnwDgus8ukg1WnoA=
Content-Language: en-gb
Cc: 'Sandra Murphy' <Sandra.Murphy@sparta.com>, 'sidr wg list' <sidr@ietf.org>
Subject: Re: [sidr] draft-sriram-bgpsec-design-choices-00 -- IXP and Route Server
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: Sun, 10 Jul 2011 16:47:02 -0000

Sriram, Kotikalapudi wrote (on 09-Jul-2011 at 14:30 +0100):
> Chris Hall wrote:
....
> >Strictly entre nous, I don't get a strong sense from the text that
> >entering into such an arrangement is an obvious and foolish mistake
> :-}
....
> Having said that, I respect Randy's viewpoint (and yours -- seems
> you are in agreement).

I was mostly paraphrasing the opinion which had been put to me quite
strongly.

>From where I sit, I would happily trust, say, the LINX.  But I
entirely take the point that a better system would not require me to
depend entirely on trust; and someone new to the LINX might prefer not
to.

....
> We can revise Section 6.6 to put greater emphasis on the "cons" part
> of it.

I think that would be a most reasonable thing to do.

Particularly, from the RS perspective, because Proxy Signing is
(currently) how a Transparent BGPSEC RS might be implemented.  The
cons would be the basis for a case for some other solution, in the
BGPSEC protocol, or elsewhere. 

Chris