Re: [Cfrg] Message Digest Algorithm Choice for CMS with Ed448

"Salz, Rich" <rsalz@akamai.com> Mon, 14 November 2016 18:30 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD02129981 for <cfrg@ietfa.amsl.com>; Mon, 14 Nov 2016 10:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.218
X-Spam-Level:
X-Spam-Status: No, score=-4.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dT_1rsTJ5WEo for <cfrg@ietfa.amsl.com>; Mon, 14 Nov 2016 10:30:43 -0800 (PST)
Received: from prod-mail-xrelay05.akamai.com (prod-mail-xrelay05.akamai.com [23.79.238.179]) by ietfa.amsl.com (Postfix) with ESMTP id 1090712997A for <cfrg@irtf.org>; Mon, 14 Nov 2016 10:30:39 -0800 (PST)
Received: from prod-mail-xrelay05.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 285A5423725; Mon, 14 Nov 2016 18:30:39 +0000 (GMT)
Received: from prod-mail-relay11.akamai.com (prod-mail-relay11.akamai.com [172.27.118.250]) by prod-mail-xrelay05.akamai.com (Postfix) with ESMTP id 0EF9442371A; Mon, 14 Nov 2016 18:30:39 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1479148239; bh=GrMNm3qEySGmVmPzpWMTKW+bCsj5WFJCConBa5G4uvY=; l=247; h=From:To:Date:References:In-Reply-To:From; b=hgaqlRlHiiciZunMIOPdyfLgPZgPa+i6Y9rzCTvHSUp3Bieu4LlToacBoIPhJB2jr cNpZmjeWFYq5fDGINY8tfBheyp5JPNF8ZD8+Tg8SXpEK4rJygJYHS5qHSwQoamiDjt U2cI8fJ3Lx/OoJftaSSFtpnXrfuPNTn6/ElXRPD8=
Received: from email.msg.corp.akamai.com (usma1ex-cas3.msg.corp.akamai.com [172.27.123.32]) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id 078241FD9E; Mon, 14 Nov 2016 18:30:39 +0000 (GMT)
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 14 Nov 2016 13:30:38 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1178.000; Mon, 14 Nov 2016 13:30:38 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Russ Housley <housley@vigilsec.com>, IRTF CFRG <cfrg@irtf.org>
Thread-Topic: [Cfrg] Message Digest Algorithm Choice for CMS with Ed448
Thread-Index: AQHSPWHICpH4fzGQvky+SPbkURYniqDYz3lA
Date: Mon, 14 Nov 2016 18:30:38 +0000
Message-ID: <1dddb08d223647379152df9213b08a02@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <7DDD1353-96FC-4E70-8427-AA9C6F499232@vigilsec.com>
In-Reply-To: <7DDD1353-96FC-4E70-8427-AA9C6F499232@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.116.59]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/er4VNJ_7X4fEbP2YBwpMVt0PNk0>
Subject: Re: [Cfrg] Message Digest Algorithm Choice for CMS with Ed448
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 18:30:46 -0000

> It seems that SHA3-512 would be a good choice to avoid having to implement
> more that one message digest algorithm to generate the signature or
> validate it.

Let's rephrase:  Any argument *against* SHA3-512?

(yes, jetlag stinks:)