Re: [v6ops] Please review the No IPv4 draft

[Gert Doering <[e-mail]>]

Hi,

On Mon, Apr 14, 2014 at 02:24:09PM -0400, Simon Perreault wrote:
> Le 2014-04-14 13:15, Nick Hilliard a écrit :
> > Stepping back a moment, the alternatives are:
> > 
> > 1. wiring both dhcpv6 and ra to include an ipv4 protocol option, and then
> > designing and implementing a completely new protocol to get both
> > client-side dhcpv6 and ra to be able to talk to to a dhcpv4 client in a
> > standardised way so that either of them can pass a shutdown signal to the
> > dhcpv4 client.
> 
> $ 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".

> - 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?

> > 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.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: [phone]           USt-IdNr.: DE813185279