A Mechanism to Reduce the junky queries to Authoritative Name Servers Serving Small Size Zones
draft-yao-dnsop-smallzone-junk-query-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dnsop                                                             J. Yao
Internet-Draft                                                     CNNIC
Intended status: Standards Track                            July 8, 2019
Expires: January 9, 2020

 A Mechanism to Reduce the junky queries to Authoritative Name Servers
                        Serving Small Size Zones
                draft-yao-dnsop-smallzone-junk-query-00

Abstract

   Some zones are small, public and stable, but very important.  They
   might deal with millions of queries every day.  But many of the
   queries are junky.  For examples, many queries DNS root servers
   receive are junky.  The queried junky names are not in the root, but
   the root servers have to waste a lot of resources to deal with them.
   It has been an obstacle to increase the performance of DNS root
   query.  In order to save the resource caused by the DNS junky
   queries, this document proposes a new mechanism by aggressive use of
   the owner name list of the DNS zone.

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 https://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
   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 January 9, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Yao                      Expires January 9, 2020                [Page 1]
Internet-Draft               root-junk-query                   July 2019

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design Overview . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Onldigest Resource Record . . . . . . . . . . . . . . . . . .   4
   5.  Create the Owner Name list and Calculate the Digest . . . . .   4
   6.  Requirements for the resolver . . . . . . . . . . . . . . . .   5
   7.  Requirements for the Authoritative Name Servers . . . . . . .   5
   8.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   6
   11. Change History  . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  draft-yao-dnsop-smallzone-junk-query: Version 00 . . . .   7
   12. Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Some zones are small, public and stable, but very important.  They
   might deal with millions of queries every day.  But many of the
   queries are junky.  For examples, many queries DNS root servers
   receive are junky.  The queried junky names are not in the root, but
   the root servers have to waste a lot of resources to deal with them.
   It has been an obstacle to increase the performance of DNS root
   query.

   In order to save the resource caused by the DNS junky queries, this
   document proposes a new mechanism by aggressive use of the owner name
Show full document text