[Int-dir] Intdir telechat review of draft-ietf-dnsop-dns-error-reporting-07

Carlos Pignataro via Datatracker <noreply@ietf.org> Sat, 09 December 2023 14:43 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Pignataro via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: dnsop@ietf.org, draft-ietf-dnsop-dns-error-reporting.all@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170213298005.1168.789324667123128986@ietfa.amsl.com>
Reply-To: Carlos Pignataro <cpignata@gmail.com>
Date: Sat, 09 Dec 2023 06:43:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/iWfBPsmDEXyS3duvcdSH2VQlTZ0>
Subject: [Int-dir] Intdir telechat review of draft-ietf-dnsop-dns-error-reporting-07

Reviewer: Carlos Pignataro
Review result: Ready with Nits

draft-ietf-dnsop-dns-error-reporting

Hi!

I was assigned a review of draft-ietf-dnsop-caching-resolution-failures, for an
INTDIR Telechat Review.

Review of       draft-ietf-dnsop-dns-error-reporting
Type    Telechat Review
Team    Internet Area Directorate (intdir)
Deadline        2023-12-09
Reviewer        Carlos Pignataro

In general, I found the document to be useful and clear, effectively organzied,
and easy to follow for an implementor.

Please find below only some minor nits for consideration:

1. Append a comma after "i.e.".

2. Change "Well known" to "Well-known".

3. Capitalization of "RRset" vs. "RRSet", although RFC 8499 mentions both.

4. Should RFC 2199 be a Normative reference instead of Informative?

Thanks!

Carlos.

[Int-dir] Intdir telechat review of draft-ietf-dn… Carlos Pignataro via Datatracker
Re: [Int-dir] [Ext] Intdir telechat review of dra… Roy Arends
Re: [Int-dir] [Ext] Intdir telechat review of dra… Carlos Pignataro