At 1:45 PM -0700 6/26/00, Richard Draves wrote:
>I'm warming up to Dave's proposal, but I would not invent new zone ids for
>all the different multicast scope levels. (Or at least I'd leave this
>optional for implementations.) I'd map the multicast scope levels into the
>link-local/site-local/global unicast scopes.
I don't think you have to create zone IDs for all multicast scope levels
*nor* do I think you have to "map" those levels into the unicast levels.
Rather, you only need zone IDs for those scopes for which you are a
boundary (or in other words, only for those zones for which you are
attached to more than one of the same scope). Whenever dealing with an
address (multicast or unicast) of a scope for which you are not a boundary,
the appropriate zone is unambiguous (all your interfaces belong to a single
zone of that scope), so you can just use the "unspecified" (e.g., zero
valued) zone id in the sin6_scope_id that accompanies that address.
Steve
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
