Re: Android (lack of) support for DHCPv6

[Mikael Abrahamsson <swmike () swm pp se>]

On Tue, 9 Jun 2015, Joel Maslak 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?

You don't need to hand out addresses by means of DHCPv6 IA_NA to windows, 
it does A=1 mode for SLAAC just fine.

There is a big difference between handing out resolver, ntp-server, dns 
search domains etc by means of DHCPv6, and handing out addresses based on 
DHCPv6 (stateless vs stateful).

> From what I have understood Android has made design decisions that means 
some things will break if you would only give is a single IPv6 address. 
This is most likely what some operators want to achieve when they say they 
want to use DHCPv6 IA_NA.

In order to actually solve the problem they're trying to solve, you need 
SAVI (https://tools.ietf.org/wg/savi/) and 802.1x (or similar mechanism) 
in order to actually gain the control these people are looking for. My 
question, do they implement this on IPv4?

--
Mikael Abrahamsson    email: swmike () swm pp se