RFC 4192: Procedures for Renumbering an IPv6 Network without a Flag Day
In plain English — editorial summary, not part of the RFC
This document describes a procedure that can be used to renumber a network from one prefix to another. It uses IPv6's intrinsic ability to assign multiple addresses to a network interface to provide continuity of network service through a "make-before-break" transition, as well as addresses naming and configuration management issues. It also uses other IPv6 features to minimize the effort and time required to complete the transition from the old prefix to the new prefix. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4192
- Published
- September 2005
- Authors
- F. Baker; E. Lear; R. Droms
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 22
- Also known as
- —
- Updates:
- RFC 2072
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4177Architectural Approaches to Multi-homing for IPv6Current
September 2005
- RFC 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- RFC 4148IP Performance Metrics (IPPM) Metrics RegistryObsoleted
August 2005
- RFC 4116IPv4 Multihoming Practices and LimitationsCurrent
July 2005
- RFC 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- RFC 4029Scenarios and Analysis for Introducing IPv6 into ISP NetworksCurrent
March 2005
- RFC 3956Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast AddressUpdated
November 2004
- RFC 3904Evaluation of IPv6 Transition Mechanisms for Unmanaged NetworksCurrent
September 2004
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?