Procedures for Renumbering an IPv6 Network without a Flag Day
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 22
- Abstract
- 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.
- Publication Date
- 2005-09-01
- Status Note
- Informational
- DOI
10.17487/RFC4192- Link
- https://doi.org/10.17487/RFC4192
- Author(s)
- Fred BakerEliot LearRalph Droms
- Keyword(s)
- IP, Make-Before-Break
Latest version of IETF RFC 4192
Document Versions — IETF RFC 4192
-
▶ IETF RFC 4192 (2005-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2072 [Active*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 2461 [Superseded*]
- IETF RFC 2462 [Superseded*]
- IETF RFC 3315 [Superseded*]
- IETF RFC 3704 [Active*]
Bibliographic Reference(s)
- Sangli, S., Rekhter, Y., Fernando, R., Scudder, J. and E. Chen, "Graceful Restart Mechanism for BGP", Work in Progress, June 2004. EXTERNAL
- von Clausewitz, C., Howard, M., Paret, P. and D. Brodie, "On War, Chapter VII, 'Friction in War'", June 1989. EXTERNAL
- Durand, A., Ihren, J. and P. Savola, "Operational Considerations and Issues with IPv6 DNS", Work in Progress, October 2004. EXTERNAL
- IETF RFC 1305 [Superseded*]
- IETF RFC 1995 [Active*]
- IETF RFC 1996 [Active*]
- IETF RFC 2136 [Active*]
- IETF RFC 2827 [Active*]
- IETF RFC 2845 [Superseded*]
- IETF RFC 2931 [Active*]
- IETF RFC 3007 [Active*]
- IETF RFC 3177 [Superseded*]
- IETF RFC 3633 [Superseded*]
- IETF RFC 3871 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4034 [Active*]
- IETF RFC 4035 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4192.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4192, Procedures for Renumbering an IPv6 Network without a Flag Day. Available at https://doi.org/10.17487/RFC4192
Snippet:
IETF RFC 4192, Procedures for Renumbering an IPv6 Network without a Flag Day. Available at https://doi.org/10.17487/RFC4192
HTML (ISO 690 compliant)
Preview:
IETF RFC 4192, Procedures for Renumbering an IPv6 Network without a Flag Day. Available at https://doi.org/10.17487/RFC4192
Snippet:
<span class="citation"><cite>IETF RFC 4192</cite>, Procedures for Renumbering an IPv6 Network without a Flag Day. Available at <a href="https://doi.org/10.17487/RFC4192" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4192</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4192, Procedures for Renumbering an IPv6 Network without a Flag Day
doi: 10.17487/RFC4192
url: https://doi.org/10.17487/RFC4192
doi: 10.17487/RFC4192
url: https://doi.org/10.17487/RFC4192
Snippet:
<li> <cite id="bib-rfc4192">IETF RFC 4192</cite>, Procedures for Renumbering an IPv6 Network without a Flag Day <span class="doi">10.17487/RFC4192</span> </li>
Referenced By
- IETF RFC 4472 [Active*]