RFC 2240: A Legal Basis for Domain Name Allocation
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2352.
Current version: RFC 2352 — A Convention For Using Legal Names as Domain Names
In plain English — editorial summary, not part of the RFC
The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2240
- Published
- November 1997
- Authors
- O. Vaughan
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 2352
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2345Domain Names and Company Name RetrievalCurrent
May 1998
- RFC 1876A Means for Expressing Location Information in the Domain Name SystemCurrent
January 1996
- RFC 1788ICMP Domain Name MessagesObsoleted
April 1995
- RFC 1591Domain Name System Structure and DelegationCurrent
March 1994
- RFC 1480The US DomainCurrent
June 1993
- RFC 1464Using the Domain Name System To Store Arbitrary String AttributesCurrent
May 1993
- RFC 3071Reflections on the DNS, RFC 1591, and Categories of DomainsCurrent
February 2001
- RFC 1394Relationship of Telex Answerback Codes to Internet DomainsCurrent
January 1993
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?