[lamps] Need SHA-3 text strings, add to draft-ietf-lamps-pkix-shake?

Sean Leonard <dev+ietf@seantek.com> Thu, 28 March 2019 17:05 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBD3120283 for <spasm@ietfa.amsl.com>; Thu, 28 Mar 2019 10:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WImdy0SVNxB5 for <spasm@ietfa.amsl.com>; Thu, 28 Mar 2019 10:05:36 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2183C1200EF for <spasm@ietf.org>; Thu, 28 Mar 2019 10:05:33 -0700 (PDT)
X-Originating-IP: 31.133.138.32
Received: from dhcp-8a20.meeting.ietf.org (dhcp-8a20.meeting.ietf.org [31.133.138.32]) (Authenticated sender: sean@seantek.org) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 130A61C0019 for <spasm@ietf.org>; Thu, 28 Mar 2019 17:05:31 +0000 (UTC)
From: Sean Leonard <dev+ietf@seantek.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <47E88B72-7ADF-4AB1-9677-E94389016851@seantek.com>
Date: Thu, 28 Mar 2019 18:05:30 +0100
To: SPASM <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/MZcJcuPs239gXosvxgdgmzEAvnk>
Subject: [lamps] Need SHA-3 text strings, add to draft-ietf-lamps-pkix-shake?
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2019 17:05:38 -0000

I have a need to identify SHA-3 algorithms by text strings. For example: SHA3-256, SHA3-512, etc.

There is an IANA registry aptly named “Hash Function Textual Names”: <https://www.iana.org/assignments/hash-function-text-names/hash-function-text-names.xhtml>.

How do I add the SHA-3 algorithms to Hash Function Textual Names? The registry says that registration requires a standards-track RFC that updates RFC 3279. Yep, that’s what it says.

draft-turner-lamps-adding-sha3-to-pkix
became
draft-ietf-lamps-pkix-shake

which is now in last call. But draft-ietf-lamps-pkix-shake says “Four other hash function instances, SHA3-224, SHA3-256, SHA3-384, and SHA3-512 are also defined but are out of scope for this document.” So I am not sure where to go for this request. Suggestions? And what about adding textual names for SHAKE-128 and SHAKE-256? (Which are not in-scope for my particular need, but there there nonetheless.)

Thanks,

Sean