Authoritative DNS-over-TLS Operational Considerations
draft-hal-adot-operational-considerations-02

Document Type Active Internet-Draft (candidate for dprive WG)
Last updated 2019-08-14 (latest revision 2019-08-13)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
dprive or dnsop                                             K. Henderson
Internet-Draft                                                  Verisign
Intended status: Informational                                  T. April
Expires: February 14, 2020                                        Akamai
                                                            J. Livingood
                                                                 Comcast
                                                         August 13, 2019

         Authoritative DNS-over-TLS Operational Considerations
              draft-hal-adot-operational-considerations-02

Abstract

   DNS over TLS (DoT) has been gaining attention, primarily as a means
   of communication between stub resolvers and recursive resolvers.
   There have also been discussions and experiments involving the use of
   DoT to communicate with authoritative nameservers (Authoritative DNS
   over TLS or "ADoT"), including communication between recursive and
   authoritative resolvers.  However, we have identified a number of
   operational concerns with ADoT that have arisen as DNS operators have
   begun to experiment with and prepare for deploying DoT.  These
   operational concerns need to be addressed prior to ADoT's deployment
   at scale by DNS operators in order to maintain the stability and
   resilience of the global DNS.  The document also provides some
   suggested next steps to advance the operator community's
   understanding of ADoT's operational impact.

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 14, 2020.

Henderson, et al.       Expires February 14, 2020               [Page 1]
Internet-Draft       ADoT Operational Considerations         August 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Background and Motivation . . . . . . . . . . . . . . . .   3
       1.1.1.  Why operational considerations are so important for
               ADoT  . . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Other considerations related to ADoT  . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Key Issues and Questions  . . . . . . . . . . . . . . . . . .   6
     3.1.  Signaling Support for ADoT  . . . . . . . . . . . . . . .   6
     3.2.  Port number . . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  TLS version . . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Resumptions . . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Operational Monitoring  . . . . . . . . . . . . . . . . .   8
     3.6.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   8
     3.7.  Socket efficiency/tuning considerations . . . . . . . . .   8
     3.8.  Post-Quantum Security . . . . . . . . . . . . . . . . . .   9
   4.  Suggestions for further research and development  . . . . . .   9
     4.1.  Required studies and analysis . . . . . . . . . . . . . .   9
     4.2.  Authoritative DNS over TLS (ADoT) Profile . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Informative References  . . . . . . . . . . . . . . . . .  10
     6.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  13
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  13
Show full document text