RFC 3467: Role of the Domain Name System (DNS)
In plain English — editorial summary, not part of the RFC
This document reviews the original function and purpose of the domain name system (DNS). It contrasts that history with some of the purposes for which the DNS has recently been applied and some of the newer demands being placed upon it or suggested for it. A framework for an alternative to placing these additional stresses on the DNS is then outlined. This document and that framework are not a proposed solution, only a strong suggestion that the time has come to begin thinking more broadly about the problems we are encountering and possible approaches to solving them. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3467
- Published
- March 2003
- Authors
- J. Klensin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 7613Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsObsoleted
August 2015
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 3454Preparation of Internationalized Strings ("stringprep")Obsoleted
January 2003
- RFC 3490Internationalizing Domain Names in Applications (IDNA)Obsoleted
March 2003
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 5335Internationalized Email HeadersObsoleted
September 2008
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?