Some applications MAY prefer one address over another, but most applications
will not care. IMHO the best solution is to allow the OS (and therefore
presumably the admin) to specify a default policy, but let applications
provide "hints" to the OS that other addresses may be better in certain
circumstances.
no, that's ridiculous. applications need a stable API that works the same from one platform to another, not one that changes at the whim of some network administrator. and we don't need an API that only works for "most applications".
I'm not convinced that such an API is immediately useful, however, since it
seems to assume a prior means of determining which addresses will work at
all. Most applications will be faced with a scenario where the source has N
addresses, the destination has M addresses, and it won't be clear which of
the N*M combinations will work without testing them all.
you're absolutely right about this part. about the only thing the API can reasonably do is let the application specify whether it can use a temporary "privacy" address (as in a web browser) or whether it needs a public address (as in a server or p2p app).
it is, and always has been, completely unreasonable to expect either hosts or apps to have to choose between a number of (source,destination) address pairs in order to successfully connect with other hosts. no API can solve that problem.
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
