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

Renew or rebind before validity ends

04

A client renews with the selected server and can later rebind to available servers.

This guide explains the 2018 publication. Superseded by RFC 9915.

Related RFCs and changes

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

RFC 8415 · § 18.2.4EXAMPLE
3 / 3
Renew or rebind before validity endsA client renews with the selected server and can later rebind to available servers.T1Renew original serverT2Rebind available serversValid lifetime expires → stop useContact timers and individual binding lifetimes are distinct
03
Without a valid extension, an expired binding can no longer be used.

Without a valid extension, an expired binding can no longer be used.

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

T1 and T2 govern renewal and rebinding for the IA where applicable.

  • T1 and T2 govern renewal and rebinding for the IA where applicable.
  • Preferred and valid lifetimes of individual bindings remain distinct from those contact timers.
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. Select a server and request configuration
  2. Group bindings using DUID and IAID
  3. Delegate a prefix to a router
  4. Renew or rebind before validity ends
  5. Encapsulate an exchange through relays
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗