In your previous mail you wrote:
I would prefer that we simply keep IPV6_MULTICAST_IF and use the sin6_-
scope_id for what it was originally intended, to identify the zone from
which a datagram was received and to identify the zone to which a datagram
should be sent. To the extent that that overlaps with what IPV6_MULTICAST_IF
does that is unfortunate but it certainly isn't the only or even the worst
example of duplicated functionality in the API specifications.
=> if the functionality is duplicated (and it is in this case) we have to
specify who has the precedence, ie. what happens when both are used.
[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]
--------------------------------------------------------------------
