Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08

Sam Hartman <hartmans-ietf@mit.edu> Fri, 16 August 2013 18:02 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD5011E81FF; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level:
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, 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 2g8uESl0QDlu; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 13E4011E8165; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5E8AA202AC; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQ7nmKCcgc0z; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C99958052F; Fri, 16 Aug 2013 14:02:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> (David Black's message of "Fri, 16 Aug 2013 13:02:35 -0400")
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Fri, 16 Aug 2013 14:02:33 -0400
Message-ID: <tslob8x345i.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:02:35 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> done.  IMHO, we really should be setting a bar that says
    Black,> that this sort of IETF imprimatur of approval of a crypto
    Black,> algorithm actually means something.



Something got manged there.
I agree that publishing a standards-track document  should endorce the
algorithm in question.

I'm somewhat uncomfortable with that sort of bar for IANA registries in
general, although I have supported it from time to time.  (My discomfort
with this has grown significantly since my time as an AD).  I do not
support that sort of bar for this registry.

I think we understand each other, but disagree.

The question now is whether you can gain sufficient support to show
rough consensus for a change in the document or to show that while there
was rough consensus behind the document in the KARP WG, there's a lack
of consensus on handling this issue between KARP and some other
significant segment of the IETF like the security area.