RFC 2008: Implications of Various Address Allocation Policies for Internet Routing
In plain English — editorial summary, not part of the RFC
The purpose of this document is to articulate certain relevant fundamental technical issues that must be considered in formulating unicast address allocation and management policies for the Public Internet, and to provide recommendations with respect to these policies. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2008
- Published
- October 1996
- Authors
- Y. Rekhter; T. Li
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops-old
- Pages
- 13
- Also known as
- BCP7
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2011SNMPv2 Management Information Base for the Internet Protocol using SMIv2Obsoleted
November 1996
- RFC 1937"Local/Remote" Forwarding Decision in Switched Data Link SubnetworksCurrent
May 1996
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 1887An Architecture for IPv6 Unicast Address AllocationCurrent
December 1995
- RFC 1886DNS Extensions to support IP version 6Obsoleted
December 1995
- RFC 1885Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)Obsoleted
December 1995
- RFC 1884IP Version 6 Addressing ArchitectureObsoleted
December 1995
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?