RFC 8767 on Serving Stale Data to Improve DNS Resiliency

rfc-editor@rfc-editor.org Tue, 31 March 2020 22:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5D5863A0BFB; Tue, 31 Mar 2020 15:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 6LvR9p9HU5ML; Tue, 31 Mar 2020 15:33:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 256AF3A0BF9; Tue, 31 Mar 2020 15:33:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 59D67F40737; Tue, 31 Mar 2020 15:33:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3Njcgb24gU2VydmluZyBTdGFsZSBEYXRhIHRvIEltcHJvdmUgRE5TIFJlc2lsaWVuY3k=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200331223354.59D67F40737@rfc-editor.org>
Date: Tue, 31 Mar 2020 15:33:54 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/99fjwIarJG_L_DLJPaJ08BqVAwQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 22:34:00 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8767

        Title:      Serving Stale Data to Improve DNS Resiliency 
        Author:     D. Lawrence,
                    W. Kumari,
                    P. Sood
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    tale@dd.org, 
        Pages:      12
        Updates:    RFC 1034, RFC 1035, RFC 2181

        I-D Tag:    draft-ietf-dnsop-serve-stale-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8767

        DOI:        10.17487/RFC8767

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.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC