Last Call Review of draft-ietf-dnsop-zoneversion-07
review-ietf-dnsop-zoneversion-07-artart-lc-levine-2024-06-09-00

Request Review of draft-ietf-dnsop-zoneversion
Requested revision No specific revision (document currently at 11)
Type IETF Last Call Review
Team ART Area Review Team (artart)
Deadline 2024-06-11
Requested 2024-05-28
Authors Hugo Salgado , Mauricio Vergara Ereche , Duane Wessels
I-D last updated 2024-10-11 (Latest revision 2024-07-23)
Completed reviews Dnsdir IETF Last Call review of -08 by Nicolai Leymann (diff)
Secdir IETF Last Call review of -06 by Shawn M Emery (diff)
Opsdir IETF Last Call review of -06 by Dan Romascanu (diff)
Artart IETF Last Call review of -07 by John R. Levine (diff)
Dnsdir IETF Last Call review of -02 by Nicolai Leymann (diff)
Dnsdir IETF Last Call review of -09 by Nicolai Leymann (diff)
Dnsdir IETF Last Call review of -10 by Nicolai Leymann (diff)
Assignment Reviewer John R. Levine
State Completed
Request IETF Last Call review on draft-ietf-dnsop-zoneversion by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/hSrOL5234XcqTSOTQZNWrpapCh8
Reviewed revision 07 (document currently at 11)
Result Ready w/nits
Completed 2024-06-09
review-ietf-dnsop-zoneversion-07-artart-lc-levine-2024-06-09-00
This draft is ready to go.  The recent revisions to the label count are
adequately clear and the rest seems straightforward.

I wonder about the paragraph "A name server MUST ignore any non-empty
ZONEVERSION payload data that might be present in the query message."  It's not
wrong, but why call out this one particular error and not others like multiple
ZONEVERSION options?  I'd take it out and leave the response to ill-formed
queries undefined, or else be more general and say a server MUST ignore invalid
ZONEVERSION options.