Visual RFC.
ALL RFCs / RFC 4862
Read the RFC ↗
RFC 4862 / PROTOCOL MECHANISMS

Renumber without an instant cutover

05

A host can hold old and new addresses while advertised prefixes and lifetimes change.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.1 ↗
RFC 4862 · § 4.1EXAMPLE
3 / 3
Renumber without an instant cutoverA host can hold old and new addresses while advertised prefixes and lifetimes change.old prefix → old addressnew prefix → new addressold: deprecated · new: preferredtransition intervalMultiple lifetimes permit gradual renumbering
03
Deprecate the old address while allowing appropriate existing traffic to continue.

Deprecate the old address while allowing appropriate existing traffic to continue.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Multiple address lifetimes allow a transition period.

  • Multiple address lifetimes allow a transition period.
  • Rogue Router Advertisements remain a security concern; lifetime rules include safeguards against particular attacks.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Form a tentative link-local address
  2. Check a tentative address for duplicates
  3. Combine an advertised prefix and identifier
  4. Track preferred and valid lifetimes
  5. Renumber without an instant cutover

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗