RFC 3736: Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6
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
Stateless Dynamic Host Configuration Protocol service for IPv6 (DHCPv6) is used by nodes to obtain configuration information, such as the addresses of DNS recursive name servers, that does not require the maintenance of any dynamic state for individual clients. A node that uses stateless DHCP must have obtained its IPv6 addresses through some other mechanism, typically stateless address autoconfiguration. This document explains which parts of RFC 3315 must be implemented in each of the different kinds of DHCP agents so that agent can support stateless DHCP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3736
- Published
- April 2004
- Authors
- R. Droms
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- 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 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3634Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) OptionCurrent
December 2003
- RFC 3633IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6Obsoleted
December 2003
- RFC 3594PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) OptionCurrent
September 2003
- RFC 3925Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)Current
October 2004
- RFC 3495Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client ConfigurationCurrent
March 2003
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 3256The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-optionCurrent
April 2002
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?