Last Call Review of draft-ietf-dnsop-rfc8624-bis-06
review-ietf-dnsop-rfc8624-bis-06-artart-lc-leiba-2025-02-21-00

Request Review of draft-ietf-dnsop-rfc8624-bis
Requested revision No specific revision (document currently at 13)
Type IETF Last Call Review
Team ART Area Review Team (artart)
Deadline 2025-03-06
Requested 2025-02-20
Authors Wes Hardaker , Warren Kumari
I-D last updated 2025-11-30 (Latest revision 2025-06-04)
Completed reviews Dnsdir IETF Last Call review of -06 by Nicolai Leymann (diff)
Artart IETF Last Call review of -06 by Barry Leiba (diff)
Secdir IETF Last Call review of -07 by Magnus Nyström (diff)
Genart IETF Last Call review of -07 by Gyan Mishra (diff)
Dnsdir IETF Last Call review of -07 by Ted Lemon (diff)
Opsdir IETF Last Call review of -09 by Nabeel Cocker (diff)
Dnsdir Telechat review of -09 by Nicolai Leymann (diff)
Secdir Telechat review of -09 by Magnus Nyström (diff)
Assignment Reviewer Barry Leiba
State Completed
Request IETF Last Call review on draft-ietf-dnsop-rfc8624-bis by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/Ye5njRLXNyuNs1vADV_wmwovThw
Reviewed revision 06 (document currently at 13)
Result Ready
Completed 2025-02-21
review-ietf-dnsop-rfc8624-bis-06-artart-lc-leiba-2025-02-21-00
Fine and useful; excellent.

Just the nittiest nit of nittiness in Section 1.2:

   By the time a DNSSEC cryptographic algorithm is made mandatory-to-
   implement
…and…
   newly introduced algorithms will
   become mandatory-to-implement in the future
…and…
   Similarly, an algorithm that has not been
   mentioned as mandatory-to-implement

In these, “mandatory to implement” is not a modifier, so shouldn’t be hyphenated.