Re: [keyassure] Opening issue #21: "Need to specify which crypto

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 11 March 2011 18:56 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3713B3A6C6F for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.971
X-Spam-Level:
X-Spam-Status: No, score=-101.971 tagged_above=-999 required=5 tests=[AWL=0.628, BAYES_00=-2.599, 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 vrJVNI3yr9gO for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:56:27 -0800 (PST)
Received: from hoffman.proper.com (unknown [IPv6:2001:4870:a30c:41::81]) by core3.amsl.com (Postfix) with ESMTP id C9BE93A6B49 for <keyassure@ietf.org>; Fri, 11 Mar 2011 10:56:25 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p2BIviif039701 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Fri, 11 Mar 2011 11:57:44 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D7A70A7.8020103@vpnc.org>
Date: Fri, 11 Mar 2011 10:57:43 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: keyassure@ietf.org
References: <E1Px6dz-0001Hb-LV@login01.fos.auckland.ac.nz> <8EB57F84-0F78-4939-82FB-5B97FBFF2CD0@kumari.net>
In-Reply-To: <8EB57F84-0F78-4939-82FB-5B97FBFF2CD0@kumari.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 18:56:28 -0000

On 3/11/11 10:45 AM, Warren Kumari wrote:
> Ok,
>
> We are calling (rough) consensus as:
>
> SHA-256 MUST be implemented.
> SHA-512 SHOULD be implemented.
>
> We fully expect to support SHA-3 once it is finalized, but we are not currently reserving code-points for it.
> We can re-visit code-points for SHA-3 as we know more about it, how many code-points it should have, etc.

Jakob and I will put out a new draft on Monday with this plus some 
different wording on trust anchors (the latter being still confusing to 
some folks).

--Paul Hoffman