[DNSOP] Opsdir last call review of draft-ietf-dnsop-extended-error-14

Scott Bradner via Datatracker <noreply@ietf.org> Tue, 31 March 2020 13:23 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-extended-error.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158566101271.28515.7650367576079262223@ietfa.amsl.com>
Reply-To: Scott Bradner <sob@sobco.com>
Date: Tue, 31 Mar 2020 06:23:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dnVb-738pI9FlL7Lm3bmWT_b3xo>
Subject: [DNSOP] Opsdir last call review of draft-ietf-dnsop-extended-error-14

Reviewer: Scott Bradner
Review result: Ready

This is an OPS-DIR review of Extended DNS Errors
<draft-ietf-dnsop-extended-error>

This ID defines a use of the EDNS0 extension mechanism that can be used by a
DNS resolver to provide additional detail about DNS lookup issues as well as
defining an initial set of 24 codes that can be used to provide specific
failure reasons.

The document is clearly written. (But I expect that not all of the
acknowledgements should be retained in the RFC)

>From an operations point of view, the additional information provided by these
error codes will be quite helpful in diagnosing DNS errors. But, as with most
error information, it will be difficult to present the error information in a
way that will make sense to the average Internet user, thus this information
may be mostly useful to IT support staff.

[DNSOP] Opsdir last call review of draft-ietf-dns… Scott Bradner via Datatracker
Re: [DNSOP] Opsdir last call review of draft-ietf… Warren Kumari