Re: v6ops-v6onbydefault: link-locals and AI_ADDRCONFIG

[Pekka Savola <pekkas@netcore.fi>]

On Wed, 29 Oct 2003 itojun@iijlab.net wrote:
[...]
> >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)

Yep, or the apps writing guidelines could recommend to turn it on.  The 
basic API spec already defines "AI_DEFAULT" even though it doesn't (AFAIR) 
specify that it should be the default :-)
 
> 	and we (*BSD groups) ship programs without AI_ADDRCONFIG, and they
> 	work just fine...

Yep, to the extent they're used.  Stig already mentioned that some apps
are moving to some custom address lookup hacks from getaddrinfo() due to
these problems.  The use of AI_ADDRCONFIG should help in the majority of
cases, i.e., deploying v6-capable apps on nodes which don't have v6
connectivity yet.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings