Providing Minimal-Sized Responses to DNS Queries with QTYPE=ANY
draft-ietf-dnsop-refuse-any-03
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (dnsop WG)
|
|
Authors |
|
Joe Abley
,
Ólafur Guðmundsson
,
Marek Majkowski
|
|
Last updated |
|
2016-12-30
(latest revision 2016-11-15)
|
|
Replaces |
|
draft-dnsop-refuse-any
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
Revised I-D Needed - Issue raised by WGLC
|
|
Document shepherd |
|
Tim Wicinski
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Tim Wicinski" <tjw.ietf@gmail.com>
|
Network Working Group J. Abley
Internet-Draft Dyn, Inc.
Updates: 1035 (if approved) O. Gudmundsson
Intended status: Standards Track M. Majkowski
Expires: May 20, 2017 Cloudflare Inc.
November 16, 2016
Providing Minimal-Sized Responses to DNS Queries with QTYPE=ANY
draft-ietf-dnsop-refuse-any-03
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.
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
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 May 20, 2017.
Copyright Notice
Copyright (c) 2016 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
Abley, et al. Expires May 20, 2017 [Page 1]
Internet-Draft Minimal Responses for ANY Queries November 2016
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. General Approach . . . . . . . . . . . . . . . . . . . . . . 4
4. Behaviour of DNS Responders . . . . . . . . . . . . . . . . . 4
5. Behaviour of DNS Initiators . . . . . . . . . . . . . . . . . 5
6. HINFO Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Updates to RFC 1035 . . . . . . . . . . . . . . . . . . . . . 6
8. Implementation Experience . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
12.1. Normative References . . . . . . . . . . . . . . . . . . 7
12.2. Informative References . . . . . . . . . . . . . . . . . 7
12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Editorial Notes . . . . . . . . . . . . . . . . . . 8
A.1. Change History . . . . . . . . . . . . . . . . . . . . . 8
A.1.1. draft-ietf-dnsop-refuse-any-03 . . . . . . . . . . . 8
A.1.2. draft-ietf-dnsop-refuse-any-02 . . . . . . . . . . . 8
A.1.3. draft-ietf-dnsop-refuse-any-01 . . . . . . . . . . . 8
A.1.4. draft-ietf-dnsop-refuse-any-00 . . . . . . . . . . . 8
A.1.5. draft-jabley-dnsop-refuse-any-01 . . . . . . . . . . 8
A.1.6. draft-jabley-dnsop-refuse-any-00 . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
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 [RFC1034] [RFC1035] does not include specific
guidance for the behaviour of DNS servers or clients in this
situation. This document aims to provide such guidance.
Abley, et al. Expires May 20, 2017 [Page 2]
Internet-Draft Minimal Responses for ANY Queries November 2016
Show full document text