Re: [v6ops] Please review the No IPv4 draft

[Ray Hunter <[e-mail]>]

Mikael Abrahamsson wrote:
> On Wed, 16 Apr 2014, Dale W. Carder wrote:
>
>> So, I am not in favor of adding more hints that may or may not 
>> observed that result in additional complexity and create an even more 
>> diverse set of behavior that has to be managed.  This is why I think 
>> the only real solution that would work in practice is ethertype 
>> filtering.
+1
>
> That still doesn't solve the problem of the enterprise network being 
> IPv6 only but publishes A and AAAA entries for internal resources on 
> the internal DNS zone, because other networks they have are dual stack.
>
> Otoh I think this would be better solved by implementing MIF 
> functionality in the device but... oh well.
>
Enterprise networks will use alternative protocols/methods to configure 
their end nodes IMHO e.g. Active Directory

And we have https://tools.ietf.org/html/rfc7078 for cases where some 
LANs are IPv4 only, some are dual stack, and others are IPv6 only 
(assuming anyone implements it)

I'm hoping that a node connected to an authenticated AD server will by 
default ignore any unauthenticated configuration hints purportedly sent 
via a DHCPv6 server.

Although as I've pointed out earlier, there could be serious race 
conditions here (RA/DHCPv6 IPv4 shutdown packet of death arrives before 
AD authentication).

-- 
Regards,
RayH