[DNSOP] draft-ietf-dnsop-structured-dns-error-15 ietf last call Genart review

Stewart Bryant via Datatracker <noreply@ietf.org> Mon, 12 May 2025 20:51 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174708311011.1668744.16084393961139511302@dt-datatracker-58d4498dbd-6gzjf>
Date: Mon, 12 May 2025 13:51:50 -0700
Message-ID-Hash: C6R7GSW4QNAVH67YVURKFPABJTRET7NN
CC: dnsop@ietf.org, draft-ietf-dnsop-structured-dns-error.all@ietf.org, last-call@ietf.org
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
Subject: [DNSOP] draft-ietf-dnsop-structured-dns-error-15 ietf last call Genart review
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iFvEVuYgKpXhVOUTO9yBB0oZviU>

Document: draft-ietf-dnsop-structured-dns-error
Title: Structured Error Data for Filtered DNS
Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

I apologies for the lateness of the review and hope that it is still helpful.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-dnsop-structured-dns-error-??
Reviewer: Stewart Bryant
Review Date: 2025-05-12
IETF LC End Date: 2025-04-28
IESG Telechat date: Not scheduled for a telechat

Summary:From a GenART perspective this is a well written text with just a
couple of minor comments at a NITs level.

Major issues: None

Minor issues: None

Nits/editorial comments:

SB> ID Nits picks up the following which should be addressed at some point.

  == There is 1 instance of lines with non-ascii characters in the document.

======

  ** Downref: Normative reference to an Informational RFC: RFC 4949
SB> For info this is in the downref registry and is OK. Perhaps the tools team
could be asked to make this check automatically to avoid reviewers needing to
manually check.
========

  ** Obsolete normative reference: RFC 7159 (Obsoleted by RFC 8259)

SB> I am not sure why RFC 7159 is listed as normative as it is only used as in
a narrative explanation of document history

[DNSOP] draft-ietf-dnsop-structured-dns-error-15 … Stewart Bryant via Datatracker