Aggressive use of DNSSEC-validated Cache
draft-ietf-dnsop-nsec-aggressiveuse-08

Document Type Active Internet-Draft (dnsop WG)
Last updated 2017-03-16 (latest revision 2017-01-12)
Replaces draft-fujiwara-dnsop-nsec-aggressiveuse
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Wicinski
Shepherd write-up Show (last changed 2017-03-02)
IESG IESG state In Last Call (ends 2017-03-27)
Consensus Boilerplate Yes
Telechat date
Responsible AD Joel Jaeggli
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                        K. Fujiwara
Internet-Draft                                                      JPRS
Updates: 4035 (if approved)                                      A. Kato
Intended status: Standards Track                               Keio/WIDE
Expires: July 16, 2017                                         W. Kumari
                                                                  Google
                                                        January 12, 2017

                Aggressive use of DNSSEC-validated Cache
                 draft-ietf-dnsop-nsec-aggressiveuse-08

Abstract

   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.]

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Fujiwara, et al.          Expires July 16, 2017                 [Page 1]
Internet-Draft              NSEC/NSEC3 usage                January 2017

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 16, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Aggressive use of Cache . . . . . . . . . . . . . . . . . . .   6
     5.1.  NSEC  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  NSEC3 . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.3.  Wildcards . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.4.  Consideration on TTL  . . . . . . . . . . . . . . . . . .   7
   6.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Update to RFC 4035  . . . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. Implementation Status . . . . . . . . . . . . . . . . . . . .   9
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Change History . . . . . . . . . . . . . . . . . . . . .  10
       11.1.1.  Version draft-fujiwara-dnsop-nsec-aggressiveuse-01 .  13
       11.1.2.  Version draft-fujiwara-dnsop-nsec-aggressiveuse-02 .  13
       11.1.3.  Version draft-fujiwara-dnsop-nsec-aggressiveuse-03 .  13
     11.2.  new section  . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text