RFC 2072: Router Renumbering Guide
In plain English — editorial summary, not part of the RFC
Routers interact with numerous network infrastructure servers, including DNS and SNMP. These interactions, not just the pure addressing and routing structure, must be considered as part of router renumbering. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2072
- Published
- January 1997
- Authors
- H. Berkowitz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 48
- Also known as
- —
- Updated by:
- RFC 4192
Topics
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 2071Network Renumbering Overview: Why would I want it and what is it anyway?Current
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?