Depending on DHCP to audit trail is flawed, because it is easy to spoof addresses.
Unless, of course, you're restricting traffic to prevent spoofing: in which case you could be doing the same for addresses assigned by SLAAC just as easily.
SLAAC also has a lot to offer for faster configuration of mobile devices roaming between networks.
Apparently OS X now supports supplying DNS servers through SLAAC. Previously this wasn't supported, so you'd still need a DHCP(v4) server to fully support a client.
> Apparently OS X now supports supplying DNS servers through SLAAC
i thought this was done via router-advertisements only. slaac is used to configure v6 host addresses, and once that is done, other network parameters e.g. rdnss etc. can be obtained either via RA or DHCPv6 (the 'O' flag in RA messages)
I predict that things will turn out fine because people will converge on speaking SLAAC between OS X and the router and DHCPv6-PD between the router and the ISP. But you have to have a router.