Re: [v6ops] Please review the No IPv4 draft

[Simon Perreault <[e-mail]>]

Le 2014-04-14 15:48, Gert Doering a écrit :
>> $ grep "option no-ipv4" /var/db/dhclient6.leases.eth0 && pkill dhclient
>>
>> - Is that too hard to implement?
> 
> Yes.  My DHCP client is called "dhcpcd".  Nick's might be "pump".

I'm sorry, I don't see your point.

>> - Why does that need to be standardized? It would be part of an OS'es
>> scripts and that usually doesn't get standardized.
> 
> Who do you expect to maintain that on the DHCPv6 client side, for all
> possible combinations with DHCPv4 clients?

Why would anyone want to maintain that for all combinations of
implementations?

Take NetworkManager for example. It uses ISC DHCPv4+v6. So it implements
the above. That's all it needs to do. Other network daemons or sets of
init scripts would do similarly however they want. It's something that
gets implemented a level above the DHCP client, in the "glue" code.

>>> Only a host which runs a dhcpv4 client is ever going to act on this option.
>>>  From a strict point of view, it has nothing to do with ipv6.
>>
>> Only a network that does provide IPv6 would ever want to set that
>> option. It has *everything* to do with IPv6.
> 
> To the contrary.  A network that does not provide IPv4 would want to set
> that option.  You might just not have public IPv4 here, because it's
> a zeroconfo network with only IPv4 link-local (169.254) addresses.

I'm not following your reasoning, sorry.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca