Last Call Review of draft-ietf-lamps-pkix-shake-08
review-ietf-lamps-pkix-shake-08-opsdir-lc-zhou-2019-04-09-00

Request Review of draft-ietf-lamps-pkix-shake
Requested rev. no specific revision (document currently at 15)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2019-04-10
Requested 2019-03-27
Draft last updated 2019-04-09
Completed reviews Secdir Last Call review of -08 by Yoav Nir (diff)
Genart Last Call review of -08 by Joel Halpern (diff)
Opsdir Last Call review of -08 by Tianran Zhou (diff)
Genart Telechat review of -11 by Joel Halpern (diff)
Assignment Reviewer Tianran Zhou
State Completed
Review review-ietf-lamps-pkix-shake-08-opsdir-lc-zhou-2019-04-09
Reviewed rev. 08 (document currently at 15)
Review result Has Issues
Review completed: 2019-04-09

Review
review-ietf-lamps-pkix-shake-08-opsdir-lc-zhou-2019-04-09

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

Document reviewed: draft-ietf-lamps-pkix-shake-08
Intended Status:  Standards Track

Summary:
In general, this document is clear to me. I did not see any special operational or network management related issue.
It's almost ready to be published. There are some issues and nits.

Issues:
The normative and informative reference in this draft are not clear to me. 
I think that [RFC8017](Informational) and [RFC8174](BCP) should not be normative reference.
And why some standard tack RFC are listed in informative reference?

Editorial:
line 102: redundand -> redundant
line 126,129: Deterministric -> Deterministic
line 314: algorithsm -> algorithms
line 378: subtitutions -> substitutions
line 763,777: Determinstic -> Deterministic