[c4mpute]

DHCPv6 is useless on mobile devices.

Mobile devices typically (read: by default, and if they don't people will berate them for not caring about privacy) randomize the DHCPv6 DUID and MAC address used for the connection, meaning that one might as well just assign a random IPv6 address from the given prefix. Which is exactly what you get without DHCPv6.

The only people demanding DHCPv6 in Android are network admins still under the strange illusion that DHCP somehow gives them some kind of "management", "accountability" or "logs". They didn't get the memo that they will still have to correlate their 802.1x auth with the current device mac and IPv6 addresses in use, which is in no way whatsoever helped by DHCPv6.

[RKearney]

Remember, Android doesn't only run on mobile phones and managed addresses are just one part of DHCPv6.

You seem to be completely ignoring the other aspects of DHCPv6. Your response comes off as extremely hostile towards others who may have different requirements than yours. Please consider that there could be other use cases beyond what you've been exposed to in the past.

[c4mpute]

Well, then be so kind as to enlighten me about those important android devices that aren't mobile phones and are in urgent need of DHCPv6.

And what might those other aspects of DHCPv6 be? That it is an ugly misdesign that doesn't even do what DHCPv4 does? That e.g. MAC-address-based address distribution is against the DHCPv6 spec and either a broken oversight or a design flaw? That DUIDs are either a privacy nightmare or useless crap? Which use cases should I consider there, pray tell...