DNS Query Name Minimisation to Improve Privacy
draft-ietf-dnsop-rfc7816bis-07

Document Type Active Internet-Draft (dnsop WG)
Authors St├ęphane Bortzmeyer  , Ralph Dolmans  , Paul Hoffman 
Last updated 2020-10-27
Replaces draft-bortzmeyer-rfc7816bis
Stream IETF
Intended RFC status Internet Standard
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call
Document shepherd Tim Wicinski
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to tjw.ietf@gmail.com
Network Working Group                                      S. Bortzmeyer
Internet-Draft                                                     AFNIC
Obsoletes: 7816 (if approved)                                 R. Dolmans
Intended status: Standards Track                              NLnet Labs
Expires: 30 April 2021                                        P. Hoffman
                                                                   ICANN
                                                         27 October 2020

             DNS Query Name Minimisation to Improve Privacy
                    draft-ietf-dnsop-rfc7816bis-07

Abstract

   This document describes a technique called "QNAME minimisation" to
   improve DNS privacy, where the DNS resolver no longer always sends
   the full original QNAME and original QTYPE to the upstream name
   server.  This document obsoletes RFC 7816.

   This document is part of the IETF DNSOP (DNS Operations) Working
   Group.  The source of the document, as well as a list of open issues,
   is at <https://framagit.org/bortzmeyer/rfc7816-bis>

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 30 April 2021.

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.

Bortzmeyer, et al.        Expires 30 April 2021                 [Page 1]
Internet-Draft             QNAME Minimisation               October 2020

   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 and Background . . . . . . . . . . . . . . . . .   2
     1.1.  Experience From RFC 7816  . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Description of QNAME Minimisation . . . . . . . . . . . . . .   4
     2.1.  QTYPE Selection . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  QNAME Selection . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Limit Number of Queries . . . . . . . . . . . . . . . . .   5
     2.4.  Stub and Forwarding Resolvers . . . . . . . . . . . . . .   6
   3.  Algorithm to Perform QNAME Minimisation . . . . . . . . . . .   7
   4.  QNAME Minimisation Examples . . . . . . . . . . . . . . . . .   8
   5.  Performance Considerations  . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Changes from RFC 7816 . . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction and Background

   The problem statement for this document is described in [RFC7626].
   This specific solution is not intended to fully solve the DNS privacy
   problem; instead, it should be viewed as one tool amongst many.

   QNAME minimisation follows the principle explained in Section 6.1 of
   [RFC6973]: the less data you send out, the fewer privacy problems
   you have.

Bortzmeyer, et al.        Expires 30 April 2021                 [Page 2]
Internet-Draft             QNAME Minimisation               October 2020

   Before QNAME minimisation, when a resolver received the query "What
   is the AAAA record for www.example.com?", it sent to the root
   (assuming a resolver whose cache is empty) the very same question.
   Sending the full QNAME to the authoritative name server was a
   tradition, not a protocol requirement.  In a conversation with one of
   the authors in January 2015, Paul Mockapetris explained that this
   tradition comes from a desire to optimise the number of requests,
Show full document text