[openpgp] SHA3 algorithm ids.

Werner Koch <wk@gnupg.org> Sat, 08 August 2015 09:25 UTC

Return-Path: <wk@gnupg.org>
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 C0CF81AC414 for <openpgp@ietfa.amsl.com>; Sat, 8 Aug 2015 02:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] 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 opbFRcz1e5gG for <openpgp@ietfa.amsl.com>; Sat, 8 Aug 2015 02:25:31 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6DDD1AC413 for <openpgp@ietf.org>; Sat, 8 Aug 2015 02:25:31 -0700 (PDT)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.80 #2 (Debian)) id 1ZO0Nd-0007zi-43 for <openpgp@ietf.org>; Sat, 08 Aug 2015 11:25:29 +0200
Received: from wk by vigenere.g10code.de with local (Exim 4.84 #3 (Debian)) id 1ZO0Jl-0007mj-Km for <openpgp@ietf.org>; Sat, 08 Aug 2015 11:21:29 +0200
From: Werner Koch <wk@gnupg.org>
To: openpgp@ietf.org
Organisation: g10 Code GmbH
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
OpenPGP: id=F2AD85AC1E42B367; url=finger:wk@g10code.com
Mail-Followup-To: openpgp@ietf.org
Date: Sat, 08 Aug 2015 11:21:29 +0200
Message-ID: <87y4hmi19i.fsf@vigenere.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/2C5jQNKcnUZZUzh84s0Di-GYKV0>
Subject: [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: Sat, 08 Aug 2015 09:25:33 -0000

Hi!

Now that an official SHA3 specs has been published I would like to see
algorithm ids assigned.  Although it is some time until we can publish
rfc-4880bis, it would be useful to agree on the algorithm ids now.
This would be helpful for experimental implementations.  Thus what about
this new table with the SHA2 drop in replacements:

      ID           Algorithm                             Text Name
      --           ---------                             ---------
      1          - MD5 [HAC]                             "MD5"
      2          - SHA-1 [FIPS180]                       "SHA1"
      3          - RIPE-MD/160 [HAC]                     "RIPEMD160"
      4          - Reserved
      5          - Reserved
      6          - Reserved
      7          - Reserved
      8          - SHA256 [FIPS180]                      "SHA256"
      9          - SHA384 [FIPS180]                      "SHA384"
      10         - SHA512 [FIPS180]                      "SHA512"
      11         - SHA224 [FIPS180]                      "SHA224"
      12         - SHA3-224 [FIPS202]                    "SHA3-224"
      13         - SHA3-256 [FIPS202]                    "SHA3-256"
      14         - SHA3-384 [FIPS202]                    "SHA3-384"
      15         - SHA3-512 [FIPS202]                    "SHA3-512"
      100 to 110 - Private/Experimental algorithm

Note that I ordered SHA3-224 first; when we did SHA2 we forgot about 224
and thus it ended up out of order.

I am not sure about the text name.  Is a dash okay (cf. armor header)?

The OIDS are:

   The hexadecimal representations for the
   currently defined hash algorithms are as follows:
    
     [...]  

     - SHA3-224:   0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07
     - SHA3-256:   0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x08
     - SHA3-384:   0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x09
     - SHA3-512:   0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x0a

   The ASN.1 Object Identifiers (OIDs) are as follows:

     [...]

     - SHA3-224:   2.16.840.1.101.3.4.2.7
     - SHA3-256:   2.16.840.1.101.3.4.2.8
     - SHA3-384:   2.16.840.1.101.3.4.2.9
     - SHA3-512:   2.16.840.1.101.3.4.2.10

   The full hash prefixes for these are as follows:

       [...]

       SHA3-224:   0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
                   0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
                   0x00, 0x04, 0x40

       SHA3-256:   0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
                   0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
                   0x00, 0x04, 0x40

       SHA3-384:   0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
                   0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
                   0x00, 0x04, 0x40

       SHA3-512:   0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
                   0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
                   0x00, 0x04, 0x40



Shalom-Salam,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.