Re: [openpgp] SHA3 algorithm ids.

Derek Atkins <derek@ihtfp.com> Mon, 10 August 2015 15:22 UTC

Return-Path: <derek@ihtfp.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D4E1B36D4 for <openpgp@ietfa.amsl.com>; Mon, 10 Aug 2015 08:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
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 fzKkDlz2jM-n for <openpgp@ietfa.amsl.com>; Mon, 10 Aug 2015 08:22:36 -0700 (PDT)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:4830:143:1::3a11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888021B36D0 for <openpgp@ietf.org>; Mon, 10 Aug 2015 08:22:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 44F94E2036; Mon, 10 Aug 2015 11:22:34 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 04976-03; Mon, 10 Aug 2015 11:22:32 -0400 (EDT)
Received: from securerf.ihtfp.org (unknown [IPv6:fe80::ea2a:eaff:fe7d:235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail2.ihtfp.org (Postfix) with ESMTPS id 01988E2034; Mon, 10 Aug 2015 11:22:31 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1439220152; bh=vSlLCXjNV8VfTz6UzClSCl40kYGRZruLwuzAQeJfLE8=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=nn6XOo/kaRuqxZ+ICMrWTJqmUHXp76Ge5IqOtOdkIi5tTPi7HqaXujsFHIRLyCbot 3lR8kjMe00niJuwp5JwLyhhTnOl5i+Tq9wEmhmLMt3gRPzZZm9tTQ3oeI2jLEc0ykl 2WOsCCOIFXl2glmVmX101dYqFgQlrqETSSXtlBqU=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.14.8/8.14.8/Submit) id t7AFMVKJ014339; Mon, 10 Aug 2015 11:22:31 -0400
From: Derek Atkins <derek@ihtfp.com>
To: ianG <iang@iang.org>
References: <87y4hmi19i.fsf@vigenere.g10code.de> <7540C7A9-2830-4A63-8310-B684796DA279@nohats.ca> <55C681FC.9010100@iang.org>
Date: Mon, 10 Aug 2015 11:22:31 -0400
In-Reply-To: <55C681FC.9010100@iang.org> (iang@iang.org's message of "Sat, 08 Aug 2015 23:26:04 +0100")
Message-ID: <sjma8tztbgo.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/6ajTghbbOeH4Vr9aBJ3i__EFVWM>
Cc: openpgp@ietf.org
Subject: Re: [openpgp] SHA3 algorithm ids.
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2015 15:22:38 -0000

ianG <iang@iang.org>; writes:

> One would be good.  Suits me to go for the longest one.

Possibly two...  But the SHA3 competition has shown that SHA2 is pretty
darn good...

> How about this:
>
>
>
>>>       ID           Algorithm                             Text Name
>>>       --           ---------                             ---------
>
> snip
>
>>>       12         - RESERVED
>>>       13         - RESERVED
>>>       14         - RESERVED
>>>       15         - SHA3-512 [FIPS202]                    "SHA3-512"
>
>
>
> And while we're at it, can we add DEPRECATED to all the rest except
> SHA(2)512 ?

I see no reason to deprecate SHA2-256.  But I'm fine with all the rest.

> iang

-derek
-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant