IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 04 March 2011 14:38 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 8C1293A6864 for <keyassure@core3.amsl.com>; Fri, 4 Mar 2011 06:38:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.82
X-Spam-Level:
X-Spam-Status: No, score=-101.82 tagged_above=-999 required=5 tests=[AWL=0.779, 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 z22mmdi2vdSy for <keyassure@core3.amsl.com>; Fri, 4 Mar 2011 06:38:07 -0800 (PST)
Received: from hoffman.proper.com (unknown [IPv6:2001:4870:a30c:41::81]) by core3.amsl.com (Postfix) with ESMTP id 82EAA3A6834 for <keyassure@ietf.org>; Fri, 4 Mar 2011 06:38:07 -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 p24EdCXo029376 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Fri, 4 Mar 2011 07:39:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D70F990.2040202@vpnc.org>
Date: Fri, 04 Mar 2011 06:39:12 -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.14) Gecko/20110221 Thunderbird/3.1.8
MIME-Version: 1.0
To: keyassure@ietf.org
References: <7CDBED48-C800-4169-AF59-72075BA7EC2E@kumari.net> <201103041246.p24CkHZt011245@fs4113.wdf.sap.corp> <AANLkTik1r-sZvnNHCUtKO1De2CGb53x1Wk+ojRPOhOih@mail.gmail.com>
In-Reply-To: <AANLkTik1r-sZvnNHCUtKO1De2CGb53x1Wk+ojRPOhOih@mail.gmail.com>
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, 04 Mar 2011 14:38:08 -0000

On 3/4/11 5:57 AM, Phillip Hallam-Baker wrote:
> OK, how about this
>
> Define code points for
>
> SHA2-256
> SHA2-512
> SHA3-256 (reserved)
> SHA3-512 (reserved)

This would only work if we knew today that there will be algorithms with 
those exact names. Those of us following the NIST hash competition have 
seen that there is a good chance that will *not* be the case: NIST is 
explicitly allowing (some would say encouraging) parameters on the 
functions.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email