[DNSOP] Dnsdir ietf last call review of draft-ietf-dnsop-structured-dns-error-12
Matt Brown via Datatracker <noreply@ietf.org> Thu, 17 April 2025 00:02 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 50B471D627A8; Wed, 16 Apr 2025 17:02:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matt Brown via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174484817618.1482052.13324267924900266340@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Wed, 16 Apr 2025 17:02:56 -0700
Message-ID-Hash: ITDHELTQNV3LYFV2HM4OJHXJER2SBVN7
X-Message-ID-Hash: ITDHELTQNV3LYFV2HM4OJHXJER2SBVN7
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-structured-dns-error.all@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Matt Brown <ietf@mattb.net.nz>
Subject: [DNSOP] Dnsdir ietf last call review of draft-ietf-dnsop-structured-dns-error-12
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1FrxeF9j0pA5S2p8Xmb9d3hM8wI>
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>
Document: draft-ietf-dnsop-structured-dns-error Title: Structured Error Data for Filtered DNS Reviewer: Matt Brown Review result: Ready I'm the designated dnsdir reviewer for this draft. I had previously reviewed -03 back in the mists of time (aka 2023!). My concerns in that review focused on the wisdom of introducing structured data intended to be machine-readable into a field previously specified as intended to be human-readable. Specifically I was not able to understand the mechanism by which clients and servers determined when or how to apply this draft to the EXTRA-TEXT field despite several careful re-readings of the document! Those concerns were addressed in the follow-up discussion on the review with the authors and subsequent updates to the draft have added and clarified the relevant sections. The draft is now clearer in describing the intended behaviour of clients and servers to ensure there is no confusion over whether or not the EXTRA-TEXT field will be human-readable, or full of I-JSON content. The current version of the draft reads well and is much clearer to me. The other issues in the original review have also been addressed. I found no further issues to comment on and consider this ready.
- [DNSOP] Dnsdir ietf last call review of draft-iet… Matt Brown via Datatracker