DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?
RFC 8324

Document Type RFC - Informational (February 2018; Errata)
Last updated 2018-03-01
Stream ISE
Formats plain text pdf html bibtex
IETF conflict review conflict-review-klensin-dns-function-considerations
Stream ISE state Published RFC
Consensus Boilerplate Unknown
Document shepherd Nevil Brownlee
Shepherd write-up Show (last changed 2017-10-29)
IESG IESG state RFC 8324 (Informational)
Telechat date
Responsible AD (None)
Send notices to Nevil Brownlee <n.brownlee@auckland.ac.nz>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Independent Submission                                        J. Klensin
Request for Comments: 8324                                 February 2018
Category: Informational
ISSN: 2070-1721

    DNS Privacy, Authorization, Special Uses, Encoding, Characters,
          Matching, and Root Structure: Time for Another Look?

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 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 draw some clear lines about functionality that is
   not really needed or that should be performed in some other way.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not candidates for any level of Internet Standard;
   see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8324.

Klensin                       Informational                     [Page 1]
RFC 8324                      DNS Revisions                February 2018

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
   (https://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.

Klensin                       Informational                     [Page 2]
RFC 8324                      DNS Revisions                February 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Background and Hypothesis . . . . . . . . . . . . . . . . . .   5
   3.  Warts and Tensions with the Current DNS . . . . . . . . . . .   6
     3.1.  Multi-type Queries  . . . . . . . . . . . . . . . . . . .   6
     3.2.  Matching Part I: Case Sensitivity in Labels and Other
           Anomalies . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Matching Part II: Non-ASCII ("Internationalized") Domain
           Name Labels . . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Matching Part III: Label Synonyms, Equivalent Names, and
           Variants  . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Query Privacy . . . . . . . . . . . . . . . . . . . . . .  10
     3.6.  Alternate Namespaces for Public Use in the DNS Framework:
           The CLASS Problem . . . . . . . . . . . . . . . . . . . .  10
     3.7.  Loose Synchronization . . . . . . . . . . . . . . . . . .  10
     3.8.  Private Namespaces and Special Names  . . . . . . . . . .  11
     3.9.  Alternate Query or Response Encodings . . . . . . . . . .  12
     3.10. Distribution and Management of Root Servers . . . . . . .  12
     3.11. Identifiers versus Brands and Other Convenience Names . .  13
     3.12. A Single Hierarchy with a Centrally Controlled Root . . .  14
     3.13. Newer Application Protocols, New Requirements, and DNS
           Evolution . . . . . . . . . . . . . . . . . . . . . . . .  14
       3.13.1.  The Extensions . . . . . . . . . . . . . . . . . . .  15
       3.13.2.  Extensions and Deployment Pressures -- The TXT
                RRTYPE . . . . . . . . . . . . . . . . . . . . . . .  15
       3.13.3.  Periods and Zone Cut Issues  . . . . . . . . . . . .  16
     3.14. Scaling of Reputation and Other Ancillary Information . .  17
     3.15. Tensions among Transport, Scaling, and Content  . . . . .  18
   4.  The Inverse Lookup Requirement  . . . . . . . . . . . . . . .  19
   5.  Internet Scale, Function Support, and Incremental Deployment   20
   6.  Searching and the DNS -- An Historical Note . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  29
Show full document text