Providing Minimal-Sized Responses to DNS Queries that have QTYPE=ANY
draft-ietf-dnsop-refuse-any-07

Document Type Active Internet-Draft (dnsop WG)
Last updated 2018-11-13 (latest revision 2018-08-14)
Replaces draft-dnsop-refuse-any
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews TSVART will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Wicinski
Shepherd write-up Show (last changed 2018-07-06)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state AUTH48-DONE
Network Working Group                                           J. Abley
Internet-Draft                                                   Afilias
Updates: 1034, 1035 (if approved)                         O. Gudmundsson
Intended status: Standards Track                            M. Majkowski
Expires: February 15, 2019                               Cloudflare Inc.
                                                                 E. Hunt
                                                                     ISC
                                                         August 14, 2018

  Providing Minimal-Sized Responses to DNS Queries that have QTYPE=ANY
                     draft-ietf-dnsop-refuse-any-07

Abstract

   The Domain Name System (DNS) specifies a query type (QTYPE) "ANY".
   The operator of an authoritative DNS server might choose not to
   respond to such queries for reasons of local policy, motivated by
   security, performance or other reasons.

   The DNS specification does not include specific guidance for the
   behaviour of DNS servers or clients in this situation.  This document
   aims to provide such guidance.

   This document updates RFC 1034 and RFC 1035.

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 February 15, 2019.

Copyright Notice

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

Abley, et al.           Expires February 15, 2019               [Page 1]
Internet-Draft      Minimal Responses for ANY Queries        August 2018

   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
   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivations for Use of ANY Queries  . . . . . . . . . . . . .   3
   3.  General Approach  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Behaviour of DNS Responders . . . . . . . . . . . . . . . . .   4
     4.1.  Answer with a Subset of Available RRSets  . . . . . . . .   5
     4.2.  Answer with a Synthesised HINFO RRSet . . . . . . . . . .   5
     4.3.  Answer with Best Guess as to Intention  . . . . . . . . .   6
     4.4.  Behaviour with TCP Transport  . . . . . . . . . . . . . .   6
   5.  Behaviour of DNS Initiators . . . . . . . . . . . . . . . . .   6
   6.  HINFO Considerations  . . . . . . . . . . . . . . . . . . . .   7
   7.  Updates to RFC 1034 and RFC 1035  . . . . . . . . . . . . . .   7
   8.  Implementation Experience . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     12.2.  Informative References . . . . . . . . . . . . . . . . .   9
     12.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Appendix A.  Editorial Notes  . . . . . . . . . . . . . . . . . .  10
     A.1.  Change History  . . . . . . . . . . . . . . . . . . . . .  10
       A.1.1.  draft-ietf-dnsop-refuse-any-07  . . . . . . . . . . .  10
       A.1.2.  draft-ietf-dnsop-refuse-any-06  . . . . . . . . . . .  10
       A.1.3.  draft-ietf-dnsop-refuse-any-05  . . . . . . . . . . .  10
       A.1.4.  draft-ietf-dnsop-refuse-any-04  . . . . . . . . . . .  10
       A.1.5.  draft-ietf-dnsop-refuse-any-03  . . . . . . . . . . .  10
       A.1.6.  draft-ietf-dnsop-refuse-any-02  . . . . . . . . . . .  10
       A.1.7.  draft-ietf-dnsop-refuse-any-01  . . . . . . . . . . .  11
       A.1.8.  draft-ietf-dnsop-refuse-any-00  . . . . . . . . . . .  11
       A.1.9.  draft-jabley-dnsop-refuse-any-01  . . . . . . . . . .  11
Show full document text