At 5:59 PM -0700 6/29/00, Dave Thaler wrote:
>Re "if scop 4 were configured to be used within a site"...
>So if we have a host with interfaces in two sites, and
>there's no manual configuration related to scop 4, and
>if an app tried to send to or join a multicast group
>in scop 4 are you saying that the send/join would fail?
I guess that is what I was saying (or, at least, an consequence of what
I was saying).
>I'd rather be liberal in what we accept here and have it
>succeed, which is what I was trying to allow.
I'm not sure how lax you want to be with zone-boundary configuration.
Seems to me that, in the IPv4 admin multicast scope case, we were quite
worried abou the hazards of "leaky" zone boundaries.
> > And you also need the capability to configure scop 4 zone ids on nodes
> > that are internal to a site, i.e., not site-boundary nodes.
>
>I didn't follow this. I was suggesting that you don't need
>separate scop 4 zone ids in this config, you use the same ids
>as for scop 5 (and you use a disjoint numbering space as Erik
>suggested to disambiguate this).
I meant for nodes that are scop 4 boundaries but not site boundaries.
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]
--------------------------------------------------------------------
