IETF Logo Mail Archive

Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement"

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 27 February 2011 17:28 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 6F6D93A6A18 for <keyassure@core3.amsl.com>; Sun, 27 Feb 2011 09:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.481
X-Spam-Level:
X-Spam-Status: No, score=-101.481 tagged_above=-999 required=5 tests=[AWL=0.565, BAYES_00=-2.599, 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 47uOr9oSVDMj for <keyassure@core3.amsl.com>; Sun, 27 Feb 2011 09:28:51 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id BA2813A6A13 for <keyassure@ietf.org>; Sun, 27 Feb 2011 09:28:51 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1RHSYtp030490 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 27 Feb 2011 10:28:34 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D6A89C2.3030101@vpnc.org>
Date: Sun, 27 Feb 2011 09:28:34 -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: Jakob Schlyter <jakob@kirei.se>
References: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net> <4D6826FE.2080107@vpnc.org> <F2D724F1-9F51-4CB7-BBD0-CCF6966BD311@kirei.se>
In-Reply-To: <F2D724F1-9F51-4CB7-BBD0-CCF6966BD311@kirei.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: keyassure@ietf.org
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement"
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: Sun, 27 Feb 2011 17:28:52 -0000

On 2/27/11 4:27 AM, Jakob Schlyter wrote:
> On 25 feb 2011, at 23.02, Paul Hoffman wrote:
>
>> Hash algorithm:
>>
>> - All implementations must support SHA-256.
>
> i.e., reference type 2.
>
>> - All implementations should have the facility to later use other hash algorithms.
>
> Also, all implementations must support reference type 0 (aka "full certificate").

Er, right, of course. That too.

v2.23.0 | Report a Bug | By Email