In your previous mail you wrote:
4. Suggested protocol change
o In IPv4 address architecture document [Hinden, 1998] explicitly state
that IPv4 mapped address is for use within basic API [Gilligan, 1999]
, and basic API only. Forbid any other uses.
=> I don't like at all SIIT so I have no concern with this proposal.
o Move any document that suggests the use of IPv4 mapped address on wire
to historic, due to security reasons.
=> you are a bit hard: these mechanisms should simply use other
injections of the IPv4 address space into the IPv6 address space
(there are many ways to inject a 2^32 space into a 2^128 one :-).
The above change will remove the threat due to the use of IPv4 mapped
address on wire.
=> I agree this should be simpler so safer.
Another way is to deprecate RFC2553 section 3.7, however, due to the
wide deployment of applications that use IPv6 basic API, the option is
not feasible.
=> I strongly object to this part of your proposal. IMHO IPv6 is NOT
a new protocol, it is only a new version of the IP protocol. So the
right target is to provide an "all version" API, as it is easy to inject
IPv4 into IPv6, the section 3.7 is the right idea!
Regards
[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]
--------------------------------------------------------------------
