Skip to main content

Last Call Review of draft-ietf-dnsop-rfc5933-bis-10
review-ietf-dnsop-rfc5933-bis-10-secdir-lc-sethi-2022-10-09-00

Request Review of draft-ietf-dnsop-rfc5933-bis
Requested revision No specific revision (document currently at 14)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2022-10-19
Requested 2022-10-05
Authors Boris Makarenko , Vasily Dolmatov
I-D last updated 2022-10-09
Completed reviews Genart Last Call review of -10 by Roni Even (diff)
Secdir Last Call review of -10 by Mohit Sethi (diff)
Dnsdir Last Call review of -10 by Jim Reid (diff)
Dnsdir Telechat review of -12 by Scott Rose (diff)
Dnsdir Telechat review of -13 by Jim Reid (diff)
Assignment Reviewer Mohit Sethi
State Completed
Request Last Call review on draft-ietf-dnsop-rfc5933-bis by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/9x5kDZn7SjE2OcBBplVETZWrkyo
Reviewed revision 10 (document currently at 14)
Result Ready
Completed 2022-10-09
review-ietf-dnsop-rfc5933-bis-10-secdir-lc-sethi-2022-10-09-00
I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. Document
editors and WG chairs should treat these comments just like any other last-call
comments.

This document updates the old GOST digital signature and hash algorithm with
the new ones for usage in DNSKEY, RRSIG, and DS resource records.

Section 8 explains how the paragraph describing the state of GOST algorithms in
section 3.1 of RFC 8624 is updated. Why is section 3.3 of RFC 8624 containing
the text "GOST R 34.11-2012 has not been standardized for use in DNSSEC." not
updated in a similar fashion?