This draft has been updated based on recent feedback. The primary change is that the new version is less prescriptive about how the resolution failure negative cache should work. e.g., rather than saying "Resolution failures MUST be cached against the specific query tuple…” it now says "Resolvers MUST implement a cache for resolution failures” but leaves the details to the implementation.
We welcome further discussion and input. DW > On Sep 12, 2022, at 3:18 PM, internet-dra...@ietf.org wrote: > > Caution: This email originated from outside the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Domain Name System Operations WG of the IETF. > > Title : Negative Caching of DNS Resolution Failures > Authors : Duane Wessels > William Carroll > Matthew Thomas > Filename : draft-ietf-dnsop-caching-resolution-failures-01.txt > Pages : 14 > Date : 2022-09-12 > > 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 datatracker status page for this draft is: > https://secure-web.cisco.com/1Tj_cyWFGUKz4YiwF0fnptDrtAqXWa3M5rS8wHsuQCrQptkzDaKaH6AWjPBY_s16axtl7VLXOVEb9P7rzXsDwHI0XVUgdeHs4Ct1cy0BTwTxeEzdzZrg4b5QYSwl-PEJnI06bCFbF7ZW3h_f6SU5_8sabBLoC6dCbfXTMYy3fDB1Wf1XvMuNGSNCCW0OUt01APnljOZTthD1IKenynQ_JrDrP9WsvUZEu9iHS86Zd8xlRfuji57W7aD2ZZtO8lEUdCl9vWYoeCDNO_nCExB2YeQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dnsop-caching-resolution-failures%2F > > There is also an htmlized version available at: > https://secure-web.cisco.com/1WFFL6urpB2je9kE3AoDDEzwQHDjXZY3xOlZQ8KwFKQW2kmo0hq_-YOLhTYSmT8I5fBPbxkc_dtNIB4K9WSJ3DZ38qALxhUO_c_xgylCWK1yQ7LAo9Ew1SiV6GQQMPuAeVTOg3Llp6mR47e8pUh7QAL9WPWrkof5j46o03CsB0ZDUb4I33Y8Syn2e8Qx0KEKtm9_jTiWexL8PwOXWHV00DIYMSVpGMNqHpBpOHnNStnNNY4pEG5AZSX_PFn2gFMF4ngFZcy3KNiKWZwmmoa94EQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dnsop-caching-resolution-failures-01 > > A diff from the previous version is available at: > https://secure-web.cisco.com/1dQmPkTAo638e9_FNBF4C67-9DmW45qKHp2-6yGP_nhj3X_dnrrbWNiovzA_BDmV64gDGpXGQddgbXrsaexx1NdzUiaeIlPNeap-nPa9cRss-1v4BQfvz9lHVqq07zwiWRV80tChWR0Zxwx50m9zjDFAzkOD02jbl7c9qcn0vIPZu9x0ydX9BTsgpEMfHEwG-TLSSFju-0Dn6laYvp02UdR96bEuQnTkfnUWKsQds3JwMigVgi8LwKXkIXdXszT8Mq7Bz42OcQHvsL0uCxfdHRg/https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-dnsop-caching-resolution-failures-01 > > > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://secure-web.cisco.com/1X4Rarmsiq-SsH39XV8rmlSY-wlnMHFd1fOwVU5jcXa6xvDmH2MmdE98OFVMnL2joeah-AhvVvD_wpcjnY5tqBkoJar30JHIpdxfNHJHBT03ZELDpSnG8n6PCkacoLgsweCFBCswxLVE_AH-B0WlhKnf8_kpryc75wefklVPqYx-wXLq8qR4P9Zs1xMqhm5T03sAQzHHytcaDWQmwjxHocjR0Mqb1zrSURbXAsCEw34oEjiz_gowwgo4JpWZePQcnfMjCkuDnhyFTxdh8guTWXg/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdnsop > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
