Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain

["Dijk, Esko" <[e-mail]>]

> Yes, this is my belief as well.
> so I still do not think that we have a clear use case/description of what/how a less-than-subnet MPL domain would be
> defined/used.

A clear use case seems to be Peter's office topology where all nodes are connected as a single LoWPAN with one 6LBR. Each office/room can be configured as an MPL domain. The event information sent by a pushbutton or sensor (to trigger the lights) only needs to be disseminated to all the nodes in the local room; hence defining a separate MPL domain is useful.

Esko

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Michael Richardson
Sent: Saturday 17 November 2012 20:35
To: Dijk, Esko
Cc: [e-mail]; [e-mail]
Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain


>>>>> "Dijk" == Dijk, Esko <[e-mail]> writes:
    Dijk> a question from your last 2 emails is the following: if
    Dijk> multiple LoWPAN networks are assigned the same 802.15.4
    Dijk> channel (which is likely as Peter explained), would they not
    Dijk> be assigned a different Pan-ID to logically separate them? So
    Dijk> for the drawing that shows the 6 border routers case, there
    Dijk> would be no mutual connectivity between dissemination regions
    Dijk> anyway.

Yes, this is my belief as well.
so I still do not think that we have a clear use case/description of what/how a less-than-subnet MPL domain would be defined/used.

It seems to me that we understand how we would implement such a thing, at least.


--
Michael Richardson <[e-mail]>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.