DNS privacy considerations
draft-ietf-dprive-problem-statement-03

The information below is for an old version of the document
Document Type Active Internet-Draft (dprive WG)
Author St├ęphane Bortzmeyer 
Last updated 2015-03-19 (latest revision 2015-03-09)
Replaces draft-bortzmeyer-dnsop-dns-privacy
Stream IETF
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Revised I-D Needed - Issue raised by WGLC, Doc Shepherd Follow-up Underway
Document shepherd Warren Kumari
Shepherd write-up Show (last changed 2015-03-19)
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Warren Kumari" <warren@kumari.net>
DNS PRIVate Exchange (dprive) Working Group                S. Bortzmeyer
Internet-Draft                                                     AFNIC
Intended status: Informational                             March 9, 2015
Expires: September 10, 2015

                       DNS privacy considerations
                 draft-ietf-dprive-problem-statement-03

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.

   (REMOVE BEFORE PUBLICATION: Discussions of the document should take
   place on the DPRIVE working group mailing list [dprive].)

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 September 10, 2015.

Copyright Notice

   Copyright (c) 2015 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

Bortzmeyer             Expires September 10, 2015               [Page 1]
Internet-Draft                 DNS privacy                    March 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

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.3.  Cache snooping  . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  On the wire . . . . . . . . . . . . . . . . . . . . . . .   7
     2.5.  In the servers  . . . . . . . . . . . . . . . . . . . . .   8
       2.5.1.  In the recursive resolvers  . . . . . . . . . . . . .   8
       2.5.2.  In the authoritative name servers . . . . . . . . . .   9
       2.5.3.  Rogue servers . . . . . . . . . . . . . . . . . . . .  10
     2.6.  Re-identification and other inferences  . . . . . . . . .  10
   3.  Actual "attacks"  . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Legalities  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Security considerations . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  16

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] and [RFC1035].  It
   is one of the most important infrastructure components of the
   Internet and often ignored or misunderstood.  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.
   (REMOVE BEFORE PUBLICATION: We hope that the document
   [I-D.hoffman-dns-terminology] will be published as a RFC so most of
   this section could be replaced by a reference to it.)  A client, the
   stub resolver, issues a DNS query to a server, called the recursive
   resolver (also called caching resolver or full resolver or recursive
   name server).  Let's use the query "What are the AAAA records for
   www.example.com?" as an example.  AAAA is the qtype (Query Type), and
   www.example.com is the qname (Query Name).  (The description which

Bortzmeyer             Expires September 10, 2015               [Page 2]
Show full document text