|Internet protocol suite|
IPv6 hosts can acquire IP addresses using stateless address autoconfiguration, or by using DHCPv6. DHCP tends to be preferred at sites where central management of hosts is valued; stateless autoconfiguration does not require any sort of central management, and is therefore preferable in networks where no management is readily available, such as a typical home network.
IPv6 hosts that use stateless autoconfiguration may require information other than an IP address. DHCPv6 can be used to acquire this information, even though it is not being used to configure IP addresses. DHCPv6 is not necessary for configuring Domain Name System servers—they can be configured using Neighbor Discovery Protocol, which is needed anyway for stateless autoconfiguration.
IPv6 routers, such as home routers, must be configured automatically with no operator intervention. Such routers require not only an IPv6 address for use in communicating with upstream routers, but also an IPv6 prefix for use in configuring devices on the downstream side of the router. DHCPv6 Prefix delegation provides a mechanism for configuring such routers.
Port numbers 
DHCPv6 uses UDP port number 546 for clients and port number 547 for servers.
DHCP Unique Identifier 
The DHCP Unique Identifier (DUID) is used by a client to get an IP address from a DHCPv6 server. It has a minimum length of 12 bytes (96 bits) and a maximum length of 20 bytes (160 bits). Its actual length depends on its type. The server compares the DUID with its database and delivers configuration data (address, lease times, DNS servers, etc.) to the client. The first 16 bits of a DUID contain the DUID type, of which there are three types. The meaning of the remaining 96 bits depend on the DUID type.
In this example, the server's link-local address is
fe80::0011:22ff:fe33:5566 and the client's link-local address is
- DHCPv6 client sends a Solicit from
- DHCPv6 server replies with an Advertise from
- DHCPv6 client replies with a Request from
[ff02::1:2]:547. (All client messages are sent to the multicast address, per section 13 of RFC 3315.)
- DHCPv6 server finishes with a Reply from
IETF standards 
- RFC 3315, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"
- RFC 3319, "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers"
- RFC 3633, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"
- RFC 3646, "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"
- RFC 3736, "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6"
- RFC 5007, "DHCPv6 Leasequery"
- RFC 6221, "Lightweight DHCPv6 Relay Agent"
- RFC 4339, IPv6 Host Configuration of DNS Server Information Approaches, J. Jeong (February 2006)
- IPv6 Intelligence: DHCPv6, comparison of DHCPv6 packages and implementations (Last updated: April, 2009)
- IPv6 Ready: DHCPv6, list of IPv6 Phase II Certified DHCPv6 implementations (Last updated: December, 2012)
|This computer networking article is a stub. You can help Wikipedia by expanding it.|