A Bootstrapping Procedure to Discover and Authenticate DNS-over-(D)TLS and DNS-over-HTTPS Servers
draft-reddy-dprive-bootstrap-dns-server-01

Document Type Active Internet-Draft (individual)
Last updated 2019-03-10
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)
DPRIVE WG                                                       T. Reddy
Internet-Draft                                                    McAfee
Intended status: Standards Track                                 D. Wing
Expires: September 10, 2019
                                                           M. Richardson
                                                Sandelman Software Works
                                                            M. Boucadair
                                                                  Orange
                                                           March 9, 2019

 A Bootstrapping Procedure to Discover and Authenticate DNS-over-(D)TLS
                       and DNS-over-HTTPS Servers
               draft-reddy-dprive-bootstrap-dns-server-01

Abstract

   This document specifies mechanisms to automatically bootstrap
   endpoints (e.g., hosts, Customer Equipment) to discover and
   authenticate DNS-over-(D)TLS and DNS-over-HTTPS servers provided by a
   local network.

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 10, 2019.

Copyright Notice

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

Reddy, et al.          Expires September 10, 2019               [Page 1]
Internet-Draft          DoT/DoH server discovery              March 2019

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Bootstrapping Endpoint Devices  . . . . . . . . . . . . . . .   5
   4.  Bootstrapping IoT Devices and CPE . . . . . . . . . . . . . .   6
   5.  Discovery Procedure . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Connection handshake and service invocation . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Application Service & Application Protocol Tags . . . . .  10
       9.1.1.  DNS Application Service Tag Registration  . . . . . .  10
       9.1.2.  dns.tls Application Protocol Tag Registration . . . .  10
       9.1.3.  dns.dtls Application Protocol Tag Registration  . . .  10
       9.1.4.  dns.https Application Protocol Tag Registration . . .  10
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Traditionally a caching DNS server has been provided by the local
   network.  This provides benefits like low latency to that DNS server
   (due to its network proximity to the endpoint).  However, if an
   endpoint is configured to use Internet-hosted or public DNS-
   over-(D)TLS [RFC7858] [RFC8094] or DNS-over-HTTPS [RFC8484] servers,
   the local DNS server cannot serve the DNS requests from the
   endpoints.  If public DNS servers are used instead of using local DNS
   servers, the operational problems are listed below:

   o  "Split DNS" [RFC2775] to use the special internal-only domain
      names (e.g., "internal.example.com") in enterprise networks will
      not work, and ".local" and "home.arpa" names cannot be locally
      resolved in home networks.

   o  Content Delivery Networks (CDNs) that map traffic based on DNS may
      lose the ability to direct end-user traffic to a nearby cluster in
Show full document text