Skip to main content

Last Call Review of draft-ietf-dnsop-rfc8624-bis-07
review-ietf-dnsop-rfc8624-bis-07-genart-lc-mishra-2025-03-08-00

Request Review of draft-ietf-dnsop-rfc8624-bis
Requested revision No specific revision (document currently at 09)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2025-03-06
Requested 2025-02-20
Authors Wes Hardaker , Warren Kumari
I-D last updated 2025-04-03 (Latest revision 2025-04-03)
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
Dnsdir Telechat review of -09 by Nicolai Leymann
Secdir Telechat review of -09 by Magnus Nyström
Assignment Reviewer Gyan Mishra
State Completed
Request IETF Last Call review on draft-ietf-dnsop-rfc8624-bis by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/3b0x_tiI1ETkMX2sMrk2yVi5ZEk
Reviewed revision 07 (document currently at 09)
Result Ready
Completed 2025-03-08
review-ietf-dnsop-rfc8624-bis-07-genart-lc-mishra-2025-03-08-00
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://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-dnsop-rfc8624-bis-??
Reviewer: Gyan Mishra
Review Date: 2025-03-08
IETF LC End Date: 2025-03-16
IESG Telechat date: Not scheduled for a telechat

Summary:

The DNSSEC protocol makes use of various cryptographic algorithms to provide
authentication of DNS data and proof of non-existence. To ensure
interoperability between DNS resolvers and DNS authoritative servers, it is
necessary to specify both a set of algorithm implementation requirements and
usage guidelines to ensure that there is at least one algorithm that all
implementations support. This document updates RFC8624 by moving the canonical
source of algorithm implementation requirements and usage guidance for DNSSEC
from RFC8624 to an IANA registry. This is done both to allow the list to be
more easily updated, and to allow the list to be more easily referenced. Future
extensions to this registry can be made under new, incremental update RFCs.

The document does not change the status (MUST, MAY, RECOMMENDED, etc) of any of
the algorithms listed in RFC8624; that is the work of future documents.

I reviewed the latest draft and believe it’s ready for publication.

Major issues:
None

Minor issues:
None

Nits/editorial comments:
None