> If this is not system-specific then it seems that the handling of
> IPv4-mapped multicast addresses was something left out of either the IPv6
> socket API or perhaps an IPv4-mapped multicast address should be
> explicitly defined? For example, 224.2.127.254 might be mapped to
> ff0e::ffff:224.2.127.254 instead of ::ffff:224.2.127.254? Linux would
> accept the first address but not the latter in a multicast socket call.
In our IPv4/IPv6 stack (for EPOC) I was tentatively planning to handle
any "::ffff:224.x.x.x" as "multicast" destination. Thus, the idea was
that one could join and leave IPv4 multicast groups using the IPv6 API
and plain IPv4 multicast addresses in IPv4-mapped format.
Can anyone see any problems with this?
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
