RFC 1816: U.S. Government Internet Domain Names
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2146.
Current document in this lineage: RFC 2146 — U.S. Government Internet Domain Names
In plain English — editorial summary, not part of the RFC
This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1816
- Published
- August 1995
- Authors
- Federal Networking Council
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1811 (1995)
- RFC 1816 (1995)
- RFC 2146 (1997) ✓
Read the full history of U.S. Government Internet Domain Names →
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 1467Status of CIDR Deployment in the InternetCurrent
August 1993
- RFC 1367Schedule for IP Address Space Management GuidelinesObsoleted
October 1992
- RFC 1366Guidelines for Management of IP Address SpaceObsoleted
October 1992
- RFC 3232Assigned Numbers: RFC 1700 is Replaced by an On-line DatabaseCurrent
January 2002
- RFC 1881IPv6 Address Allocation ManagementCurrent
December 1995
- RFC 1917An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANACurrent
February 1996
- RFC 2036Observations on the use of Components of the Class A Address Space within the InternetCurrent
October 1996
- RFC 2860Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityCurrent
June 2000
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?