Maybe a note that the assignment will take place once the drafts are
approved, and that the RFC should coordiante with the authors and NIST
on this? (I presume we have done this before, and we do not have the
problem we have in some other cases of "no number until RFC" / "no RFC
until number".)
Yours,
Joel
On 3/31/19 1:21 AM, Russ Housley wrote:
On Mar 30, 2019, at 5:55 AM, Joel Halpern via Datatracker <noreply@xxxxxxxx> 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
