Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local

[Ralph Droms <[e-mail]>]

On Sep 24, 2013, at 9:56 AM 9/24/13, Carsten Bormann <[e-mail]> wrote:

> On Sep 24, 2013, at 10:49, "Ralph Droms (rdroms)" <[e-mail]> wrote:
> 
>>>> When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined to
>>>> include all interfaces participating in the IEEE802.15.4 multi-link
>>>> subnet.
> 
> While this solves the special case of a 6LoWPAN (it might actually want to use the term 6LoWPAN for that), I always understood the RPL approach to go beyond networks delimited by the use of a specific link layer technology.
> 
> Wouldn't it be natural to have a MPL scope be congruent with the network covered by a RPL scope?
> (Now, there may be several of those around in a network, but I'd at least try to start from there.)
> 
> Again, this is a natural thing to do in a 6LoWPAN, we just seem to lack the term for a scope that happens to include other than 802.15.4 radios.

This point is where my suggestion for "scop 4" enters the picture.  I suggest "scop 3" for the L2-defined topology and "scop 4" for the administratively defined, RPL-congruent topology.

- Ralph

> 
> Grüße, Carsten
> 
> _______________________________________________
> Roll mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/roll