In your previous mail you wrote:
>>>>> On Thu, 29 Jun 2000 10:17:46 +0200,
>>>>> Francis Dupont <[EMAIL PROTECTED]> said:
> We could implement Steve's proposal if we invented unique space of
> identifiers that covers all scopes. And I admit it would be useful if
> we can specify the outgoing interface by the sin6_scope_id field
> without any other APIs (such as socket options), but it would be too
> complecated for application programmers, especially on properly using
> different type of sin6_scope_id values (i.e. sometimes use it as an
> interface identifier, and sometimes use it as a zone identifier of a
> larger scope).
> => do you believe we should use conditional? In fact the sin6_scope_id
> space is not yet specified then in theory it is not too late.
I can't understand what you meant by "conditional" (sorry),
=> could in place of can, invented in place of invent, ...
For me this usage of past show you wouldn't like to support to
Steve's proposal...
but it is
correct that the semantics of sin6_scope_id is not yet defined. My
concern is possible confusion due to the complexity of the semantics
in the future.
=> I understand your concern but powerful things are usually complex.
I'd like to get both a powerful and uniform thing, ie. something which
can be made simple to explain. Another question is do we need a very
powerful thing or should we stay with the current solution (sin6_scope_ids
are used only for link-locals).
By the way, do you intend to use the same approach for unicast
addresses?
=> I don't see any good reason to have different approaches for unicast
and multicast addresses. In IPv4 they are very different for historical
reasons and it is very hard for a beginner to program a multicast
application for this reason (the lack of documentation doesn't help too).
IMHO we should try to complete Steve's proposal and see if it works
reasonnably (look at the scope I-D thread about potential issues).
Thanks
[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]
--------------------------------------------------------------------
