Yesterday's Windows update causes IPv4 to be default

[Lorenzo Colitti]

On Wed, Nov 21, 2012 at 10:28 AM, Doug Barton <dougb at dougbarton.us> wrote:

> I tend to agree with the spirit of this implementation (and for the
> record, I would have done HE differently in any case), but my immediate
> concern is for the "cached known-good IPv6" state when there is an
> intermittent problem on the link.
>

Look at it this way: in IPv4, if you have intermittent problems on a
link... well, it intermittently doesn't work. For thirty years, the answer
to that problem has been, "don't give a host an address (or router, or DNS
server, etc.) that doesn't work".

You could argue this is the way it should be. I suspect that app developers
don't want to be in a world where every address may or may not work and
they have to constantly probe destinations using all the host's addresses
every time they connect. They would probably perceive that to be a waste of
development effort and CPU time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20121121/d39a7308/attachment.htm>