[DNSOP] I-D Action: draft-ietf-dnsop-nsec-aggressiveuse-09.txt

internet-drafts@ietf.org Thu, 30 March 2017 19:05 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D94E1201FA; Thu, 30 Mar 2017 12:05:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149090072915.15432.12520194496053843455@ietfa.amsl.com>
Date: Thu, 30 Mar 2017 12:05:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/u9Ed75Tdeb0BNuus3POOhh8aqD4>
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-nsec-aggressiveuse-09.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 19:05:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations of the IETF.

        Title           : Aggressive use of DNSSEC-validated Cache
        Authors         : Kazunori Fujiwara
                          Akira Kato
                          Warren Kumari
	Filename        : draft-ietf-dnsop-nsec-aggressiveuse-09.txt
	Pages           : 16
	Date            : 2017-03-30

   The DNS relies upon caching to scale; however, the cache lookup
   generally requires an exact match.  This document specifies the use
   of NSEC/NSEC3 resource records to allow DNSSEC validating resolvers
   to generate negative answers within a range, and positive answers
   from wildcards.  This increases performance / decreases latency,
   decreases resource utilization on both authoritative and recursive
   servers, and also increases privacy.  It may also help increase
   resilience to certain DoS attacks in some circumstances.

   This document updates RFC4035 by allowing validating resolvers to
   generate negative answers based upon NSEC/NSEC3 records (and positive
   answers in the presence of wildcards).

   [ Ed note: Text inside square brackets ([]) is additional background
   information, answers to frequently asked questions, general musings,
   etc.  They will be removed before publication.This document is being
   collaborated on in Github at: https://github.com/wkumari/draft-ietf-
   dnsop-nsec-aggressiveuse.  The most recent version of the document,
   open issues, etc should all be available here.  The authors
   (gratefully) accept pull requests.]

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: