IETF Logo Mail Archive

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

Warren Kumari <warren@kumari.net> Fri, 11 March 2011 18:44 UTC

Return-Path: <warren@kumari.net>
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 647C73A691E for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level:
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, 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 wlLVBSlclUYy for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:44:35 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id A49503A68CB for <keyassure@ietf.org>; Fri, 11 Mar 2011 10:44:35 -0800 (PST)
Received: from dot.her.corp.google.com (unknown [74.202.225.33]) by vimes.kumari.net (Postfix) with ESMTPSA id F04431B401D8 for <keyassure@ietf.org>; Fri, 11 Mar 2011 13:45:54 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1081)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <E1Px6dz-0001Hb-LV@login01.fos.auckland.ac.nz>
Date: Fri, 11 Mar 2011 13:45:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8EB57F84-0F78-4939-82FB-5B97FBFF2CD0@kumari.net>
References: <E1Px6dz-0001Hb-LV@login01.fos.auckland.ac.nz>
To: keyassure@ietf.org
X-Mailer: Apple Mail (2.1081)
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:44:36 -0000

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. 

W

v2.23.0 | Report a Bug | By Email