On Mon, 25 Jun 2001 [EMAIL PROTECTED] wrote:
> �Hola!
>
> > however, it's not so simple. in this way we have two indipendent protocol
> > families AF_INET and AF_INET6 (i would define them orthogonal), so
> > we should modify the behaviour of getaddrinfo.
>
> No change to getaddrinfo is needed.
then both the glibc and the USAGI implementation of getaddrinfo on linux
are broken.
> > in fact, when called with AI_PASSIVE flag set and AF_UNSPEC protocol
> > family, in a both ipv4- and ipv6-compliant system, getaddrinfo should
> > return two different results (::1 for ipv6 and 127.0.0.1 for ipv4).
> > moreover, calling getaddrinfo with AF_UNSPEC protocol family should
> > produce a result that's the sum of the results of two getaddrinfo
> > calls (one for AF_INET and one for AF_INET6).
>
> That's exactly how getaddrinfo works.
not on a rfc2553-compliant system like linux.
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi [EMAIL PROTECTED]
Ferrara Linux User Group http://www.ferrara.linux.it
Project6 - IPv6 for Linux http://project6.ferrara.linux.it
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
