[DNSOP] Artart last call review of draft-ietf-dnsop-zoneversion-07

John Levine via Datatracker <noreply@ietf.org> Sun, 09 June 2024 14:13 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Levine via Datatracker <noreply@ietf.org>
To: art@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171794241870.3247.17055653550600432692@ietfa.amsl.com>
Date: Sun, 09 Jun 2024 07:13:38 -0700
Message-ID-Hash: PS2JU7GZ6VKAXWE3AA5P5EBFLU5HBPR7
CC: dnsop@ietf.org, draft-ietf-dnsop-zoneversion.all@ietf.org, last-call@ietf.org
Reply-To: John Levine <johnl@taugh.com>
Subject: [DNSOP] Artart last call review of draft-ietf-dnsop-zoneversion-07
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RiS-F_NGxyRekLgz_dplbMdX9tk>

Reviewer: John Levine
Review result: Ready with Nits

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.

[DNSOP] Artart last call review of draft-ietf-dns… John Levine via Datatracker
[DNSOP] Re: Artart last call review of draft-ietf… Wessels, Duane