An Proxy Use Case of DNS over HTTPS
draft-ietf-dnsop-dns-wireformat-http-02

Document Type Active Internet-Draft (dnsop WG)
Last updated 2018-03-21
Replaces draft-song-dns-wireformat-http
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  L. Song
Internet-Draft                                Beijing Internet Institute
Intended status: Experimental                                   P. Vixie
Expires: September 22, 2018                                         TISF
                                                                 S. Kerr
                                                          March 21, 2018

                  An Proxy Use Case of DNS over HTTPS
                draft-ietf-dnsop-dns-wireformat-http-02

Abstract

   This memo introduces a DNS proxy use case to tunnel DNS query and
   response over HTTPs using DOH, a newly proposed DNS transport.  This
   is useful in some situation where DNS is not working properly and DOH
   is not widely available for many stub-resolvers.

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 September 22, 2018.

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

Song, et al.           Expires September 22, 2018               [Page 1]
Internet-Draft     An Proxy Use Case of DNS over HTTPS        March 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Use case description  . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Registration of application/dns-tcpwireformat Media Type    4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   RFC 1035 [RFC1035] specifies the wire format for DNS messages.  It
   also specifies DNS transport on UDP and TCP on port 53, which is
   still used today.  To enhance the availability of honest DNS, a new
   DNS transport DOH is proposed which transport DNS over HTTPs
   [I-D.ietf-doh-dns-over-https], in a way to cure DNS's long-time
   suffering from on-path attack by spoofing and blocking.

   This memo introduces a DNS proxy use case to leverage the DOH
   protocol as a substrate to tunnel DNS data over HTTPs which is called
   called DOH proxy in the rest of the document.  It is useful
   especially when most DNS stub-resolvers and servers are not aware the
   new DOH protocol, but a public or private proxy using DOH can be
   deployed and offer DOH capacity to users to bypass the networks where
   DNS is not working properly.

   Just as a normal DNS proxy described in [RFC5625], DOH proxy works as
   a simple DNS forwarder keeping the transparency principle, so any
   "hop-by-hop" mechanisms or newly introduced protocol extensions
   operate as if the proxy were not there.  The only difference is DOH
   proxy consist two part, a proxy client as a initiator of DOH tunnel
   and a proxy server as a terminator.

   In order to keep the transparency of DOH proxy, a new media type is
   required in DOH proxy use case to allow the proxy client and proxy
   server use the same transport (UDP or TCP) connecting sub-resolver
   and far-end server.

   May REMOVE BEFORE PUBLICATION: Comparing using a general VPN, the DOH
   proxy can work on an actual HTTP server, so it can be hosted on a
   machine that also serves web pages.  This means that DNS over HTTP is
   slightly more "stealthy" than a VPN, in that it can be
   indistinguishable from normal web traffic.

Song, et al.           Expires September 22, 2018               [Page 2]
Internet-Draft     An Proxy Use Case of DNS over HTTPS        March 2018

2.  Use case description

   As mentioned in introduction, DOH proxy is a special use case to
Show full document text