Re: [sidr] WG acceptance call for draft-ymbk-rpki-grandparenting

Danny McPherson <danny@tcb.net> Thu, 08 November 2012 13:39 UTC

Return-Path: <danny@tcb.net>
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 F0FA421F8A69 for <sidr@ietfa.amsl.com>; Thu, 8 Nov 2012 05:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 p4zHwPDG1WBX for <sidr@ietfa.amsl.com>; Thu, 8 Nov 2012 05:39:50 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [IPv6:2600:3000:150f:701:5054:ff:fed1:24a9]) by ietfa.amsl.com (Postfix) with ESMTP id 8F87521F8A55 for <sidr@ietf.org>; Thu, 8 Nov 2012 05:39:50 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 00E91209F for <sidr@ietf.org>; Thu, 8 Nov 2012 13:39:49 +0000 (UTC)
Received: from dhcp-17b7.meeting.ietf.org (dhcp-17b7.meeting.ietf.org [130.129.23.183]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id 5E9D9449; Thu, 8 Nov 2012 06:39:49 -0700 (MST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F63B6E9BFB@Hermes.columbia.ads.sparta.com>
Date: Thu, 08 Nov 2012 08:39:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EAD8147-2EEF-45B8-938F-1D2CC5C5830F@tcb.net>
References: <CAL9jLaapLh7s1XfW7CHKPZR7HrPjeQxEC_Hgkr2j6ZTPjYRd4w@mail.gmail.com>, <CCC104A2.E764%andy@arin.net> <24B20D14B2CD29478C8D5D6E9CBB29F63B6E9BFB@Hermes.columbia.ads.sparta.com>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
X-Mailer: Apple Mail (2.1283)
X-DSPAM-Result: Whitelisted
X-DSPAM-Processed: Thu Nov 8 06:39:49 2012
X-DSPAM-Confidence: 0.9899
X-DSPAM-Improbability: 1 in 9809 chance of being spam
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 509bb625199631073215858
X-DSPAM-Factors: 27, the+#+I, 0.01000, to+#+#+in, 0.01000, Cc*sidr+#+#+#+ietf.org, 0.01000, to+#+this, 0.01000, Murphy+Sandra, 0.01000, Mime-Version*Message+#+v1283, 0.01000, 2012+#+#+#+AM, 0.01000, this+is, 0.01000, a+#+to, 0.01000, 2012+at, 0.01000, Cc*sidr+wg, 0.01000, the+#+#+a, 0.01000, To*Sandra+Sandra.Murphy, 0.01000, Mime-Version*Apple+#+framework, 0.01000, To*Sandra+#+sparta.com, 0.01000, AM+#+#+wrote, 0.01000, Murphy+#+wrote, 0.01000, Cc*wg+#+sidr, 0.01000, at+#+#+#+Murphy, 0.01000, Mime-Version*1.0+Apple, 0.01000, the+#+for, 0.01000, Mime-Version*1.0+#+Message, 0.01000, Cc*sidr+#+list, 0.01000, Cc*wg+list, 0.01000, on+the, 0.01000, in+the, 0.01000, in+#+#+that, 0.01000
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] WG acceptance call for draft-ymbk-rpki-grandparenting
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: Thu, 08 Nov 2012 13:39:51 -0000

On Nov 8, 2012, at 8:21 AM, Murphy, Sandra wrote:

> A topic that generates a fire storm of discussion has a good chance.  Nothing like actively working on a topic to demonstrate interest in working on the topic.

I do NOT support adoption of this.  It creates the opportunity for collisions in the system that a relying party has no capability to resolve.  

AS0-esque hacks make this even worse.

If the CA or some "grandparent" wants to provide this capability there are ways they can do this.

Quite frankly, this is why I like delegation models where you can't do this (e.g., DNS-esque).

-danny