Minor comment on comments.. > From: Pekka Savola <[EMAIL PROTECTED]>
> 4) I'm not sure whether I see the immediate need for the unique subnet > multicast scope assignment, as below: > > Furthermore, to avoid the need to perform manual configuration in > most cases, an implementation should, by default, initially assign > zone indices as follows, and only as follows: > [...] > o A unique subnet (multicast "scop" value 3) index for each > interface > > ==> this seems mostly like a flawed concept anyway, because you don't really > don't have a multicast "subnet" to begin with, because you don't assign > multicast addresses on interfaces anyway. So, I'd consider removing this > automatic default and requiring the subnet scope be configured manually. I need this default, because I have zone ids are implemented as an array of 16 id's on the interface, and each much have sensible default, without requiring manual configuration (yes, the delivered code has full support of site locals, or any other scope you might want). This may be left as implementation issue, but any text with "MUST" and manual configuration won't do. Besides, I'm experimenting with a kind of "multilink subnets", and I'm using this scope to indicate group of interfaces that need to be "bridged". Thus, the subnet index must by default be different, or bridging starts to happen... (if I manage to get it to work :-) -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
