DNS privacy problem statement
draft-bortzmeyer-dnsop-dns-privacy-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-11-27
Replaced by rfc7626, draft-ietf-dprive-problem-statement
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                      S. Bortzmeyer
Internet-Draft                                                     AFNIC
Intended status: Informational                         November 27, 2013
Expires: May 31, 2014

                     DNS privacy problem statement
                 draft-bortzmeyer-dnsop-dns-privacy-00

Abstract

   This document describes the privacy issues associated with the use of
   the DNS by Internet users.  It is intended to be mostly a problem
   statement and it does not prescribe solutions (although Section 5
   suggests some possible improvments).

   Discussions of the document should take place on the dnsop mailing
   list [dnsop]

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 May 31, 2014.

Copyright Notice

   Copyright (c) 2013 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 May 31, 2014                  [Page 1]
Internet-Draft                DNS privacy                  November 2013

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Risks . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Data in the DNS request . . . . . . . . . . . . . . . . .   3
     2.2.  On the wire . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  In the servers  . . . . . . . . . . . . . . . . . . . . .   5
       2.3.1.  In the resolvers  . . . . . . . . . . . . . . . . . .   6
       2.3.2.  In the authoritative name servers . . . . . . . . . .   6
       2.3.3.  Rogue servers . . . . . . . . . . . . . . . . . . . .   7
   3.  Actual "attacks"  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Legalities  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Possible technical solutions  . . . . . . . . . . . . . . . .   7
     5.1.  On the wire . . . . . . . . . . . . . . . . . . . . . . .   8
       5.1.1.  Reducing the attack surface . . . . . . . . . . . . .   8
       5.1.2.  Encrypting the DNS traffic  . . . . . . . . . . . . .   8
     5.2.  In the servers  . . . . . . . . . . . . . . . . . . . . .  10
       5.2.1.  In the resolvers  . . . . . . . . . . . . . . . . . .  10
       5.2.2.  In the authoritative name servers . . . . . . . . . .  10
       5.2.3.  Rogue servers . . . . . . . . . . . . . . . . . . . .  11
   6.  Security considerations . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Domain Name System is specified in [RFC1034] and [RFC1035].  It
   is one of the most important infrastructure components of the
   Internet and one of the most 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 we try to give
   here a comprehensive and accurate list.

   Let us start with a small reminder of the way the DNS works (with
   some simplifications).  A client, the stub resolver, issues a DNS
   query to a server, the resolver (also called caching resolver or full
   resolver or recursive name server).  For instance, the query is "What
   are the AAAA records for www.example.com?".  AAAA is the qtype (Query
   Type) and www.example.com the qname (Query Name).  To get the answer,
   the resolver will query first the root nameservers, which will, most
   of the times, send a referral.  Here, the referral will be to .com
Show full document text