IETF Logo Mail Archive

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

Jakob Schlyter <jakob@kirei.se> Sun, 27 February 2011 12:26 UTC

Return-Path: <jakob@kirei.se>
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 C8C173A6827 for <keyassure@core3.amsl.com>; Sun, 27 Feb 2011 04:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 WfoK1WeGbgDF for <keyassure@core3.amsl.com>; Sun, 27 Feb 2011 04:26:44 -0800 (PST)
Received: from spg.kirei.se (gomi.kirei.se [91.206.174.9]) by core3.amsl.com (Postfix) with ESMTP id 1EEEC3A6803 for <keyassure@ietf.org>; Sun, 27 Feb 2011 04:26:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=l42WhTADT6eQBaRW5U0OIG7l/VWfsgV7ZEEH/B3EN2E=; b=GcSxsYT3klEF8rqhQYL76m8tH/wnJCXG0oxiKILVObfPItkcs9Hx9Tk0husG6G4HWk89vsG+JXted EI7CsKoqVnYWWm3dFZuA6CWMGmSmwalQ77VCLrByJ+1YTnHZlo2II+IwubnZGQNvyZdtm0qok5HOpc mXzYo4ml4sHOe2Uw=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg.kirei.se (Halon Mail Gateway) with ESMTPS; Sun, 27 Feb 2011 13:27:37 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Jakob Schlyter <jakob@kirei.se>
In-Reply-To: <4D6826FE.2080107@vpnc.org>
Date: Sun, 27 Feb 2011 13:27:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2D724F1-9F51-4CB7-BBD0-CCF6966BD311@kirei.se>
References: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net> <4D6826FE.2080107@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1082)
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 12:26:45 -0000

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

	jakob

v2.23.0 | Report a Bug | By Email