Renew before the lease expires
03A bound client first renews with its original server, then tries any server, and finally stops using an expired address.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 4.4.5 ↗
RFC 2131 · § 4.4.5EXAMPLE
4 / 4
04
Stop using the address.
Without a valid extension the client returns to initialization.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Expiry is a hard boundary on address use.
- T1 normally defaults to 50% of the lease; T2 to 87.5%. Servers may configure them.
- At T1 the client enters RENEWING and unicasts DHCPREQUEST to the original server.
- At T2 it enters REBINDING and broadcasts; if the lease expires without renewal, it must stop using the address.
These defaults may include random variation to avoid synchronized requests. An ACK that extends the lease resets the relevant timing.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy