RFC 8415 / START HERE
DHCPv6, before the details
DHCPv6: DHCP for IPv6
DHCP means Dynamic Host Configuration Protocol. DHCPv6 lets IPv6 clients obtain configuration and can delegate address prefixes to downstream routers.
The idea in one picture
An IPv6 client asks
DHCPv6 supplies configuration
Addresses or prefixes are managed
A simplified picture of the idea; the chapters explain the actual mechanisms.
Why it exists
Some networks need centrally managed addresses or configuration in addition to what router advertisements provide. This guide covers the 2018 publication.
A familiar example
A home router asks a provider for an IPv6 prefix that it can use on its own local networks.
Helpful background
You can start here without reading another RFC. If these ideas are unfamiliar, these short introductions may help.
What you’ll learn next
Begin with chapter one, or choose a topic.
- Select a server and request configurationA typical DHCPv6 allocation uses Solicit, Advertise, Request, and Reply.→
- Group bindings using DUID and IAIDA DHCP Unique Identifier identifies a participant; an Identity Association groups related leases under an IAID.→
- Delegate a prefix to a routerAn IA_PD requests and carries delegated prefixes for a downstream router rather than a single host address.→
- Renew or rebind before validity endsA client renews with the selected server and can later rebind to available servers.→
- Encapsulate an exchange through relaysRelay-forward and Relay-reply messages carry client exchanges across the relay path.→
This introduction explains RFC 8415 (2018). This publication has a successor; see the related guides and the RFC status. Read the original RFC ↗