>> > - there are really misbehaving DNS servers out there, which jeopardize
>> >your IPv4 service if you query for AAAA's, and
>>
>> this is a separate problem (this is not what AI_ADDRCONFIG cares
>> about).
>
>Yes, this is a separate problem .. but one that AI_ADDRCONFIG works around
>for the vast majority of nodes which could be dual-stack, but without IPv6
>connectivity. So, in that sense, IMHO AI_ADDRCONFIG helps the situation
>*a lot*, but of course we still have to fix the problem for those
>dual-stack nodes that do, in fact, have IPv6 connectivity.
>
>Remember, the most important thing we should care about is that dual-stack
>deployments can get more common without causing problems for *IPv4* or
>services in general. AI_ADDRCONFIG is one step in that direction.
for your story to be effective it has to be host-wide configuration
knob, not a parameter to library function. (we cannot change every
program we use to have AI_ADDRCONFIG)
and we (*BSD groups) ship programs without AI_ADDRCONFIG, and they
work just fine...
itojun
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
