SLAAC will never exist on anything I control if I have any say in the matter
Then you're not using any Android devices, which still doesn't support DHCP6
I use IP6 on all my android devices, but then i statically configure the IP from start-up scripts (by the way, has anyone had issues with android 5+ routing ip6 tcp off lan? udp6 seems to work, i can't get tcp6 to work on the newer boxes I run)
But yeah, if android over ip6 has to be supported now, and it doesn't support dhcp6 then i guess you're right.. Up to now, though, all androids I've seen have been IP4 only from the 'consumer' side of things.
I agree that SLAAC sucks, but there is one valid use case: on home networks with dynamic addressing. If the line drops and reconnects, you need to renumber your devices very quickly, which would mean extremely short lease times if using DHCP6.
Now you say, surely IPv6 has enough address space to give everyone a static allocation? It certainly does, but dynamic addressing is not due to shortage of address space: it's due to route aggregation.
I realise many ISPs will still give out dynamic Ip6 prefixes when they start doing ip6... But you make a good point regarding the renumbering... I hadn't thought of that.... A "cost" of not using NAT! You could always use NAT6 <gets coat> :-)
How would slaac help though? Surely in either situation a machine needs to repoll for its new IP, or have it pushed.. It surely would be the same for a dhcp'd or slacc'ed host to realise its ip was no longer valid, and need to be updates?