Associating a DoH Server with a Resolver
draft-hoffman-resolver-associated-doh-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-08-23
Replaced by draft-ietf-doh-resolver-associated-doh
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                         P. Hoffman
Internet-Draft                                                     ICANN
Intended status: Standards Track                         August 23, 2018
Expires: February 24, 2019

                Associating a DoH Server with a Resolver
                draft-hoffman-resolver-associated-doh-00

Abstract

   Some clients will want to know if there are one or more DoH servers
   associated with the DNS recursive resolver that the client is already
   using.  This document describes a protocol for a resolver to tell a
   client what its associated DoH servers are.

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 24, 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                 Expires February 24, 2019               [Page 1]
Internet-Draft           Resolver Associated DoH             August 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  RAD RRtype Description  . . . . . . . . . . . . . . . . . . .   3
   4.  Use of RAD  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Server Use of RAD . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Client Use of RAD . . . . . . . . . . . . . . . . . . . .   4
   5.  Design Choices  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Root Zone . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.2.  Registration for RAD RRtype . . . . . . . . . . . . . . .   5
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   DoH [I-D.ietf-doh-dns-over-https] requires that one or more DoH
   servers be configured for the DoH client.  That document does not say
   how the DoH servers are found, nor how to select from a list of
   possible DoH servers, nor what the user interface (UI) for the
   configuration should be.

   There is a use case for clients who have one or more currently-
   configured DNS recursive resolvers wanting to use DoH for DNS
   resolution instead.  Clients typically configure their DNS recursive
   resolvers with through manual configuration (such as manually editing
   a /etc/named.conf file) or through automatic configuration from a
   protocol such as DHCP.

   The client that wants to change from its currently-configured DNS
   recursive resolvers might be the stub resolver in an operating
   system, although at this time it is rare that such stub resolvers can
   use DoH.  A much more likely use case is a web browser that is
   getting name resolution through the stub resolver on the computer on
   which it is running.  The user of the browser might have a preference
   for using a DoH server, and it might want a DoH server that is
   associated with the resolver that the computer is currently using.

   To address this use case, this document defines a new RRtype and
   describes how it is used.  The design choices made are described in
   Section 5.

Hoffman                 Expires February 24, 2019               [Page 2]
Internet-Draft           Resolver Associated DoH             August 2018
Show full document text