Specification of DNS over Dedicated QUIC Connections
draft-huitema-dprive-dnsoquic-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                         C. Huitema
Internet-Draft                                      Private Octopus Inc.
Intended status: Standards Track                               A. Mankin
Expires: September 6, 2020                                    Salesforce
                                                            S. Dickinson
                                                              Sinodun IT
                                                          March 05, 2020

          Specification of DNS over Dedicated QUIC Connections
                    draft-huitema-dprive-dnsoquic-00

Abstract

   This document describes the use of QUIC to provide transport privacy
   for DNS.  The encryption provided by QUIC has similar properties to
   that provided by TLS, while QUIC transport eliminates the head-of-
   line blocking issues inherent with TCP and provides more efficient
   error corrections than UDP.  DNS over QUIC (DoQ) has privacy
   properties similar to DNS over TLS (DoT) specified in RFC7858, and
   performance characteristics similar to classic DNS over UDP.

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 6, 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

Huitema, et al.         Expires September 6, 2020               [Page 1]
Internet-Draft           DNS over Dedicated QUIC              March 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Key Words . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Design Considerations . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Scope is Limited to the Stub to Resolver Scenario . . . .   4
     3.2.  Provide DNS Privacy . . . . . . . . . . . . . . . . . . .   5
     3.3.  Design for Minimum Latency  . . . . . . . . . . . . . . .   5
     3.4.  No Specific Middlebox Bypass Mechanism  . . . . . . . . .   6
   4.  Specifications  . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Connection Establishment  . . . . . . . . . . . . . . . .   6
       4.1.1.  Draft Version Identification  . . . . . . . . . . . .   6
       4.1.2.  Port Selection  . . . . . . . . . . . . . . . . . . .   7
     4.2.  Stream Mapping and Usage  . . . . . . . . . . . . . . . .   7
       4.2.1.  Server Initiated Transactions . . . . . . . . . . . .   8
       4.2.2.  Stream Reset  . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Connection Management . . . . . . . . . . . . . . . . . .   8
     4.4.  Connection Resume and 0-RTT . . . . . . . . . . . . . . .   9
   5.  Implementation Requirements . . . . . . . . . . . . . . . . .   9
     5.1.  Authentication  . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Fall Back to Other Protocols on Connection Failure  . . .  10
     5.3.  Address Validation  . . . . . . . . . . . . . . . . . . .  10
     5.4.  Response Sizes  . . . . . . . . . . . . . . . . . . . . .  10
     5.5.  DNS Message IDs . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  Padding . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.7.  Connection Handling . . . . . . . . . . . . . . . . . . .  11
       5.7.1.  Connection Reuse  . . . . . . . . . . . . . . . . . .  11
       5.7.2.  Connection Close  . . . . . . . . . . . . . . . . . .  12
       5.7.3.  Idle Timeouts . . . . . . . . . . . . . . . . . . . .  12
     5.8.  Flow Control Mechanisms . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  13
     7.1.  Privacy Issues With Zero RTT data . . . . . . . . . . . .  13
     7.2.  Privacy Issues With Session Resume  . . . . . . . . . . .  14