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

Martin Rex <mrex@sap.com> Thu, 03 March 2011 04:56 UTC

Return-Path: <mrex@sap.com>
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 19DF03A6969 for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 20:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.235
X-Spam-Level:
X-Spam-Status: No, score=-10.235 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 r5dFWxditqiU for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 20:56:00 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id 0D5403A695E for <keyassure@ietf.org>; Wed, 2 Mar 2011 20:55:59 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p234v4Qx012329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Mar 2011 05:57:04 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201103030457.p234v4g5025114@fs4113.wdf.sap.corp>
To: paul.hoffman@vpnc.org
Date: Thu, 03 Mar 2011 05:57:04 +0100
In-Reply-To: <4D6EE7E1.1070700@vpnc.org> from "Paul Hoffman" at Mar 2, 11 04:59:13 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
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
Reply-To: mrex@sap.com
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: Thu, 03 Mar 2011 04:56:01 -0000

Paul Hoffman wrote:
> 
> Phillip Hallam-Baker wrote:
> >
> > 1) Make support for SHA2-256 and SHA2-384 REQUIRED
> > 2) Ensure that it is feasible to transition from use of SHA2
> >    to a new algorithm
> > 3) Deprecate use of MD2,MD4,MD5 and SHA1.
> 
> We disagree on #1 in that I don't think that requiring SHA-384 has any 
> practical value and adds a second code path where none is needed.
> 
> We agree only partially on #2. You keep saying "SHA2" when you probably 
> mean "SHA-256 and SHA-384". I agree that making the transition feasible 
> is good, and we already have that.
> 
> We disagree on #3, and deprecating crypto is a different issue than 
> mandating crypto.

I agree to all what Paul wrote.

Iff SHA-256 is to be a mandatory to implement hash for DANE, then
I see _no_ point in supporting SHA-1 at all (and saves us migration).


-Martin