Mauro,
>> but v4 mapped does not affect the ISV porting effort at all and in fact
>> makes their job much easier if the platform they are porting to supports
>> that paradigm.
>you are absolutely right. my concern was about api issues. a modification
>in the behaviour of af_inet6 passive socket, so that they are not allowed
>to accept connections from af_inet sockets, would have imho nightmarish
>effects.
An af_inet6 socket should not accept a connection for an af_inet socket.
Any implementation specific code path in a hybrid stack (different from
a dual stack I think you know??) that does this or neglects the issue
will have problems as you state. If an implementation does this it is
broken, the market will fix the correction. Also we have never had this
problem at any test event. Also early on I have run ftp, telnet, etc at
the same time and have not seen any bugs. In fact what you ask is a
test at present.
No where in any spec do we (the IETF or the XNET TBD API we are buildin
the base for here on ipng group) require how one uses mapped,
compatible, or native IPv6 addresses. Nor should we other than to
define them and make them available to applications via the API.
>there has been a misunderstanding. i wanted to say that forbidding the use
>of ipv4 mapped address "on the wire" would surely eliminate all security
>problems. as someone has pointed out, this is not acceptable - and i am
>also of this opinion. but itojun is certainly right when he says that rfcs
>and drafts should be precise, clear and not contradictory when dealing
>with important matters that can become a security issue.
If we could ever achieve perfection with any spec anywhere in the IETF
we would never ship a spec. We go with what we can get done within in a
reasonable amount of time and test the implementations. The market has
already started to port to IPv6 and ISPs are putting it in their RFPs as
other suppliers.
I see no change to rfc2553bis API for this dicussion.
regards,
/jim
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
