DoHPE: DoH with Privacy Enhancements
draft-dickinson-doh-dohpe-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-18
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)
Network Working Group                                       S. Dickinson
Internet-Draft                                                Sinodun IT
Intended status: Standards Track                               W. Toorop
Expires: January 19, 2019                                     NLnet Labs
                                                           July 18, 2018

                  DoHPE: DoH with Privacy Enhancements
                      draft-dickinson-doh-dohpe-00

Abstract

   This document describes DoHPE (DoH with Privacy Enhancements) - a
   privacy and anonymity profile for DoH [I-D.ietf-doh-dns-over-https]
   clients.  The profile provides guidelines on the composition of DoH
   messages, designed to minimize disclosure of identifying information.

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 January 19, 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
   (http://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.

Dickinson & Toorop      Expires January 19, 2019                [Page 1]
Internet-Draft    DoHPE: DoH with Privacy Enhancements         July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Protocol specification  . . . . . . . . . . . . . . . . . . .   4
     3.1.  Selection of DoH server . . . . . . . . . . . . . . . . .   4
     3.2.  HTTPS connections . . . . . . . . . . . . . . . . . . . .   4
     3.3.  HTTP version  . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  HTTP method . . . . . . . . . . . . . . . . . . . . . . .   5
     3.5.  HTTP headers  . . . . . . . . . . . . . . . . . . . . . .   5
       3.5.1.  User agent  . . . . . . . . . . . . . . . . . . . . .   5
       3.5.2.  Other headers . . . . . . . . . . . . . . . . . . . .   5
     3.6.  Client authentication . . . . . . . . . . . . . . . . . .   5
     3.7.  Other HTTP functionality  . . . . . . . . . . . . . . . .   5
     3.8.  Countermeasures to Traffic Analysis . . . . . . . . . . .   5
   4.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Implementations . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The DoH protocol [I-D.ietf-doh-dns-over-https] is currently under
   development with stated potential use cases of:

   "... preventing on-path devices from interfering with DNS operations
   and allowing web applications to access DNS information via existing
   browser APIs in a safe way consistent with Cross Origin Resource
   Sharing (CORS)."

   Whilst DoH has clear benefits in terms of encryption, authentication,
   traffic obfuscation and ease of implementation, it introduce new
   privacy concerns when compared with DNS over UDP, TCP or TLS
   (RFC7858) simply because it introduces a new transport layer (HTTPS)
   that can contain client identifiers (e.g.  user-agent, accept-
   language) not present in any existing DNS transport.

   The privacy considerations section of that draft state the following:

   "The DoH protocol design allows applications to fully leverage the
   HTTP ecosystem, including features that are not enumerated here.
   Utilizing the full set of HTTP features enables DoH to be more than
   an HTTP tunnel, but at the cost of opening up implementations to the
Show full document text