[DNSOP] Dnsdir last call review of draft-ietf-dnsop-zoneversion-08

Nicolai Leymann via Datatracker <noreply@ietf.org> Mon, 17 June 2024 13:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C1DC151551; Mon, 17 Jun 2024 06:37:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nicolai Leymann via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171863143515.5215.8720108541523376673@ietfa.amsl.com>
Date: Mon, 17 Jun 2024 06:37:15 -0700
Message-ID-Hash: CY5ZZRHLMNPUPRVM25NRN2UOZSY7XRIL
X-Message-ID-Hash: CY5ZZRHLMNPUPRVM25NRN2UOZSY7XRIL
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dnsop@ietf.org, draft-ietf-dnsop-zoneversion.all@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Nicolai Leymann <n.leymann@telekom.de>
Subject: [DNSOP] Dnsdir last call review of draft-ietf-dnsop-zoneversion-08
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YSw3ghVRlCdqAMFn0SDCgcYeKTg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Reviewer: Nicolai Leymann
Review result: Ready

I am the designated DNS Directorate reviewer for draft-ietf-dnsop-zoneversion.
This is the second review I am doing - my last review on the -02 version only
identified a few nits. The draft is going to be published as Informational RFC.
The document is well written and defines an EDNS option which can be used for
debugging purposes.

There was sufficient discussion on the mailing list and significant changes
were made (compared to the -02 version) in order to make it more readable.
Overall I think the document is ready for publication.