RFC 1916: Enterprise Renumbering: Experience and Information Solicitation
In plain English — editorial summary, not part of the RFC
Because of the urgent need for, and substantial difficulty in, renumbering IP networks, the PIER working group is compiling a series of documents to assist sites in their renumbering efforts. The intent of these documents is to provide both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1916
- Published
- February 1996
- Authors
- H. Berkowitz; P. Ferguson; W. Leland; P. Nesser
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 3413Simple Network Management Protocol (SNMP) ApplicationsCurrent
December 2002
- RFC 1856The Opstat Client-Server Model for Statistics RetrievalCurrent
September 1995
- RFC 2377Naming Plan for Internet Directory-Enabled ApplicationsUpdated
September 1998
- RFC 2502Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast EnvironmentCurrent
February 1999
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 3125Electronic Signature PoliciesCurrent
September 2001
- RFC 3150End-to-end Performance Implications of Slow LinksCurrent
July 2001
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?