By Any Other Name: Considerations on DNS, Other Naming Protocols, and the Hierarchical Domain Name Space
draft-sullivan-draft-sullivan-namespaces-and-dns-00

Document Type Expired Internet-Draft (individual)
Author Andrew Sullivan 
Last updated 2014-08-18 (latest revision 2014-02-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sullivan-draft-sullivan-namespaces-and-dns-00.txt

Abstract

You should probably not read this. It's not done. Not every domain name is intended to appear in the global DNS. It is also possible that not everything that looks like a domain name is intended to be one. Regardless of whether a given name is intended to appear in the DNS, such names often turn up in domain name slots. When choosing a naming scheme that is not intended to be part of the global DNS, it is necessary to understand the architectural implications of using domain names or a domain-name-like syntax.

Authors

Andrew Sullivan (asullivan@dyn.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)