Protocol Action: 'Negative Caching of DNS Resolution Failures' to Proposed Standard (draft-ietf-dnsop-caching-resolution-failures-08.txt)

The IESG <iesg-secretary@ietf.org> Thu, 21 September 2023 22:01 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: Protocol Action: 'Negative Caching of DNS Resolution Failures' to Proposed Standard (draft-ietf-dnsop-caching-resolution-failures-08.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, andrew@depht.com, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-caching-resolution-failures@ietf.org, rfc-editor@rfc-editor.org, warren@kumari.net
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169533368569.13369.2832659995791399831@ietfa.amsl.com>
Date: Thu, 21 Sep 2023 15:01:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FyupseKXgA6ozElvG_PVxzsHKXc>

The IESG has approved the following document:
- 'Negative Caching of DNS Resolution Failures'
(draft-ietf-dnsop-caching-resolution-failures-08.txt) as Proposed Standard

This document is the product of the Domain Name System Operations Working
Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-caching-resolution-failures/

Technical Summary

In the DNS, resolvers employ caching to reduce both latency for end
users and load on authoritative name servers. The process of
resolution may result in one of three types of responses: (1) a
response containing the requested data; (2) a response indicating the
requested data does not exist; or (3) a non-response due to a
resolution failure in which the resolver does not receive any useful
information regarding the data's existence. This document concerns
itself only with the third type.

RFC 2308 specifies requirements for DNS negative caching. There,
caching of type (1) and (2) responses is mandatory and caching of
type (3) responses is optional. This document updates RFC 2308 to
require negative caching for DNS resolution failures.

RFC 4035 allows DNSSEC validation failure caching. This document
updates RFC 4035 to require caching for DNSSEC validation failures.

RFC 4697 prohibits aggressive requerying for NS records at a failed
zone's parent zone. This document updates RFC 4697 to expand this
requirement to all query types and to all ancestor zones.

Working Group Summary

While there was not much discussion on the document, what discussion there was was supportive. The authors did a good job of addressing comments, and so there was minimal / no drama...

Document Quality

This document specifies a behavior ("cache resolution failures, yo!") rather than an exact specification. A number of implementations now follow this behavior, but only one (ISC BIND) is documented to do so in the draft.

Personnel

Andrew McConachie is DS!
Warren "Ace" Kumari is RAD!!!!1!!1!1

Protocol Action: 'Negative Caching of DNS Resolut… The IESG