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

Use binding lifetimes and contact timers correctly

03

T1/T2 contact behavior and the preferred/valid lifetime of individual bindings are different pieces of state.

Related RFCs and changes

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

DIAGRAM§ 14 ↗
RFC 9915 · § 14EXAMPLE
3 / 3
Use binding lifetimes and contact timers correctlyT1/T2 contact behavior and the preferred/valid lifetime of individual bindings are different pieces of state.PER-BINDING LIFETIMESaddressprefixRenew / Rebind contactExpired address removed; prefix tracked separatelyIllustrative intervals; contact is not automatic lifetime extension
03
Remove a binding whose valid lifetime expires without extension.

Remove a binding whose valid lifetime expires without extension.

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

Renewal and rebinding try to extend configuration before individual bindings expire.

  • Renewal and rebinding try to extend configuration before individual bindings expire.
  • A valid-lifetime expiry ends use even if a contact timer has not produced a successful response.
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. Choose a two-message or four-message exchange
  2. Keep address and prefix associations distinct
  3. Use binding lifetimes and contact timers correctly
  4. Carry link context in a relay envelope
  5. Separate configuration from trust and privacy
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗