Hello everyone,

it seems that we now have two drafts about the same topic - this new one and draft-moura-dnsop-negative-cache-loop.

Perhaps authors could discuss if they are in agreement and could pick one?

Petr Špaček  @  Internet Systems Consortium



On 14. 01. 22 19:14, Wessels, Duane wrote:
Dear DNSOP,

In light of some recent events and research, we feel that it could be beneficial to strengthen the requirements around negative caching of DNS resolution failures. Please see the recently submitted Internet Draft referenced below and let us know if you have any feedback.

DW


Begin forwarded message:

*From: *<[email protected] <mailto:[email protected]>>
*Subject: **[EXTERNAL] New Version Notification for draft-dwmtwc-dnsop-caching-resolution-failures-00.txt*
*Date: *January 13, 2022 at 1:28:00 PM PST
*To: *Duane Wessels <[email protected] <mailto:[email protected]>>, Matthew Thomas <[email protected] <mailto:[email protected]>>, William Carroll <[email protected] <mailto:[email protected]>>

A new version of I-D, draft-dwmtwc-dnsop-caching-resolution-failures-00.txt
has been successfully submitted by William Carroll and posted to the
IETF repository.

Name:draft-dwmtwc-dnsop-caching-resolution-failures
Revision:00
Title:Negative Caching of DNS Resolution Failures
Document date:2022-01-13
Group:Individual Submission
Pages:13
URL: https://www.ietf.org/archive/id/draft-dwmtwc-dnsop-caching-resolution-failures-00.txt <https://www.ietf.org/archive/id/draft-dwmtwc-dnsop-caching-resolution-failures-00.txt> Status: https://datatracker.ietf.org/doc/draft-dwmtwc-dnsop-caching-resolution-failures/ <https://datatracker.ietf.org/doc/draft-dwmtwc-dnsop-caching-resolution-failures/> Htmlized: https://datatracker.ietf.org/doc/html/draft-dwmtwc-dnsop-caching-resolution-failures <https://datatracker.ietf.org/doc/html/draft-dwmtwc-dnsop-caching-resolution-failures>


Abstract:
  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.




The IETF Secretariat

_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to