RFC 4367: What's in a Name: False Assumptions about DNS Names
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4367
- Published
- February 2006
- Authors
- J. Rosenberg; IAB
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5507Design Choices When Expanding the DNSCurrent
April 2009
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
- RFC 4470Minimally Covering NSEC Records and DNSSEC On-line SigningCurrent
April 2006
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
- RFC 4185National and Local Characters for DNS Top Level Domain (TLD) NamesCurrent
October 2005
- RFC 4159Deprecation of "ip6.int"Current
August 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?