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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 02 March 2011 22:58 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 4D33F3A68FE for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 14:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.583
X-Spam-Level:
X-Spam-Status: No, score=-100.583 tagged_above=-999 required=5 tests=[AWL=-0.396, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 c0Q4OEv6u537 for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 14:58:11 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 96C4E3A6816 for <keyassure@ietf.org>; Wed, 2 Mar 2011 14:58:04 -0800 (PST)
Received: from sn87.proper.com (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p21McALR062114 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Tue, 1 Mar 2011 15:38:11 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D6D7551.3070606@vpnc.org>
Date: Tue, 01 Mar 2011 14:38:09 -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.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: keyassure@ietf.org
References: <AANLkTimGsc38B+2R03CiW2TzKoiHvj_7NLs0gD=340Tw@mail.gmail.com> <201103011815.p21IFukr020670@fs4113.wdf.sap.corp> <AANLkTinE1QqjqY5g+nQtq3hKD7z5spkuFqsT=9tmB+WR@mail.gmail.com>
In-Reply-To: <AANLkTinE1QqjqY5g+nQtq3hKD7z5spkuFqsT=9tmB+WR@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: Wed, 02 Mar 2011 22:58:12 -0000

On 3/1/11 1:37 PM, Phillip Hallam-Baker wrote:
> This particular topic is one on which the Security ADs and the IETF
> chair have very very specific opinions on. And given their role in
> trying to effect an industry wide transition to stronger algorithms, I
> think that they are quite right to insist on them.

If you can quote previous statements from any of them suggesting that 
SHA-256 is suspect, that would be more useful than you simply suggesting 
that they had said something. It would be useful to this discussion for 
each of us to speak only for ourselves and for those who have asked us 
to speak for them, or to quote others whom we think are authorities.