> >>    I'm not sure what is meant in above (shin, if possible email me
> >>    in Japanese privately).
> >Woops sorry, just replace AI_CANNONNAME with AI_ADDRCONFIG.
> 
>       Now I see what you meant.  Thanks.  Then maybe getipnodebyname()
>       misbehaving?

Yes it won't be spec conformant. But,,,

>       NOTE: all existing getaddrinfo code (BIND8 = NRL, BIND9, KAME) has 
>       the same problem.  To address this right I think there needs to be a
>       big rewrite in src/lib/libc/net (can we meet 4.0 deadline with it?
>       I'm not sure).

Big rewrite in this period will be impossible, and I think
just using AI_ADDRCONFIG inside getaddrinfo() will be
realistic choice. (And also need to fix maybe another problem
which is happening now.)

The effect is (in commit permission format :-) ),

  upside:     IPv4 apps on IPv4 only kernel don't need to wait AAAA resolving
  downside:   getaddrinfo() on IPv4 only kernel don't do AAAA resolving.
              And it won't be spec conformant.

              (But I think if AI_ADDRCONFIG become available
              for geetaddrinfo(), then most of apps will just
              specify AI_ADDRCONFIG for getaddrinfo(), so the
              behaviour of each apps will be same.)


Yoshinobu Inoue


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to