Re: [v6ops] Question re. stateless DHCPv6 and 'M' & 'O' flags

[Tomoyuki Sahara <[e-mail]>]

Hi,

> On May 15, 2015, at 15:21, Liubing (Leo) <[e-mail]> wrote:
> 
>> [Bing] (Speak as a co-author) We indeed didn't test the case as you said
>> above, but we tested a similar case: at initial stage, when A=0,M=0, and O=1,
>> some platform would start stateless DHCPv6 while some not.
>> [Dusan] Did the hosts run stateless DHCPv6, or stateful DHCPv6 without the
>> address option in ORO, or stateful DHCPv6 and ignored the address in
>> REPLY?
> [Bing] Let me quote the result in the draft:
> o  A=0, M=0, O=1
> 
>      *  Windows 8.1 acquired addresses and other information from
>         DHCPv6. (P.S. Window 8.1 always tries to acquire address and other information through stateful DHCPv6, regardless of whatever the flags are)

I got a different result from my experiment.

My Windows 8.1 host (updated today, running on VirtualBox on MacOS)
does not try to acquire address from DHCPv6 Solicitation but sends
DHCPv6 Information Request to aquire other information where RA flags
are A=0, M=0, O=1.  It behaves same as other operating systems.

I changed router's configuration to send RA with M=1 and the host
started to send DHCPv6 Solicitation, as I expected.

Then, I changed router's configuration back to M=0.  I expected that
Windows 8.1 host would send DHCPv6 Information Request but it continued
to send DHCPv6 Soliciation actually.

Then, I unplugged the Ethenret cable and plugged it back.  The host
started to send DHCPv6 Information Request again.


Thanks,
Tomoyuki