DOH Digests
draft-nottingham-doh-digests-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                      M. Nottingham
Internet-Draft                                             July 02, 2018
Intended status: Informational
Expires: January 3, 2019

                              DOH Digests
                    draft-nottingham-doh-digests-00

Abstract

   The lack of flexible configuration and selection mechanisms for DOH
   servers is identified as suboptimal for privacy and performance in
   some applications.

   This document makes a straw-man proposal for an improvement.

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 January 3, 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.

Nottingham               Expires January 3, 2019                [Page 1]
Internet-Draft                 DOH Digests                     July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  DOH's Additional Benefits for Associated Services . . . .   2
     1.2.  Achieving DOH's Privacy Goals through Diversity . . . . .   3
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   4
   3.  DOH Digests . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Using DOH Digests . . . . . . . . . . . . . . . . . . . .   4
     3.2.  The DOH Digest Format . . . . . . . . . . . . . . . . . .   5
     3.3.  Hostname Normalisation  . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   One of the core motivations for DOH [I-D.ietf-doh-dns-over-https] is
   to improve end-user privacy by obfuscating the stream of DNS requests
   that the DOH client makes.  It does this by mixing DOH requests into
   a stream of "normal" HTTP requests to a configured Web server; for
   example, a large Web site or a Content Delivery Network.

   However, DOH intentionally avoids defining a mechanism for
   configuring a particular DOH server for a given application or host.
   So far, the most common way to do so is to select one from a pre-
   configured list of services in an application, such as a Web browser.

   Typically, the list of available DOH services is vetted by the
   application's vendor to assure that they will honour the
   application's requirements for handling of sensitive data (i.e., the
   client's DNS request stream) and similar concerns.

   This document proposes a means of selecting a DOH server that
   encourages the deployment of DOH servers by sharing some of its
   additional benefits with servers that are good candidates for serving
   DOH traffic.

1.1.  DOH's Additional Benefits for Associated Services

   When a DOH server is colocated with (or closely coordinated with)
   other network services - especially HTTP services - those associated
   services enjoy a few additional benefits beyond those seen by
   adopting DOH in the first place.

Nottingham               Expires January 3, 2019                [Page 2]
Internet-Draft                 DOH Digests                     July 2018

   o  Associated services have an additional privacy benefit; there is
      one less party involved in the interaction, whereas "normal" DNS
      and DOH to an unassociated HTTP server require a third party to
      resolve names.

   o  Removing a third party also removes a separate point of potential
Show full document text