What's in a Name: False Assumptions about DNS Names
RFC 4367, “What's in a Name: False Assumptions about DNS Names”, is an Informational document published in February 2006 by J. Rosenberg, IAB. The canonical text is published by the RFC Editor.
Abstract
The Domain Name System (DNS) provides an essential service on the Internet, mapping structured names to a variety of data, usually IP addresses. These names appear in email addresses, Uniform Resource Identifiers (URIs), and other application-layer identifiers that are often rendered to human users. Because of this, there has been a strong demand to acquire names that have significance to people, through equivalence to registered trademarks, company names, types of services, and so on. There is a danger in this trend; the humans and automata that consume and use such names will associate specific semantics with some names and thereby make assumptions about the services that are, or should be, provided by the hosts associated with the names. Those assumptions can often be false, resulting in a variety of failure conditions. This document discusses this problem in more detail and makes recommendations on how it can be avoided. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4367 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4366 Transport Layer Security Extensions
- RFC 4368 Multiprotocol Label Switching Label-Controlled Asynchronous Transfer Mode and Frame-Relay Management Interface Definition
- RFC 4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks
- RFC 4369 Definitions of Managed Objects for Internet Fibre Channel Protocol
- RFC 4364 BGP/MPLS IP Virtual Private Networks
- RFC 4370 Lightweight Directory Access Protocol Proxied Authorization Control
- RFC 4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions
- RFC 4371 BCP 101 Update for IPR Trust