Android (lack of) support for DHCPv6

Wed Jun 10 05:52:48 UTC 2015

On Tue, Jun 9, 2015 at 10:35 PM, Mikael Abrahamsson <swmike at swm.pp.se>
wrote:

> What would you find acceptable behaviour from a device that finds itself
> on a wifi network that only gives it a single DHCPv6 IA_NA ? That some apps
> silently stop working because 464XLAT doesn't work, that it throws up a
> splash screen for the user to say that the network its connected to doesn't
> work, or that it just doesn't use this network and continues to use
> cellular (basically like it would one where the connection manager can't
> verify connectivity), and also that tethering won't work.

Isn't that the problem of the network operator?  To know and accept the
tradeoffs for how they operate their network?  If this theory that DHCPv6
is going to break the world comes true, then the operators will adjust
their methods.  Personally, I find operating a dual-stack network far
simpler than futzing with XLAT or NAT64. It is a known configuration vs. a
complete list of unknown gotchas in translation solutions.  Not to mention
the added complexity on the client and the network edge.