RFC 4242: Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8415.
Current document in this lineage: RFC 9915 — Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
This document describes a Dynamic Host Configuration Protocol for IPv6 (DHCPv6) option for specifying an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6. It is used with stateless DHCPv6 as there are no addresses or other entities with lifetimes that can tell the client when to contact the DHCPv6 server to refresh its configuration. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4242
- Published
- November 2005
- Authors
- S. Venaas; T. Chown; B. Volz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
- Obsoleted by:
- RFC 8415
Topics
Standards lineage
This document is one revision in a chain of 9 RFCs, each formally replacing the one before it.
- RFC 3315 (2003)
- RFC 3633 (2003)
- RFC 3736 (2004)
- RFC 4242 (2005)
- RFC 7083 (2013)
- RFC 7283 (2014)
- RFC 7550 (2015)
- RFC 8415 (2018)
- RFC 9915 (2026) ✓
Read the full history of Dynamic Host Configuration Protocol for IPv6 (DHCPv6) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4193Unique Local IPv6 Unicast AddressesCurrent
October 2005
- RFC 4292IP Forwarding Table MIBCurrent
April 2006
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4087IP Tunnel MIBCurrent
June 2005
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 2005
- RFC 4064Experimental Message, Extensions, and Error Codes for Mobile IPv4Current
May 2005
- RFC 4433Mobile IPv4 Dynamic Home Agent (HA) AssignmentCurrent
March 2006
- RFC 4436Detecting Network Attachment in IPv4 (DNAv4)Current
March 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?