Re: [lamps] Genart last call review of draft-ietf-lamps-pkix-shake-08

Russ Housley <housley@vigilsec.com> Sun, 31 March 2019 00:29 UTC

Return-Path: <housley@vigilsec.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 0B44F120044 for <spasm@ietfa.amsl.com>; Sat, 30 Mar 2019 17:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable 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 459JzeIwdsCz for <spasm@ietfa.amsl.com>; Sat, 30 Mar 2019 17:29:12 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2FB4120164 for <spasm@ietf.org>; Sat, 30 Mar 2019 17:29:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 17BCA300AE2 for <spasm@ietf.org>; Sat, 30 Mar 2019 20:04:37 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Rovh7M1WEtWR for <spasm@ietf.org>; Sat, 30 Mar 2019 20:04:31 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id DB2B3300AD5; Sat, 30 Mar 2019 20:04:30 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <155393972295.3950.3582710869606616692@ietfa.amsl.com>
Date: Sat, 30 Mar 2019 20:21:20 -0400
Cc: IETF Gen-ART <gen-art@ietf.org>, spasm@ietf.org, IETF <ietf@ietf.org>, draft-ietf-lamps-pkix-shake.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3508ACC-5F76-4205-B380-FC4D35A4496E@vigilsec.com>
References: <155393972295.3950.3582710869606616692@ietfa.amsl.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/6Ks-GUnwnb6K-CnnrYdTkpi5w48>
Subject: Re: [lamps] Genart last call review of draft-ietf-lamps-pkix-shake-08
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: Sun, 31 Mar 2019 00:29:14 -0000


> On Mar 30, 2019, at 5:55 AM, Joel Halpern via Datatracker <noreply@ietf.org> wrote:
> 
> Reviewer: Joel Halpern
> Review result: Almost Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-lamps-pkix-shake-08
> Reviewer: Joel Halpern
> Review Date: 2019-03-30
> IETF LC End Date: 2019-04-10
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: This document is almost ready for publication as a Proposed Standard
> 
> Major issues:
>    One of the key points of this RFC seems to be to assign the identifiers for
>    the use of the two SHAKE variants.  It is thus confusing that the
>    identifiers end with "TBD", and thus are not defined in this document.

They will be assigned by NIST once they are sure that these are the identifiers that we want.  This is much the same as we do when IANA is ti assign the identifier.

Russ