Re: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>

Samita Chakrabarti <samita.chakrabarti@ericsson.com> Thu, 30 October 2014 01:31 UTC

Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A033E1ACF07 for <6lo@ietfa.amsl.com>; Wed, 29 Oct 2014 18:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KD5fJepD8wp for <6lo@ietfa.amsl.com>; Wed, 29 Oct 2014 18:30:56 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 436541ACEF4 for <6lo@ietf.org>; Wed, 29 Oct 2014 18:30:56 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-74-54513a57261d
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 60.17.25146.75A31545; Wed, 29 Oct 2014 20:04:55 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Wed, 29 Oct 2014 21:30:46 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Don Sturek <d.sturek@att.net>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>
Thread-Index: AQHP6Yqs9rUQKCMFekOdk3hb9Mnb45w0FdyAgAnp9KCAAOztsIAJAjng
Date: Thu, 30 Oct 2014 01:30:45 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C26E266@eusaamb103.ericsson.se>
References: <D0657818.2EB6C%d.sturek@att.net> <E045AECD98228444A58C61C200AE1BD8489FD608@xmb-rcd-x01.cisco.com> <ECA43DA70480A3498E43C3471FB2E1F01C257EFE@eusaamb103.ericsson.se> <E045AECD98228444A58C61C200AE1BD848A1C7CC@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD848A1C7CC@xmb-rcd-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_ECA43DA70480A3498E43C3471FB2E1F01C26E266eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyuXSPt264VWCIwbSbGhbNUwQsLjVcZ7aY MeUdowOzx7Fl+5k9pvzeyOqxZMlPpgDmKC6blNSczLLUIn27BK6MtmeNTAV3vzJVbJi1mrWB 8e05pi5GTg4JAROJOVPmMULYYhIX7q1n62Lk4hASOMIocf9RDyuEs5xR4vb9rcwgVWwCVhId vXvYQWwRgRKJA88vg9nCAqkSRzYeZoaIp0m8mviRCcJ2k3i4cSkbiM0ioCqx4t4dsHpeAV+J W78WMUMs+M4o8XPmQrAGTqDEmaZ2sJMYgU76fmoNWJxZQFzi1pP5UGcLSCzZc54ZwhaVePn4 HyuErSTx8fd8doj6fImOi9sZIZYJSpyc+YRlAqPILCSjZiEpm4WkDCKuI7Fg9yc2CFtbYtnC 18ww9pkDj5mQxRcwsq9i5CgtTi3LTTcy3MQIjKtjEmyOOxgXfLI8xCjAwajEw/tBPiBEiDWx rLgy9xCjNAeLkjivZvW8YCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MLVZr8646/hTTuXb2 OsdffpZd9Rqnp5xR3Nfw5e7ZmEV9/TuYHP48u3t67fKdU/d68e5yOWZuobk4KMNSkedk54Zz t1L+6/ydzDBnu3NWENf+F+lhunXZVbdYv/cV2j6aI7MrRfJLzrsz3/g4uqYz3f1l1rH87I9P J6Z52LlnfHNv/Limt1yzUYmlOCPRUIu5qDgRAFQO2IqMAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/6lo/jpeFcvlT5NPBpw7Ya3cQ4zc57WM
Subject: Re: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 01:31:02 -0000

I see your point. Sorry, I did not get this point the first time.

Thanks,
-Samita

From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
Sent: Friday, October 24, 2014 1:00 AM
To: Samita Chakrabarti; Don Sturek; 6lo@ietf.org
Subject: RE: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>



>known windows of time. Also it is important to figure if the transaction is always triggered by the device, meaning that > it is acceptable that no route to the device exist in the network when the device is asleep.
[SC>] If we delete the route in the network as the device goes to sleep, it might create a lot of busy work at the routers  and signaling in the network if it has to keep track of a large number of nodes' sleep and wakeup. Is not it possible that the devices shut off listening while sleeping to save battery?

[PT] Sorry Samita you lost me. Yes, devices shut their radio off when sleeping. And the trouble is the amount of state in intermediate nodes and eventually the root. If a device only wakes up at a determined time every day, the associated state could exist only in the network at the relevant time. We can devise ways to optimize the state installation above and beyond current RPL.

Cheers,

Pascal
From: Don Sturek [mailto:d.sturek@att.net]
Sent: jeudi 16 octobre 2014 22:28
To: Pascal Thubert (pthubert); 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: Re: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>

Hi Pascal,

Absolutely, I will have a look.

What we would like to see if the ability for a leaf node to sleep for very long periods of time (maybe only awake monthly) to provide 10+ years or so battery life.

I will see if the draft would support something like that.

Don


From: "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Date: Thursday, October 16, 2014 10:11 AM
To: "6lo@ietf.org<mailto:6lo@ietf.org>" <6lo@ietf.org<mailto:6lo@ietf.org>>
Subject: [6lo] 6LoWPAN ND host attaching to RPL router <was: RE: [Roll] multicast & MLD on LLN>

Hello Don:

<note, I moved to 6lo>

> What would be really nice is if we could have non-RPL aware end devices also in the network but I think that is another topic :-)
Yes, it is. The 6TiSCH architecture requires that we make that work and we produced http://tools.ietf.org/html/draft-thubert-6lo-rfc6775-update-reqs to promote that work. Would you be willing to help there to make sure all your requirements are covered?

Cheers,

Pascal

From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Don Sturek
Sent: mercredi 15 octobre 2014 18:58
To: Routing Over Low power and Lossy networks
Cc: IJsbrand Wijnands (iwijnand)
Subject: Re: [Roll] multicast & MLD on LLN

Hi Pascal,

Let me try to provide a use case.

The network is a Neighborhood Area Network.  The application can be something like street lights or a smart metering AMI (really any collection of devices that are networked centrally with a non-trivial number of devices in the network)

Here are some details:
1)   Around 5000 devices in the network total.  There can be as many as 15 hops from the DODAG to the furthest leaf node in the network.
2)  One border router that supports ROLL RPL.  All devices in the network are ROLL RPL aware (some as routers, some end devices).  What would be really nice is if we could have non-RPL aware end devices also in the network but I think that is another topic :-)
3)  We support all of the mandatory multicast groups (eg all routers) in our networked devices
4)  From an application point of view, we want to use special application-defined multicast groups for things like:
       A.    Control a geographic collection of street lights (like all the ones in an area where there is to be a festival this evening)
       B.    Control a geographically  diverse collection of devices that are not the entire population (for example, I want a message sent to all of my pre-pay customers which are mainly focused in some neighborhoods, less in others)
5)  I don't want to incur the MPL overhead of all multicast traffic flooding all 5000 devices/forwarded up to 15 hops in my network when I send these special multicast group messages.

What would be great in the above scenario is if the multicast traffic only traversed the portions of the network where members of the multicast group exist (eg, don't forward down portions of the tree where there are no multicast members).  MPL as a flooding mechanism fails this goal (which is fine with relatively few devices but not so when talking about 5000 devices/24 hops!

Is the above good enough to start a discussion on how to solve the problem?

Don


From: "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Date: Wednesday, October 15, 2014 9:38 AM
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Cc: "IJsbrand Wijnands (iwijnand)" <ice@cisco.com<mailto:ice@cisco.com>>
Subject: Re: [Roll] multicast & MLD on LLN

Hello Kerry:

Or Roll Multicast Operations ( : ROLLMOps? : )

Basically, BIER needs a preexisting tree structure and RPL is designed to build and maintain one. They need a root node and we have one.
On paper it is a perfect match. Now the question is whether there is enough need for that work, and then we'll find a place to make it happen.

To start with, would you have a specific use case of multicast in LLNs where MPL is less applicable than the classical tree-based forwarding?

With that, we could connect into the BIER effort.

Strong points:
- very limited state in the nodes, could even be used for unicast, independent on the number of groups and the size of the network
- bit aggregation easy to advertise in existing DAOs, low cost there too
- transparent support for v4 and v6 (since it is an overlay)

Weak points:
- extra encapsulation (since it is an overlay)
- new routing and forwarding operation to implement in the nodes (bitwise)
- limited number of nodes per DODAG (roughly 100).

Cheers,

Pascal

From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Kerry Lynn
Sent: mercredi 15 octobre 2014 18:25
To: Routing Over Low power and Lossy networks
Cc: IJsbrand Wijnands (iwijnand)
Subject: Re: [Roll] multicast & MLD on LLN

On Wed, Oct 15, 2014 at 12:00 PM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Or form a new group :)

What about Routing Over Complete Kaos?

More seriously, it's probably a good idea to goto through the BoF sequence again to analyze what's left to be done.
I can certainly see an analog of what the 6lo is to 6LoWPAN, but for ROLL.

For me the first question is whether multicast in the LLN would be RPL-
dependent, or have RPL-like features (e.g. dependence on a DODAG).
That could argue for doing the work in ROLL or a follow on group
(ROLLMAN?)

At least some of the 6lo proposals (MS/TP comes to mind) are not mesh
networks, but still constrained from a host and bandwidth perspective.

I like the topology-independence of MPL, but I think work still needs to be
done to see how far it is from optimal (in terms of energy and bandwidth
usage) under different operating conditions and parameter settings.

-K-

Cheers,

Pascal

_______________________________________________ Roll mailing list Roll@ietf.org<mailto:Roll@ietf.org> https://www.ietf.org/mailman/listinfo/roll
_______________________________________________ 6lo mailing list 6lo@ietf.org<mailto:6lo@ietf.org> https://www.ietf.org/mailman/listinfo/6lo