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, 06 March 2011 08:40 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 28C1628C0CF for <keyassure@core3.amsl.com>; Sun, 6 Mar 2011 00:40:11 -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 z4DP9pVXBTtB for <keyassure@core3.amsl.com>; Sun, 6 Mar 2011 00:40:10 -0800 (PST)
Received: from spg.kirei.se (gomi.kirei.se [91.206.174.9]) by core3.amsl.com (Postfix) with ESMTP id 6E9E13A6918 for <keyassure@ietf.org>; Sun, 6 Mar 2011 00:40:08 -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=823ijBuj14QYR7dSvct/T/2sLEVT2nBtCRUNP306uO0=; b=jcwrmdFWOwVxGk778ypx0sA959bqUFXQjQWtK8s9IYpUnJSC4dmk6Um0+aiLCTEtD0Kq12ovFGBxl lw8nWHT0WtAl5/9au66k59UJDkO9pg8vxvtdtWRIkmoEhMtLQZu+YlGwHH8gO6SfGC9UNI71X11gTV sYP1byRK47gEtF4Q=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg.kirei.se (Halon Mail Gateway) with ESMTPS; Sun, 6 Mar 2011 09:41:17 +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: <4D725DF4.5000806@vpnc.org>
Date: Sun, 06 Mar 2011 09:41:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2AE0FD2-086D-43AE-A6F5-43EB960E9FEE@kirei.se>
References: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net> <7CDBED48-C800-4169-AF59-72075BA7EC2E@kumari.net> <AANLkTi=nKOHDajvY5Sd48p9kSbk5DUaLPFU_OE8f7Mck@mail.gmail.com> <8A18EE8A-EA0B-4AB5-A222-5D572458E9F1@kirei.se> <4D725DF4.5000806@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, 06 Mar 2011 08:40:11 -0000

On 5 mar 2011, at 16.59, Paul Hoffman wrote:

> This is not an argument against SHA-512, but if we are going to make arguments for its use, let's make sensible ones. I don't think there are many sensible ones for anything other than SHA-1, so we can just pick what we want.

I agree and after some more thinking (and reading) about this I do believe we should settle for SHA-256 and SHA-384 as the initial set of, and mandatory to implement, digest algorithms for TLSA (just as Warren proposed).

	jakob

v2.23.0 | Report a Bug | By Email