IETF Logo Mail Archive

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

Chris Palmer <chris@eff.org> Tue, 08 March 2011 00:04 UTC

Return-Path: <chris@eff.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 7F5FB3A69B5 for <keyassure@core3.amsl.com>; Mon, 7 Mar 2011 16:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.044
X-Spam-Level:
X-Spam-Status: No, score=-6.044 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JSFOgAKg2hnt for <keyassure@core3.amsl.com>; Mon, 7 Mar 2011 16:04:25 -0800 (PST)
Received: from mail1.eff.org (mail1.eff.org [64.147.188.4]) by core3.amsl.com (Postfix) with ESMTP id CF00B3A68AA for <keyassure@ietf.org>; Mon, 7 Mar 2011 16:04:25 -0800 (PST)
Received: from [192.168.0.28] (208-90-214-239.PUBLIC.monkeybrains.net [208.90.214.239]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: chris) by mail1.eff.org (Postfix) with ESMTPSA id 21425BDD55; Mon, 7 Mar 2011 16:05:41 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Chris Palmer <chris@eff.org>
In-Reply-To: <8FB60B62-483F-48B5-8A36-390872C18BD5@kumari.net>
Date: Mon, 07 Mar 2011 16:05:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B7097F3-26FD-412F-B96E-8AB46D1E967C@eff.org>
References: <201103071425.p27EPvrB000688@fs4113.wdf.sap.corp> <208C68A5-568B-4447-854C-70A4A229B84C@checkpoint.com> <9C30235F-FF8C-44E7-B7BC-5D284586D11B@eff.org> <4D752197.5090403@vpnc.org> <8FB60B62-483F-48B5-8A36-390872C18BD5@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1082)
Cc: keyassure@ietf.org, Paul Hoffman <paul.hoffman@vpnc.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: Tue, 08 Mar 2011 00:04:26 -0000

On Mar 7, 2011, at 3:09 PM, Warren Kumari wrote:

> The WG chairs (well, this one at least) sees no consensus yet[0]....

Actually, I thought that people had roughly agreed to specify SHA-256 and -384 and to create a slot for SHA-3. If I'm wrong and that's not what people have roughly agreed, then I apologize and here are my two cents: As long as the minimum is -256 with a plan for SHA-3, I'm happy.


-- 
Chris Palmer
Technology Director, Electronic Frontier Foundation

v2.23.0 | Report a Bug | By Email