The Everything Feed - All Packet Pushers Pods IPB197: SLAAC and the End of DHCP?
Apr 2, 2026
They dig into why SLAAC is essential for CLAT in IPv6-mostly deployments and how it enables IPv6 operation for legacy apps. They compare IPv6-mostly, v6-only, and dual stack approaches. They discuss enterprise friction with SLAAC, tracking and accountability options, standards work for SLAAC-to-DHCPv6 registration, and operational workarounds like 802.1x and zero trust.
AI Snips
Chapters
Transcript
Episode notes
What IPv6 Mostly Actually Means
- IPv6 mostly lets hosts use the highest-level IP capability they support, falling back only when necessary.
- Ed Orley explains hosts will run IPv6-only with CLAT, or dual stack/IPv4 if features are missing, easing gradual migration.
SLAAC Is Core To IPv6 Mostly
- SLAAC plus CLAT/NAT64/DNS64 are required to make IPv6 mostly functional on clients.
- Tom Coffeen and Ed Orley emphasize DHCPv6 option 108 and prefix discovery are necessary for CLAT activation and translation to work.
Why CLAT Requires SLAAC Addresses
- CLAT needs a unique IPv6 address independent of the host OS to function.
- Ed Orley explains DHCPv6 typically assigns one /128 per client so it can't provide the second address the CLAT needs.