Serving Stale Data to Improve DNS Resiliency
draft-tale-dnsop-serve-stale-02
| Document | Type |
Replaced Internet-Draft
(dnsop WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | David C Lawrence , Warren "Ace" Kumari | ||
| Last updated | 2017-10-30 | ||
| Replaced by | draft-ietf-dnsop-serve-stale | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-serve-stale | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
David C Lawrence
Warren "Ace" Kumari
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)