[180673] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Doug Clements)
Tue Jun 9 16:42:54 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CADb+6TAdbgVy3ZqXFQYqFV+QBR6T1G6Qd77obhFO9EkCRnHJnw@mail.gmail.com>
Date: Tue, 9 Jun 2015 16:40:13 -0400
From: Doug Clements <dclements@gmail.com>
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Tue, Jun 9, 2015 at 4:27 PM, Joel Maslak <jmaslak@antelope.net> wrote:
> Agreed - apparently the solution is to implement SLAAC + DNS advertisements
> *AND* DHCPv6. Because you need SLAAC + DNS advertisements for Android, and
> you need DHCPv6 for Windows.
>
> Am I the only one that thinks this situation is stupid?
>
If you think this is stupid, look in to the situation for modern WiFi and
Android.
https://code.google.com/p/android/issues/detail?id=17972
https://code.google.com/p/android/issues/detail?id=59502
https://code.google.com/p/android/issues/detail?id=62076
Summary:
- No 802.11k (though 802.11r in barely new devices)
- No DFS Channel support in Nexus-branded units, due to Google's resistance
to certification.
- Most WPA2-Enterprise schemes are sullied with warnings about traffic
being monitored as a response to private CAs being installed.
Windows support for enterprise features is downright stellar in comparison.
--Doug
