Domain Names
draft-lewis-domain-names-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-09-30
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)
Independent Submission                                        E. Lewis
Internet-Draft                                                   ICANN
Expires: March 30, 2016                       Date: September 30, 2015
Intended Status: unknown

                            Domain Names
                    draft-lewis-domain-names-01.txt

Abstract

This document states a definition of Domain Name beyond the use of
the term within the Domain Name System.  The document includes a
survey of the diverse ways Domain Names have been interpreted within
various protocols over time.  The purpose of this is to give a solid
foundation for work on Domain Names across all protocols making use
of Domain Names.

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 March 30, 2016.

Copyright Notice

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

0.  NOTE TO RFC EDITOR AND REVIEWERS  . . . . . . . . . . . . . .   1
1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   1
2.  Reaching a definition of a Domain Name  . . . . . . . . . . .   1
3.  Subtypes of Domain Names  . . . . . . . . . . . . . . . . . .   1
4.  Interoperability Considerations   . . . . . . . . . . . . . .   1
5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   1
6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   1
7.  Security Considerations . . . . . . . . . . . . . . . . . . .   1
8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   1
9.  Authors' Addresses  . . . . . . . . . . . . . . . . . . . . .   1

0.  NOTE TO RFC EDITOR AND REVIEWERS

A suitable venue for discussion of this document is the dnsop working
group.  Private comments may also be directed at the editor.

This document will be presented to the Dispatch WG as it relates
to the use of identifiers across protocols, despite perceptions
that the DNS defines Domain Names.

This section (and sub-sections) should be removed prior to
publication.  

1. Introduction

Two or three decades into the history of Domain Names, a popular
notion has taken hold that Domains Names were defined and specified
STD 13, the definition of the Domain Name System (DNS).  The
definitions within RFC 1034 and RFC 1035 have become the
apparently-authoritative source for discussions on what is a Domain
Name.

The truth is, RFC 1034 and RFC 1035 do not define Domain Names, those
documents define only how Domain Names are used and processed in the
DNS.  But the way in which those RFCs are written seem to lend to the
confusion.

Throughout this document the term "Domain Names" is capitalized to
emphasize the concept of the names and DNS is used to describe the
protocol and algorithms described in STD 13, including any applicable
updates, related standards track documents and experimental track
documents.

The term domain is a generic term.  And there are many naming
systems in existence.  The use of the term Domain Names in this
document refers to the roughly-defined set of protocols and their
applications use of a naming structure that is prevalent amongst
many protocols defined in IETF RFC documents.

If there is a use of Domain Names not listed here it is merely an
omission.  The goal in this document is to provide a survey that
is sufficent to avoid hand-waving arguments, recognizing the dimishing
return in trying to build a complete roster of uses of Domain Names.
If there are omissions that ought to be included, please send
references for the use case to the author (while this is an Internet
Draft, that is).

1.1 Deconstructing RFC 1034's Introduction

RFC 1034, section 2 begins with this text:

"This RFC introduces domain style names, their use for Internet mail
Show full document text