DNS over HTTPS (DoH) Considerations for Operator Networks
draft-reid-doh-operator-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-18 (latest revision 2019-03-09)
Replaces draft-reid-operator-doh
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)
DoH                                                            A. Fidler
Internet-Draft                                                    BT plc
Intended status: Informational                                 B. Hubert
Expires: September 11, 2019                                  OpenXchange
                                                            J. Livingood
                                                                 Comcast
                                                                 J. Reid
                                                                RTFM llp
                                                              N. Leymann
                                                     Deutsche Telekom AG
                                                          March 10, 2019

       DNS over HTTPS (DoH) Considerations for Operator Networks
                       draft-reid-doh-operator-00

Abstract

   The introduction of DNS over HTTPS (DoH), defined in RFC8484,
   presents a number of challenges to network operators.  These are
   described in this document.  The objective is to document the problem
   space and make suggestions that could help inform network operators
   on how to take account of DoH deployment.  This document also
   identifies topics that may require further analysis.

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

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Fidler, et al.         Expires September 11, 2019               [Page 1]
Internet-Draft          draft-reid-doh-operators              March 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Contrasting DoH and Conventional DNS  . . . . . . . . . . . .   3
   4.  Regulatory and Policy Considerations  . . . . . . . . . . . .   4
     4.1.  Local Policy Constraints  . . . . . . . . . . . . . . . .   4
     4.2.  Regulatory and Legal Impacts  . . . . . . . . . . . . . .   5
     4.3.  Regulatory Constraints  . . . . . . . . . . . . . . . . .   5
   5.  Network Operations  . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Impact on DNS query logging . . . . . . . . . . . . . . .   6
     5.2.  CDN endpoint selection  . . . . . . . . . . . . . . . . .   6
     5.3.  Redirection for captive portals . . . . . . . . . . . . .   7
     5.4.  Managed network services  . . . . . . . . . . . . . . . .   7
     5.5.  Resolver capacity management  . . . . . . . . . . . . . .   7
     5.6.  Failure recovery  . . . . . . . . . . . . . . . . . . . .   8
     5.7.  Impact on Network Address Translation . . . . . . . . . .   8
     5.8.  Load balancing and failover . . . . . . . . . . . . . . .   8
   6.  User Support  . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Provisioning  . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Privacy Concerns  . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. Human Rights Considerations . . . . . . . . . . . . . . . . .  13
   11. Open Issues for Further Study . . . . . . . . . . . . . . . .  14
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     14.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   Traditional DNS traffic between stub resolvers, recursive servers and
Show full document text