[DNSOP] Opsdir last call review of draft-ietf-dnsop-zoneversion-06
Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 07 June 2024 08:35 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 8562FC18DB85; Fri, 7 Jun 2024 01:35:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171774931553.9697.12934746638461600829@ietfa.amsl.com>
Date: Fri, 07 Jun 2024 01:35:15 -0700
Message-ID-Hash: LNWAALSNMMIFQK65UJXJ3T72XUOMFQ6G
X-Message-ID-Hash: LNWAALSNMMIFQK65UJXJ3T72XUOMFQ6G
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, dromasca@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Dan Romascanu <dromasca@gmail.com>
Subject: [DNSOP] Opsdir last call review of draft-ietf-dnsop-zoneversion-06
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ig29oowNmskp7yds6L-03UwEQiU>
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: Dan Romascanu Review result: Ready This document aims Informational RFC status. It defines an DNS ZONEVERSION option (as per RFC 6891) which is a way for DNS clients to request, and for authoritative DNS servers to provide, information regarding the version of the zone from which a response is generated. This seems a useful extension, as including zone version data in a response simplifies and improves the quality of debugging and and diagnostics since the version and the data are provided atomically. This can be especially useful for zones and DNS providers that leverage IP anycast or multiple backend systems. The document seems useful for operators and I would recommend reading and understanding its content. It is READY from an operational point of view.
- [DNSOP] Opsdir last call review of draft-ietf-dns… Dan Romascanu via Datatracker