IETF Logo Mail Archive

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

Warren Kumari <warren@kumari.net> Fri, 11 March 2011 18:58 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 EC2573A6B48 for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level:
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, 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 QniBdYM3N+AW for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:58:51 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id CEC403A68F5 for <keyassure@ietf.org>; Fri, 11 Mar 2011 10:58:51 -0800 (PST)
Received: from dot.her.corp.google.com (unknown [74.202.225.33]) by vimes.kumari.net (Postfix) with ESMTPSA id 37B5F1B401D8; Fri, 11 Mar 2011 14:00:11 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4D7A70A7.8020103@vpnc.org>
Date: Fri, 11 Mar 2011 14:00:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E00FE45A-6970-4280-802D-F5A39E22C906@kumari.net>
References: <E1Px6dz-0001Hb-LV@login01.fos.auckland.ac.nz> <8EB57F84-0F78-4939-82FB-5B97FBFF2CD0@kumari.net> <4D7A70A7.8020103@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1081)
Cc: keyassure@ietf.org
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:58:53 -0000

On Mar 11, 2011, at 1:57 PM, Paul Hoffman wrote:

> 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).

The chairs would like to thank our authors for being on top of things, quickly integrating WG consensus and writing such a readable doc....

W

> 
> --Paul Hoffman
> _______________________________________________
> keyassure mailing list
> keyassure@ietf.org
> https://www.ietf.org/mailman/listinfo/keyassure
>

v2.23.0 | Report a Bug | By Email