Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Fri, 06 December 2019 02:00 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: tjw.ietf@gmail.com, dnsop-chairs@ietf.org, dnsop@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, draft-ietf-dnsop-no-response-issue@ietf.org, warren@kumari.net
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <157559763911.16433.13149772616705852561.idtracker@ietfa.amsl.com>
Date: Thu, 05 Dec 2019 18:00:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/V-4RJ5XLl8KEuE46xNyv0V9ElMM>

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'A Common Operational Problem
in DNS Servers - Failure To Communicate.'
<draft-ietf-dnsop-no-response-issue-14.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2019-12-19. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract

The DNS is a query / response protocol. Failing to respond to
queries, or responding incorrectly, causes both immediate operational
problems and long term problems with protocol development.

This document identifies a number of common kinds of queries to which
some servers either fail to respond or else respond incorrectly.
This document also suggests procedures for zone operators to apply to
identify and remediate the problem.

The document does not look at the DNS data itself, just the structure
of the responses.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-no-response-issue/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-no-response-issue/ballot/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
rfc6840: Clarifications and Implementation Notes for DNS Security (DNSSEC) (Proposed Standard - IETF stream)
rfc3225: Indicating Resolver Support of DNSSEC (Proposed Standard - IETF stream)
rfc7766: DNS Transport over TCP - Implementation Requirements (Proposed Standard - IETF stream)
rfc4035: Protocol Modifications for the DNS Security Extensions (Proposed Standard - IETF stream)

Last Call: <draft-ietf-dnsop-no-response-issue-14… The IESG