Upgrading Communication from Stub Resolvers to DoT or DoH
draft-pp-add-stub-upgrade-02

Document Type Active Internet-Draft (individual)
Authors Puneet Sood  , Paul Hoffman 
Last updated 2020-06-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) 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. Sood
Internet-Draft                                                    Google
Intended status: Standards Track                              P. Hoffman
Expires: January 1, 2021                                           ICANN
                                                           June 30, 2020

       Upgrading Communication from Stub Resolvers to DoT or DoH
                      draft-pp-add-stub-upgrade-02

Abstract

   This document describes methods for a DNS stub resolver to upgrade
   its communications with a known recursive resolver to include
   encrytion using DoT or DoH.  This protocol is designed for the
   scenario where the stub resolver already has the IP address of the
   recursive resolver.

   Other protocols under develpment address scenarios where the stub
   resolver wants to discover recursive resolvers that use DoT or DoH.
   This document does not cover such discovery.

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 1, 2021.

Copyright Notice

   Copyright (c) 2020 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

Sood & Hoffman           Expires January 1, 2021                [Page 1]
Internet-Draft         Stub upgrade to DoT or DoH              June 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Using RESINFO Responses for Upgrade . . . . . . . . . . . . .   3
     2.1.  Contacting This Resolver Using DoH  . . . . . . . . . . .   3
     2.2.  Contacting This Resolver Using DoT  . . . . . . . . . . .   3
     2.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Method Overview . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Order of Desired Protocols  . . . . . . . . . . . . . . .   6
   4.  Method Details  . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Inputs to the Process . . . . . . . . . . . . . . . . . .   6
     4.2.  TLS Authentication  . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Registration for doh-templates in the IANA DNS Resolver
           Information Registry  . . . . . . . . . . . . . . . . . .   7
     5.2.  Registration for dot-ports in the IANA DNS Resolver
           Information Registry  . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   A stub resolver (hereafter called "a stub") using traditional DNS
   over port 53 may wish to use encrypted communication with the
   recursive resolver (hereafter called "a resolver").  In such a
   scenario, the stub needs to know how to probe the resolver to find
   out if it can use encrypted communication.  This document describes a
   mechanism for a stub that knows the IP address of the resolver to do
   so.  It is assumed that the IP address was received insecurely, such
   as through DHCP.

   The method in this document assumes that a stub wants to attempt to
   upgrade its communication with the resolver to either DNS-over-TLS
   (DoT, [RFC7858]) or DNS-over-HTTPS (DoH, [RFC8484]).  The method is
   basically to use a DNS request as defined in [I-D.pp-add-resinfo] to
   get information about whether the resolver supports DoT or DoH.  The
   method can later be extended to other secure transports for stub-to-
Show full document text