RFC 2894: Router Renumbering for IPv6
In plain English — editorial summary, not part of the RFC
This document defines a mechanism called Router Renumbering ("RR") which allows address prefixes on routers to be configured and reconfigured almost as easily as the combination of Neighbor Discovery and Address Autoconfiguration works for hosts. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2894
- Published
- August 2000
- Authors
- M. Crawford
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 3019IP Version 6 Management Information Base for The Multicast Listener Discovery ProtocolObsoleted
January 2001
- RFC 2711IPv6 Router Alert OptionUpdated
October 1999
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
- RFC 2675IPv6 JumbogramsCurrent
August 1999
- RFC 3122Extensions to IPv6 Neighbor Discovery for Inverse Discovery SpecificationCurrent
June 2001
- RFC 2590Transmission of IPv6 Packets over Frame Relay Networks SpecificationUpdated
May 1999
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 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?