Re: [secdir] Secdir review of draft-ietf-sidr-res-certs

Sam Hartman <hartmans-ietf@mit.edu> Thu, 10 March 2011 19:06 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C90903A6828; Thu, 10 Mar 2011 11:06:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.878
X-Spam-Level:
X-Spam-Status: No, score=-102.878 tagged_above=-999 required=5 tests=[AWL=-0.613, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ScvgkMKD0PRs; Thu, 10 Mar 2011 11:06:42 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 0D4BE3A6806; Thu, 10 Mar 2011 11:06:41 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 89FBA202B2; Thu, 10 Mar 2011 14:05:14 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 78108432D; Thu, 10 Mar 2011 14:07:31 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <tslhbbag9m1.fsf@mit.edu> <4D791B26.8020001@vpnc.org>
Date: Thu, 10 Mar 2011 14:07:31 -0500
In-Reply-To: <4D791B26.8020001@vpnc.org> (Paul Hoffman's message of "Thu, 10 Mar 2011 10:40:38 -0800")
Message-ID: <tsl4o7ag5fw.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: draft-ietf-sidr-res-certs@tools.ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, secdir@ietf.org
Subject: Re: [secdir] Secdir review of draft-ietf-sidr-res-certs
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 19:06:42 -0000

>>>>> "Paul" == Paul Hoffman <paul.hoffman@vpnc.org> writes:

    Paul> On 3/10/11 9:37 AM, Sam Hartman wrote:
    >> The document also requires that relying parties reject
    >> certificates that include unknown extensions. The rationale
    >> explained in section 8 is that it is undesirable to have a
    >> situation where if an RP implemented more extensions it would
    >> reject certificates that a more minimal RP would accept.  In
    >> other words the profile picks security and minimalism over
    >> extensibility.

    Paul> This statement is too narrow, and it causes your analysis to
    Paul> come to a too narrow conclusion. The profile picks security
    Paul> and minimalism over extensibility *of this profile only*. If a
    Paul> flaw is later found that requires an extension, that extension
    Paul> will be written up in a standards-track document that will
    Paul> obsolete this profile. An implementation that conforms to that
    Paul> new profile will use the extension. Thus, errors can be
    Paul> corrected with new profiles, and the RPKI will have multiple
    Paul> profiles running on it, just as the Internet has multiple
    Paul> versions of some protocols running on it.


Paul, that's a great argument for why it's OK to prohibit issuing
certificates with new extensions in this profile.
We absolutely can change CA behavior with a new profile.

However, I don't think your argument makes sense for RP behavior.
Under this profile, if an RP is presented with a certificate issued
under a new RPKI profile, it will reject that certificate.

So, it sounds a lot like you'd need to upgrade all the RPs that might
need to rely on a particular resource certificate before  you could
issue that certificate under a new profile.
Given that resource certificates can be used by a lot of RPs--for
example anyone who needs to verify origins of a route presumably--that's
a long wait.
I think that's unjustified.

One of us is clearly missing something. I would be happy if it's me.