RFC 4477: Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues
In plain English — editorial summary, not part of the RFC
A node may have support for communications using IPv4 and/or IPv6 protocols. Such a node may wish to obtain IPv4 and/or IPv6 configuration settings via the Dynamic Host Configuration Protocol (DHCP). The original version of DHCP (RFC 2131) designed for IPv4 has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This document describes issues identified with dual IP version DHCP interactions, the most important aspect of which is how to handle potential problems in clients processing configuration information received from both DHCPv4 and DHCPv6 servers. The document makes a recommendation on the general strategy on how best to handle such issues and identifies future work to be undertaken. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4477
- Published
- May 2006
- Authors
- T. Chown; S. Venaas; C. Strauf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4436Detecting Network Attachment in IPv4 (DNAv4)Current
March 2006
- RFC 4433Mobile IPv4 Dynamic Home Agent (HA) AssignmentCurrent
March 2006
- RFC 4636Foreign Agent Error Extension for Mobile IPv4Current
October 2006
- RFC 4292IP Forwarding Table MIBCurrent
April 2006
- RFC 4242Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2005
- RFC 4193Unique Local IPv6 Unicast AddressesCurrent
October 2005
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4861Neighbor Discovery for IP version 6 (IPv6)Updated
September 2007
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?