Re: [Roll] multicast & MLD on LLN

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 15 October 2014 16:39 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 3F74E1A892C for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 09:39:01 -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 Vck_yZM4Vqos for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 09:38:59 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EA5A1A895E for <roll@ietf.org>; Wed, 15 Oct 2014 09:38:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19362; q=dns/txt; s=iport; t=1413391129; x=1414600729; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oNcRTOILqSrwBx+h2yGlxuc51yOMhKu2+ftqx/ChcZ4=; b=fx847SfMOl9WfQqJbAuu05tK9ntrRFRccn0NV13LxjAF4o3KFEHrCun9 Lj40k7te5b8Jpl2CVoWy5EPvrWIOSoYZCkFwShN14E2i6pIQM7aqZ1H+i B44LUCYOhGN9MGOVZPewJQa4E4ZjwCnZm0k4K+08RUJtZXWZozHeGqEoQ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFANChPlStJA2H/2dsb2JhbABbgkhGU1gEgwLQSgIbeRYBfYQCAQEBBCMKTBACAQgRBAEBCx0DAgICMBQJCAIEDgUIiDazN5UmAQEBAQEBAQEBAQEBAQEBAQEBAQEBF492Ch0xBgGCdzaBHgWRf6Fvg3dsgQZCgQIBAQE
X-IronPort-AV: E=Sophos; i="5.04,725,1406592000"; d="scan'208,217"; a="87232153"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP; 15 Oct 2014 16:38:49 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9FGcm4V017231 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <roll@ietf.org>; Wed, 15 Oct 2014 16:38:48 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.132]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 11:38:48 -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: AQHP5RuvdYkdkHPd5kSqasUTvxD8SJwxXtilgAAApEA=
Date: Wed, 15 Oct 2014 16:38:47 +0000
Deferred-Delivery: Wed, 15 Oct 2014 16:38:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842E1C6B0@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>
In-Reply-To: <CABOxzu2d_JNFQ+Nu9mw=pW2TPG7qxFm6ocLFvSXChvA_By3xVw@mail.gmail.com>
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_E045AECD98228444A58C61C200AE1BD842E1C6B0xmbrcdx01ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/5TJRyPGtq7WQis5c_o9cjA5r6l0
Cc: "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 16:39:01 -0000

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