IETF RFC 4367
[ACTIVE]
What's in a Name: False Assumptions about DNS Names
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- 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.
- Publication Date
- 2006-02-01
- Status Note
- Informational
- DOI
10.17487/RFC4367- Link
- https://doi.org/10.17487/RFC4367
- Author(s)
- Jonathan RosenbergIAB
- Keyword(s)
- DNS
Latest version of IETF RFC 4367
Document Versions — IETF RFC 4367
-
▶ IETF RFC 4367 (2006-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Faltstrom, P., "Design Choices When Expanding DNS" , Work in Progress, June 2005. EXTERNAL
- IETF RFC 1034 [Active*]
- IETF RFC 1122 [Active*]
- IETF RFC 1876 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2219 [Active*]
- IETF RFC 2326 [Superseded*]
- IETF RFC 2533 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2703 [Active*]
- IETF RFC 2782 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 2826 [Active*]
- IETF RFC 2912 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3262 [Active*]
- IETF RFC 3310 [Active*]
- IETF RFC 3403 [Active*]
- IETF RFC 3675 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4367.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4367, What's in a Name: False Assumptions about DNS Names. Available at https://doi.org/10.17487/RFC4367
Snippet:
IETF RFC 4367, What's in a Name: False Assumptions about DNS Names. Available at https://doi.org/10.17487/RFC4367
HTML (ISO 690 compliant)
Preview:
IETF RFC 4367, What's in a Name: False Assumptions about DNS Names. Available at https://doi.org/10.17487/RFC4367
Snippet:
<span class="citation"><cite>IETF RFC 4367</cite>, What's in a Name: False Assumptions about DNS Names. Available at <a href="https://doi.org/10.17487/RFC4367" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4367</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4367, What's in a Name: False Assumptions about DNS Names
doi: 10.17487/RFC4367
url: https://doi.org/10.17487/RFC4367
doi: 10.17487/RFC4367
url: https://doi.org/10.17487/RFC4367
Snippet:
<li> <cite id="bib-rfc4367">IETF RFC 4367</cite>, What's in a Name: False Assumptions about DNS Names <span class="doi">10.17487/RFC4367</span> </li>
Referenced By
- IETF RFC 6950 [Active*]