RFC 1900: Renumbering Needs Work
In plain English — editorial summary, not part of the RFC
Hosts in an IP network are identified by IP addresses, and the IP address prefixes of subnets are advertised by routing protocols. A change in such IP addressing information associated with a host or subnet is known as "renumbering". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1900
- Published
- February 1996
- Authors
- B. Carpenter; Y. Rekhter
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1627Network 10 Considered Harmful (Some Practices Shouldn't be Codified)Obsoleted
July 1994
- RFC 1597Address Allocation for Private InternetsObsoleted
March 1994
- RFC 1797Class A Subnet ExperimentCurrent
April 1995
- RFC 2011SNMPv2 Management Information Base for the Internet Protocol using SMIv2Obsoleted
November 1996
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2338Virtual Router Redundancy ProtocolObsoleted
April 1998
- RFC 2960Stream Control Transmission ProtocolObsoleted
October 2000
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 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?