DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?
draft-klensin-dns-function-considerations-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-06-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-klensin-dns-function-considerations
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                                         J. Klensin
Internet-Draft                                              June 2, 2017
Intended status: Informational
Expires: December 4, 2017

    DNS Privacy, Authorization, Special Uses, Encoding, Characters,
          Matching, and Root Structure: Time for Another Look?
             draft-klensin-dns-function-considerations-00

Abstract

   The basic design of the Domain Name System was completed almost 30
   years ago.  The last half of that period has been characterized by
   significant changes in requirements and expectations, some of which
   either require changes to how the DNS is used or that can be
   accommodated only poorly or not at all.  This document asks the
   question of whether it is time to either redesign and replace the DNS
   to match contemporary requirements and expectations (rather than
   continuing to try to design and implement incremental patches that
   are not fully satisfactory) or to draw some clear lines about
   functionality that is not really needed or that should be performed
   somewhere else.

Author's Note

   This draft is intended to draw a number of issues and references
   together in one place and to start a discussion.  It is obviously
   incomplete, particularly with regard to the list of perceived issues
   and deficiencies with that DNS.  To avoid misunderstanding, I don't
   completely believe some of the deficiencies listed below but am
   merely providing information about claims of deficiencies.  Input is
   welcome, especially about what is missing (or plain wrong) and would
   be greatly appreciated.

   This document should be discussed on the IETF list or by private
   conversation with the author.

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/.

Klensin                 Expires December 4, 2017                [Page 1]
Internet-Draft                DNS Revisions                    June 2017

   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 December 4, 2017.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Background and Hypothesis . . . . . . . . . . . . . . . . . .   3
   3.  Warts and Tensions With The Current DNS . . . . . . . . . . .   4
     3.1.  Multiple address types  . . . . . . . . . . . . . . . . .   4
     3.2.  Matching Part I: Case Sensitivity in Labels and Other
           Anomalies . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Matching Part II: Non-ASCII ("internationalized") Domain
           Name Labels . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Matching Part III: Label Synonyms, Equivalent Names, and
           Variants  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Query Privacy . . . . . . . . . . . . . . . . . . . . . .   7
     3.6.  Alternate Name Spaces for Public Use in the DNS
           Framework: The CLASS Problem  . . . . . . . . . . . . . .   8
     3.7.  Loose Synchronization . . . . . . . . . . . . . . . . . .   8
     3.8.  Private Name Spaces and Special Names . . . . . . . . . .   9
     3.9.  Alternate Response Encodings  . . . . . . . . . . . . . .   9
     3.10. Distribution and Managment of Root Servers  . . . . . . .  10
     3.11. Identifiers Versus Brands and Other Convenience Names . .  10
     3.12. A Single Hierarchy with a Centrally-controlled Root . . .  11
     3.13. Scaling of Reputation and Other Ancillary Information . .  11
   4.  Searching and the DNS - An Historical Note  . . . . . . . . .  12
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text