RFC 2071: Network Renumbering Overview: Why would I want it and what is it anyway?
In plain English — editorial summary, not part of the RFC
This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2071
- Published
- January 1997
- Authors
- P. Ferguson; H. Berkowitz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2072Router Renumbering GuideUpdated
January 1997
- RFC 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 2194Review of Roaming ImplementationsCurrent
September 1997
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
October 1995
- RFC 2330Framework for IP Performance MetricsUpdated
May 1998
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
- RFC 2432Terminology for IP Multicast BenchmarkingCurrent
October 1998
- RFC 2477Criteria for Evaluating Roaming ProtocolsCurrent
January 1999
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?