Last Call Review of draft-ietf-kitten-pkinit-alg-agility-04
review-ietf-kitten-pkinit-alg-agility-04-opsdir-lc-bradner-2019-02-17-00

Request Review of draft-ietf-kitten-pkinit-alg-agility
Requested rev. no specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2019-02-17
Requested 2019-02-03
Draft last updated 2019-02-17
Completed reviews Opsdir Last Call review of -04 by Scott Bradner (diff)
Secdir Last Call review of -04 by Takeshi Takahashi (diff)
Genart Last Call review of -05 by Christer Holmberg (diff)
Genart Telechat review of -06 by Christer Holmberg (diff)
Assignment Reviewer Scott Bradner
State Completed
Review review-ietf-kitten-pkinit-alg-agility-04-opsdir-lc-bradner-2019-02-17
Reviewed rev. 04 (document currently at 08)
Review result Has Nits
Review completed: 2019-02-17

Review
review-ietf-kitten-pkinit-alg-agility-04-opsdir-lc-bradner-2019-02-17

This is an OPS-DIR review of PKINIT Algorithm Agility (draft-ietf-kitten-pkinit-alg-agility).  This ID updates PKINIT following the guidelines in BCP 201 to make it algorithm agile and to expose acceptable algorithms.

This is a very well written clear document.  I do not find any operational issues with the document except that the document could use a section on interoperability (old server-new client, new server-old client).

There are a few words about the topic deep in section 6 about the supportedKDFs field but I do not see a general discussion or a discussion about the kdf field. The text about the supportedKDFs field could be moved to a new section and each of the old/new combinations could be addressed.  I see this as an operational issue because compatibility issues are a frequent source of operational headaches.