RE: Android (lack of) support for DHCPv6

["Paul B. Henson" <henson () acm org>]

> From: Ray Soucy
> Sent: Wednesday, June 10, 2015 6:06 AM
>
> As for thinking "long term" and "the future", we need devices to work
> within current models of IPv6 to accelerate _adoption_ of IPv6 _today_
> before we can get to that future you're talking about.
>
> Not supporting DHCPv6 ultimately holds back adoption, which makes people
> see IPv6 as optional for longer, and discourages deployment because vendor
> support is all over the place and seen as "not ready".
>
> This isn't theory, we've been _living_ with this as a reality for years
> now.  The networks are ready; the clients are not.
>
> Universities see a constant stream of DMCA violation notices that need to
> be dealt with and not being able to associate a specific IPv6 address to a
> specific user is a big enough liability that the only option is to not use
> IPv6.  As I said, Android becomes a second class citizen on the network
> under your model.

Your ideas are intriguing to me and I wish to subscribe to your newsletter ;).

When someone shows up with a device that only supports WEP, or doesn't support WPA2-Enterprise, we tell them they need 
to replace it with a device supporting current standards that provide the minimum level of security we have decided 
upon for our network policy. When someone shows up with an android device that can't connect to our IPv6 network, we 
will tell them to replace it with a device that fully supports current standards.

I still find it hard to believe that Google as a corporate entity thinks it is more important to try and force network 
operators to conform to their ideals for configuration than it is to make android feature equivalent with its 
competitors.