Cited by 13Network Security and Intrusion DetectionCaching and Content DeliveryNetwork Traffic and Congestion Control

The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.

Serving Stale Data to Improve DNS Resiliency

Abstract

This draft 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. It updates the definition of TTL from [RFC1034], [RFC1035], and [RFC2181] to make it clear that data can be kept in the cache beyond the TTL expiry and used for responses when a refreshed answer is not readily available. 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.

Overview

Integrity signals

Registry

Crossref · 10.17487/rfc8767

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cited by

Sorted by citations

See all 13

Metadata

Authors
Lawrence, D., Kumari, W., & Sood, P.
Publisher
RFC Editor
Published
2020-03
OpenAlex
W2765188251
Cited by
12
References
1
Citations by year
2026: 2 · 2025: 1 · 2024: 1 · 2023: 3 · 2022: 1
Type
report
Language
en
Open access
closed
Topics
  • Physical Sciences › Computer Science › Computer Networks and Communications › Network Security and Intrusion Detection
  • Physical Sciences › Computer Science › Computer Networks and Communications › Caching and Content Delivery
  • Physical Sciences › Computer Science › Computer Networks and Communications › Network Traffic and Congestion Control
Keywords
TTL, denial-of-service attacks, DNSSEC

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review