If you want to port in an IPv4 and IPv6 independent manner you will use
the tools as currently specified. There is not protocol that will matter
besides IPv4 and IPv6 for at least the next 10 years. The debate is not
technical but where the future will be. This makes it hard. API folks
have debated this the answer is as is specified now.
/jim
"Shout it out G.L.O.R.I.A." (Them [Van Morrison])
On Sat, 23 Jun 2001, Jun-ichiro itojun Hagino wrote:
> >> for example: on linux system, if you would like to turn IPV6_V6ONLY
> >> option on, you can only accept IPv6 traffic with getaddrinfo(3) loop.
> >If that changes were done, turning IPV6_V6ONLY on would not be frequently d=
> >one.
>
> if you want to see IPv4 traffic on AF_INET socket (so that we don't
> get confused by bogus source address, and generating bogus traffic
> when responding) you will want to do IPV6_V6ONLY.
>
> itojun
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
