DNS-over-HTTPS and DNS-over-TLS Server Deployment Considerations for Enterprise Networks
draft-reddy-add-enterprise-00

Document Type Active Internet-Draft (individual)
Authors Tirumaleswar Reddy.K  , Dan Wing 
Last updated 2020-06-23
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
ADD                                                             T. Reddy
Internet-Draft                                                    McAfee
Intended status: Informational                                   D. Wing
Expires: December 25, 2020                                        Citrix
                                                           June 23, 2020

  DNS-over-HTTPS and DNS-over-TLS Server Deployment Considerations for
                          Enterprise Networks
                     draft-reddy-add-enterprise-00

Abstract

   This document discusses DoH/DoT deployment considerations for
   Enterprise networks.  It particularly sketches the required steps to
   use DNS-over-TLS (DoT) and/or DNS-over-HTTPS (DoH) server provided by
   the Enterprise network.

   One of the goals of the document is to assess to what extent existing
   tools can be used to provide such service.

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 December 25, 2020.

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
   carefully, as they describe your rights and restrictions with respect

Reddy & Wing            Expires December 25, 2020               [Page 1]
Internet-Draft       DoH/DoT in Enterprise Networks            June 2020

   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.  IT-owned devices  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IoT Devices . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  BYOD  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Roaming Enterprise Users  . . . . . . . . . . . . . . . . . .   7
     6.1.  VPN tunnel  . . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Client Authentication . . . . . . . . . . . . . . . . . .   7
   7.  Upstream Encryption . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   [RFC7626] discusses DNS privacy considerations in both "on the wire"
   (Section 2.4 of [RFC7626]) and "in the server" (Section 2.5 of
   [RFC7626]) contexts.  In recent years there has also been an increase
   in the availability of "public resolvers" [RFC8499] which DNS clients
   may be pre-configured to use instead of the default network resolver
   for a variety of reasons (e.g., offer a good reachability, support an
   encrypted transport, provide a strong privacy policy, (lack of)
   filtering).

   If public (DoT) [RFC7858] or DNS-over-HTTPS (DoH) [RFC8484] servers
   are used instead of using local DNS servers, it can adversely impact
   Enterprise network-based security.  Various network security services
   are provided by Enterprise networks to protect endpoints (e.g.,
   laptops, printers, IoT devices), and to enforce enterprise policies.
   These policies may be necessary to protect employees, customers, or
   citizens.  They are not the subject of this memo.

   Enterprise DNS servers in place for these purpose act on DNS requests
   originating from endpoints.  However, if an endpoint uses public DoT
   or DoH servers, the desired enterprise protection and enforcement can
   be bypassed.

Reddy & Wing            Expires December 25, 2020               [Page 2]
Internet-Draft       DoH/DoT in Enterprise Networks            June 2020
Show full document text