Hacker News Reader

All of these things already exist for IPv6, although I don't know how much DHCPv6 is deployed in practice.

It should be deployed everywhere where IPv6 is deployed and there's an IT department if only for logging/audit.

Stateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android. And I in fact agree with them.

And DHCPv6 isn't needed for logging/audit: the router always has an association of MAC addresses and IPv6 addresses even if hosts assign their own addresses with SLAAC.

> Stateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android.

Which is absolutely ridiculous. Google should not be trying to dictate to their customers how to run infrastructure. If someone wants to use stateful DHCPv6 for their Android devices, that is their right and Google has no business standing in their way.

IPv6 DHCP isn't the same as IPv4 DHCP though. It doesn't work very well for logging and audits. It's more for assigning prefixs to routers.

Regrettably little, mainly because Lorenzo Colitti who is in charge of the Google Android network stack refuses to support it.

His justification for not supported stateful dhcpv6 is completely reasonable and I wish more platforms had come to the same conclusions.

Reply on news.ycombinator.com