RFC 3071: Reflections on the DNS, RFC 1591, and Categories of Domains
In plain English — editorial summary, not part of the RFC
This document is being published primarily for historical context and comparative purposes, essentially to document some thoughts about how 1591 might have been interpreted and adjusted by the Internet Assigned Numbers Authority (IANA) and ICANN to better reflect today's world while retaining characteristics and policies that have proven to be effective in supporting Internet growth and stability. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3071
- Published
- February 2001
- Authors
- J. Klensin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1591Domain Name System Structure and DelegationCurrent
March 1994
- RFC 1480The US DomainCurrent
June 1993
- RFC 1386The US DomainObsoleted
December 1992
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 3088OpenLDAP Root Service An experimental LDAP referral serviceCurrent
April 2001
- RFC 3152Delegation of IP6.ARPAObsoleted
August 2001
- RFC 2352A Convention For Using Legal Names as Domain NamesCurrent
May 1998
- RFC 2345Domain Names and Company Name RetrievalCurrent
May 1998
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?