DNS Privacy Considerations
draft-bortzmeyer-dprive-rfc7626-bis-01

Document Type Active Internet-Draft (dprive WG)
Last updated 2018-07-18 (latest revision 2018-07-16)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
dprive                                                     S. Bortzmeyer
Internet-Draft                                                     AFNIC
Obsoletes: 7626 (if approved)                               S. Dickinson
Intended status: Informational                                Sinodun IT
Expires: January 17, 2019                                  July 16, 2018

                       DNS Privacy Considerations
                 draft-bortzmeyer-dprive-rfc7626-bis-01

Abstract

   This document describes the privacy issues associated with the use of
   the DNS by Internet users.  It is intended to be an analysis of the
   present situation and does not prescribe solutions.

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 http://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 January 17, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (http://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.

Bortzmeyer & Dickinson  Expires January 17, 2019                [Page 1]
Internet-Draft         DNS Privacy Considerations              July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Risks . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  The Alleged Public Nature of DNS Data . . . . . . . . . .   5
     2.2.  Data in the DNS Request . . . . . . . . . . . . . . . . .   5
       2.2.1.  Data in the DNS payload . . . . . . . . . . . . . . .   7
     2.3.  Cache Snooping  . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  On the Wire . . . . . . . . . . . . . . . . . . . . . . .   7
       2.4.1.  Unencrypted Transports  . . . . . . . . . . . . . . .   7
       2.4.2.  Encrypted Transports  . . . . . . . . . . . . . . . .   9
     2.5.  In the Servers  . . . . . . . . . . . . . . . . . . . . .  10
       2.5.1.  In the Recursive Resolvers  . . . . . . . . . . . . .  10
       2.5.2.  In the Authoritative Name Servers . . . . . . . . . .  12
       2.5.3.  Rogue Servers . . . . . . . . . . . . . . . . . . . .  13
       2.5.4.  Authentication of servers . . . . . . . . . . . . . .  13
       2.5.5.  Blocking of services  . . . . . . . . . . . . . . . .  14
     2.6.  Re-identification and Other Inferences  . . . . . . . . .  14
     2.7.  More Information  . . . . . . . . . . . . . . . . . . . .  15
   3.  Actual "Attacks"  . . . . . . . . . . . . . . . . . . . . . .  15
   4.  Legalities  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   This document is an analysis of the DNS privacy issues, in the spirit
   of Section 8 of [RFC6973].

   The Domain Name System is specified in [RFC1034], [RFC1035], and many
   later RFCs, which have never been consolidated.  It is one of the
   most important infrastructure components of the Internet and often
   ignored or misunderstood by Internet users (and even by many
   professionals).  Almost every activity on the Internet starts with a
   DNS query (and often several).  Its use has many privacy implications
   and this is an attempt at a comprehensive and accurate list.

   Let us begin with a simplified reminder of how the DNS works.  (See
   also [I-D.ietf-dnsop-terminology-bis]) A client, the stub resolver,
   issues a DNS query to a server, called the recursive resolver (also
Show full document text