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> Sat, 05 March 2011 09:00 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 0F9C93A68EC for <keyassure@core3.amsl.com>; Sat, 5 Mar 2011 01:00:34 -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=[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 hdMVndUVwxJf for <keyassure@core3.amsl.com>; Sat, 5 Mar 2011 01:00:33 -0800 (PST)
Received: from spg.kirei.se (gomi.kirei.se [91.206.174.9]) by core3.amsl.com (Postfix) with ESMTP id 640A23A6859 for <keyassure@ietf.org>; Sat, 5 Mar 2011 01:00:31 -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=bpF8YiNjIbDLxsvLv559fUen+/Vztf2snZryxXbhWOY=; b=LpRvhaKU4CB9DzP4qe1AQT4aQS4kS7gktotm2jXjlYk30B5Y44P+Qnl44b4KzSTLQY7fLlySTeHhG gKSN1WpY454EzAHU3YWKbCRaFWrv4gFBv+lV8JFcBHR2BU0qtrdQrhSAY622KleDc0mvIm14WMfon9 XKCHjFug5VvGGLaQ=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg.kirei.se (Halon Mail Gateway) with ESMTPS; Sat, 5 Mar 2011 10:01: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: <AANLkTi=nKOHDajvY5Sd48p9kSbk5DUaLPFU_OE8f7Mck@mail.gmail.com>
Date: Sat, 05 Mar 2011 10:01:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A18EE8A-EA0B-4AB5-A222-5D572458E9F1@kirei.se>
References: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net> <7CDBED48-C800-4169-AF59-72075BA7EC2E@kumari.net> <AANLkTi=nKOHDajvY5Sd48p9kSbk5DUaLPFU_OE8f7Mck@mail.gmail.com>
To: Ben Laurie <benl@google.com>
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: Sat, 05 Mar 2011 09:00:34 -0000

On 4 mar 2011, at 18.37, Ben Laurie wrote:

> On 3 March 2011 19:36, Warren Kumari <warren@kumari.net> wrote:
>> Hi all,
>> 
>> After watching the thread, I'd like to propose this as a strawman:
>> 
>> Mandatory to implement algorithms are SHA-256 and SHA-384. For now, these are all we specify.
>> 
>> My reasoning behind this is:
>> 3: In order to do DANE, you have to be able to do DNSSEC -- in order to do DNSSEC you should already support the above.
> 
> Hang on. SHA-384? I don't think that is required by DNSSEC.

Correct, in order to require what DNSSEC use we should specify SHA-256 and SHA-512.

	jakob

v2.23.0 | Report a Bug | By Email