[Add] Dnsdir telechat review of draft-ietf-add-resolver-info-11

Jim Reid via Datatracker <noreply@ietf.org> Fri, 15 March 2024 14:05 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jim Reid via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
Cc: add@ietf.org, draft-ietf-add-resolver-info.all@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171051153591.20015.18362424985743292212@ietfa.amsl.com>
Reply-To: Jim Reid <jim@rfc1035.com>
Date: Fri, 15 Mar 2024 07:05:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/3ssHevKwNHvDyDfOzXpAN0Tfh7M>
Subject: [Add] Dnsdir telechat review of draft-ietf-add-resolver-info-11

Reviewer: Jim Reid
Review result: Almost Ready

The authors have resolved my earlier comments in the most recent version of the
I-D. Thanks. I have almost nothing to add. The doc is just about complete and
IMO does not need further substantive work.

However the use of "or" in "(e.g., Extended Error Reporting [RFC8914] or
encrypted DNS)" doesn't scan properly since the examples are part of a list.
[Using "or" here seems to imply a binary choice.] I suppose fixing this can be
left for the RFC Editor or the IETF Grammar/Style Police.

[Add] Dnsdir telechat review of draft-ietf-add-re… Jim Reid via Datatracker