Serving Stale Data to Improve DNS Resiliency
draft-tale-dnsop-serve-stale-02
| Document | Type | Replaced Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Last updated | 2017-10-30 | ||
| Replaced by | RFC 8767 | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-serve-stale | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-tale-dnsop-serve-stale-02.txt
https://www.ietf.org/archive/id/draft-tale-dnsop-serve-stale-02.txt
Abstract
This draft defines a method for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data.
Authors
tale
(tale@akamai.com)
Warren Kumari
(warren@kumari.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)