Re: [Roll] multicast & MLD on LLN

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 15 October 2014 17:11 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC70B1A8AA1 for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 10:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 OgP-RuVuQ1rK for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 10:11:52 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F1B71A8A98 for <roll@ietf.org>; Wed, 15 Oct 2014 10:11:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29509; q=dns/txt; s=iport; t=1413393074; x=1414602674; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GxBBLMm5flOYevTm+lcoGJDa2XdAkb5HsJModaRVyK4=; b=G3s7WTz6lB12DfRPrH6H/YC3c+5v/Nlhcp1VnLaB6tXcE+Z6wwJVwDjO SfsKz6Sasax7GCsXHpE4ju5atYMJ6ZeQTmpEdhBhu4BZQGFWY/9A7nG5T M0IizKLfO7+cjk/j3nv89VM1CMgyKm8bplX5OoYfHrKyNdTMhs2ud0O2T 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAIGpPlStJV2P/2dsb2JhbABbgkhGU1gEy3UBCYdNAoEWFgF9hAIBAQEEAQEBKkELEAIBCBEDAQEBCxYBBgcnCxQJCAIEDgUIiDYNyF8BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIpPhScKHSANBAYBBoMngR4FkX+hb4N3bIEGQoECAQEB
X-IronPort-AV: E=Sophos; i="5.04,725,1406592000"; d="scan'208,217"; a="87239347"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-4.cisco.com with ESMTP; 15 Oct 2014 17:11:12 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9FHBCXm025954 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <roll@ietf.org>; Wed, 15 Oct 2014 17:11:12 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.132]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 12:11:12 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] multicast & MLD on LLN
Thread-Index: AQHP5RuvdYkdkHPd5kSqasUTvxD8SJwxaFmpgAADOoA=
Date: Wed, 15 Oct 2014 17:11:11 +0000
Deferred-Delivery: Wed, 15 Oct 2014 17:11:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842E1C822@xmb-rcd-x01.cisco.com>
References: <aef2e75903e84afe988ff58d04a0fc56@DB4PR01MB0431.eurprd01.prod.exchangelabs.com> <6B9D200B-58B8-423C-ADEA-A6C61F73748B@cisco.com> <AC402B16-8AD9-4033-A7F3-780725F9BAB8@tzi.org> <CABOxzu0-MLJ9esL55oxj_eQRpzXJrf6XErV+jd6UeZ2vuF0H5w@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD842E1C49A@xmb-rcd-x01.cisco.com> <CABOxzu2d_JNFQ+Nu9mw=pW2TPG7qxFm6ocLFvSXChvA_By3xVw@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD842E1C6B0@xmb-rcd-x01.cisco.com> <D063F2D8.2EA57%d.sturek@att.net>
In-Reply-To: <D063F2D8.2EA57%d.sturek@att.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.49.80.52]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD842E1C822xmbrcdx01ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/hEAk79Rg5BlKOAVhoIpzSFwyZ6Q
Cc: "Greg Shepherd (shep)" <shep@cisco.com>, "IJsbrand Wijnands (iwijnand)" <ice@cisco.com>
Subject: Re: [Roll] multicast & MLD on LLN
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Oct 2014 17:11:57 -0000

Thanks a bunch, Don!

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