Serving Stale Data to Improve DNS Resiliency
RFC 8767

Received changes through RFC Editor sync (created alias RFC 8767, changed abstract to 'This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data.  One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector.  This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.', changed pages to 12, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-03-31, changed IESG state to RFC Published, created updates relation between draft-ietf-dnsop-serve-stale and RFC 1034, created updates relation between draft-ietf-dnsop-serve-stale and RFC 1035, created updates relation between draft-ietf-dnsop-serve-stale and RFC 2181)