RFC 9077 on NSEC and NSEC3: TTLs and Aggressive Use

rfc-editor@rfc-editor.org Fri, 23 July 2021 05:22 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71E5B3A1D4E; Thu, 22 Jul 2021 22:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mC0TwZ8hd3W; Thu, 22 Jul 2021 22:22:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5998F3A1D48; Thu, 22 Jul 2021 22:22:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CBBBEF4077F; Thu, 22 Jul 2021 22:22:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNzcgb24gTlNFQyBhbmQgTlNFQzM6IFRUTHMgYW5kIEFnZ3Jlc3NpdmUgVXNl?=
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: <20210723052210.CBBBEF4077F@rfc-editor.org>
Date: Thu, 22 Jul 2021 22:22:10 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IfpuV7bdTeHuCTF09_8_FFE0Y9Q>
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: Fri, 23 Jul 2021 05:22:30 -0000

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

        
        RFC 9077

        Title:      NSEC and NSEC3: TTLs and 
                    Aggressive Use 
        Author:     P. van Dijk
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2021
        Mailbox:    peter.van.dijk@powerdns.com
        Pages:      8
        Updates:    RFC 4034, RFC 4035, RFC 5155, RFC 8198

        I-D Tag:    draft-ietf-dnsop-nsec-ttl-05.txt

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

        DOI:        10.17487/RFC9077

Due to a combination of unfortunate wording in earlier documents,
aggressive use of NSEC and NSEC3 records may deny the existence of
names far beyond the intended lifetime of a denial. This document
changes the definition of the NSEC and NSEC3 TTL to correct that
situation. This document updates RFCs 4034, 4035, 5155, and 8198.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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