Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

If you turn off IPv4 on the host, that would mean a restart in most
cases. Tha means it would also not do anything on IPv4, no Discovery
etc. after some time the lease runs out and nothing more happens.

Is anything more needed? I am surely missing some detail here.

On 05/02/14 15:18, Ted Lemon wrote:
> On Feb 5, 2014, at 9:15 AM, Prashanth Patil (praspati) <praspati@cisco.com> wrote:
>> The desire was to better manage configuration sent
>> down to the host, if possible. Especially if I started dual stack, see my
>> IPv6 working great and decide to turn off IPv4.
> 
> It's unlikely that anybody would ever do that.   Most end users don't know the difference, and those that do are probably wise enough to realize that if the network configuration is working, changing it is as likely to cause problems as improvements.
> 
> More likely the network configuration would change as the result of a software update.   The software update would probably reconfigure the network anyway, so the problems would come out in the wash.   A software update that disables IPv4 by default when it is available on the network seems vanishingly unlikely.
> 
> More likely is that the network will stop providing IPv4, and the host will become IPv6-only by virtue of that change.
> 
> Are you seeing operational demand for this functionality?
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"