Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

[Philip Homburg <[e-mail]>]

>So really the effect we needed is not necessarily a "hard off" for the IPv4
>stack or even RFC 3927. 

One thing that could work is to turn the flag into a 'no IPv4 link local
in the absence of DHCPv4' flag.

As far as I know, networks that rely on IPv4 link local are quite rare and
in general you would not expect an untrused host to show up on such a network.
That should kill any unwanted service discovery.

Then the flag can be used as a heuristic to reduce the DHCPv4 DISCOVER rate.
That should be safe as long the host just reduces the rate to something
reasonable instead of completely stopping DHCPv4.

Anybody who is worried about the flag would then only have to run a DHCPv4
server, which is what the vast majority of the IPv4 networks already have.