RFC Origins of Domain Names
draft-lewis-domain-names-13

Document Type Active Internet-Draft (individual)
Last updated 2019-08-22 (latest revision 2019-08-06)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf html bibtex
IETF conflict review conflict-review-lewis-domain-names
Stream ISE state In IESG Review
IESG Review Completed
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-08-14)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                           E. Lewis
Internet-Draft                                                     ICANN
Intended status: Informational                            August 6, 2019
Expires: February 7, 2020

                      RFC Origins of Domain Names
                      draft-lewis-domain-names-13

Abstract

   Is the concept of Domain Names owned by the DNS protocol or does the
   DNS protocol exist to support the concept of Domain Names?  This
   question has become pertinent in light of proposals to use Domain
   Names in protocols in ways incompatible with the DNS protocol and the
   operational environment built to run the protocol.

   This document is intended to help answer this question by presenting
   a look into the recorded history of relevant Requests for Comments.
   This document comprises the research and views of the author and has
   benefited from review and input from many IETF experts, but it does
   not represent the consensus opinion of the IETF.

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 February 7, 2020.

Copyright Notice

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

Lewis                   Expires February 7, 2020                [Page 1]
Internet-Draft         RFC Origins of Domain Names           August 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Goal  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Early RFCs  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Emergence of Domain Names . . . . . . . . . . . . . . . . . .   6
     3.1.  The Term "Domain Name" Itself . . . . . . . . . . . . . .   7
     3.2.  The Term "Resolve"  . . . . . . . . . . . . . . . . . . .   8
     3.3.  Where Does It Start?  . . . . . . . . . . . . . . . . . .   9
   4.  Dialects, So To Speak, of Domain Names  . . . . . . . . . . .  10
     4.1.  Domain Names in the DNS . . . . . . . . . . . . . . . . .  10
     4.2.  Host Names  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.3.  URI Authority and Domain Names  . . . . . . . . . . . . .  12
     4.4.  Internet Protocol Address Literals  . . . . . . . . . . .  12
     4.5.  Internationalized Domain Names in Applications  . . . . .  12
     4.6.  Restricted for DNS Registration . . . . . . . . . . . . .  13
     4.7.  Tor Network Names . . . . . . . . . . . . . . . . . . . .  13
     4.8.  X.509 . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.9.  Multicast DNS . . . . . . . . . . . . . . . . . . . . . .  14
     4.10. /etc/hosts  . . . . . . . . . . . . . . . . . . . . . . .  14
     4.11. Other Protocols . . . . . . . . . . . . . . . . . . . . .  14
     4.12. Other Others  . . . . . . . . . . . . . . . . . . . . . .  15
   5.  Interoperability Considerations . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   9.  Informational References  . . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Which came first, the concept of Domain Names or the DNS?  This
   question is at the heart of whether or how Domain Names are put to
   use in ways avoiding the DNS protocol.

   The discussion leading to "The '.onion' Special-Use Domain Name"
   [RFC7686], a document designating "onion" as a top-level domain in
   the Special Use Domain Names registry (see "Special Use Domain Names"
Show full document text