> So, I'll conclude by a few questions to give food for thought:
>
> - does this seem like a problem, that is, should getaddrinfo() +
> AI_ADDRCONFIG perform AAAA DNS queries etc. if
> the node only has v6 link-local/loopback addresses?
>
> - is getaddrinfo() + link-local addresses something we should support?
>
> - should this be fixed by e.g.:
> a) recommending that the implementations filter out link-locals as well
> when doing AI_ADDRCONFIG (a BCP/Info document)
> b) specifying additional semantics for AI_ADDRCONFIG
> c) specifying a new hint which would perform this
d) obsolete AI_ADDRCONFIG. AI_ADDRCONFIG semantics is too vague, and
way too difficult to specify (for instance, if you have IPv6 global
unicast address and no route, is it configured?). also, even without
AI_ADDRCONFIG programs work just fine (socket(2) or connect(2) will
issue the right error).
itojun
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
