AF_INET6 will always permit the catch only model because its been a method
for over 6 years and customers have ported to that model. We are not
getting rid of it now. That is not going to happen. The market has
spoken and the early adopter deployment customers will not have their code
broken.
As far as the default it is you will get v4mapped on AF_INET6 unless you
set v6only sockopt.
It is done it is written.
/jim
"Shout it out G.L.O.R.I.A." (Them [Van Morrison])
On Mon, 25 Jun 2001, Mauro Tortonesi wrote:
> On Sun, 24 Jun 2001, Francis Dupont wrote:
>
> > PS: (again) IPv6 is not a new protocol, IPv6 is the new version of IP.
> > If you believe in this (stronger than IPv6 itself) then you can really
> > understand the dual stack model (the integrated dual version model).
>
> right. but this is not the real problem. the real problem is if
> AF_INET6 family should be a catch-all extension of AF_INET or if
> they should be an unrelated, being AF_INET6 a totally different type of
> socket from AF_INET.
>
> i vote for the second option.
>
> --
> 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]
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
