Re: [v6ops] Please review the No IPv4 draft

[Karsten Thomann <[e-mail]>]

I have still problems to understand why a message on one link/interface should be able to 
shutdown the whole IPv4 stack or the dhcpv4 client, the scope of the message should be limited 
to the link/interface on which the message was received and not further... 

In my opinion the system should remove the v4 address, and the dhcpv4 client should stop 
sending discover messages on that specific interface, and the easiest way to tell dhcpv4 to do 
that is a dhcpv4 message.

Karsten

Am Dienstag, 15. April 2014, 09:38:58 schrieb Simon Perreault:
> Le 2014-04-15 04:36, Gert Doering a écrit :
> > I agree to this.  Interestingly, this is something else than "just
> > shutdown
> > the dhcpv4 client if this option is detected" - it is "shutdown IPv4",
> > which many OSes can't do today at all (and yes, that needs fixing).
> 
> Correct, it means "shutdown IPv4". Our draft lists precisely what needs
> to be shut down. And you're correct in that implementing this could mean
> more than just "pkill dhclient" on some OSes. But that work needs to
> happen anyway.
> 
> Simon