DNS Queries over HTTPS (DoH)
draft-ietf-doh-dns-over-https-14
Network Working Group P. Hoffman
Internet-Draft ICANN
Intended status: Standards Track P. McManus
Expires: February 17, 2019 Mozilla
August 16, 2018
DNS Queries over HTTPS (DoH)
draft-ietf-doh-dns-over-https-14
Abstract
This document defines a protocol for sending DNS queries and getting
DNS responses over HTTPS. Each DNS query-response pair is mapped
into an HTTP exchange.
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 17, 2019.
Copyright Notice
Copyright (c) 2018 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
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.
Hoffman & McManus Expires February 17, 2019 [Page 1]
Internet-Draft DNS Queries over HTTPS (DoH) August 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Selection of DoH Server . . . . . . . . . . . . . . . . . . . 3
4. The HTTP Exchange . . . . . . . . . . . . . . . . . . . . . . 4
4.1. The HTTP Request . . . . . . . . . . . . . . . . . . . . 4
4.1.1. HTTP Request Examples . . . . . . . . . . . . . . . . 5
4.2. The HTTP Response . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Handling DNS and HTTP Errors . . . . . . . . . . . . 6
4.2.2. HTTP Response Example . . . . . . . . . . . . . . . . 7
5. HTTP Integration . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Cache Interaction . . . . . . . . . . . . . . . . . . . . 7
5.2. HTTP/2 . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3. Server Push . . . . . . . . . . . . . . . . . . . . . . . 9
5.4. Content Negotiation . . . . . . . . . . . . . . . . . . . 10
6. Definition of the application/dns-message media type . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7.1. Registration of application/dns-message Media Type . . . 10
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
8.1. On The Wire . . . . . . . . . . . . . . . . . . . . . . . 12
8.2. In The Server . . . . . . . . . . . . . . . . . . . . . . 12
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. Operational Considerations . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
11.1. Normative References . . . . . . . . . . . . . . . . . . 16
11.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Protocol Development . . . . . . . . . . . . . . . . 19
Appendix B. Previous Work on DNS over HTTP or in Other Formats . 19
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction
This document defines a specific protocol, DNS over HTTPS (DoH), for
sending DNS [RFC1035] queries and getting DNS responses over HTTP
[RFC7540] using https [RFC2818] URIs (and therefore TLS [RFC8446]
security for integrity and confidentiality). Each DNS query-response
pair is mapped into an HTTP exchange.
The described approach is more than a tunnel over HTTP. It
establishes default media formatting types for requests and responses
but uses normal HTTP content negotiation mechanisms for selecting
alternatives that endpoints may prefer in anticipation of serving new
use cases. In addition to this media type negotiation, it aligns
Show full document text