RFC 2050: Internet Registry IP Allocation Guidelines
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7020.
Current document in this lineage: RFC 7020 — The Internet Numbers Registry System
In plain English — editorial summary, not part of the RFC
This document describes the registry system for the distribution of globally unique Internet address space and registry operations. Particularly this document describes the rules and guidelines governing the distribution of this address space. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2050
- Published
- November 1996
- Authors
- K. Hubbard; M. Kosters; D. Conrad; D. Karrenberg; J. Postel
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 13
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1366 (1992)
- RFC 1466 (1993)
- RFC 2050 (1996)
- RFC 7020 (2013) ✓
Read the full history of The Internet Numbers Registry System →
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 1814Unique Addresses are GoodCurrent
June 1995
- RFC 2142Mailbox Names for Common Services, Roles and FunctionsCurrent
May 1997
- RFC 2339An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 ProtocolsCurrent
May 1998
- RFC 1375Suggestion for New Classes of IP AddressesCurrent
October 1992
- RFC 2780IANA Allocation Guidelines For Values In the Internet Protocol and Related HeadersUpdated
March 2000
- RFC 3069VLAN Aggregation for Efficient IP Address AllocationCurrent
February 2001
- RFC 3094Tekelec's Transport Adapter Layer InterfaceCurrent
April 2001
- RFC 3232Assigned Numbers: RFC 1700 is Replaced by an On-line DatabaseCurrent
January 2002
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?