Re: [Roll] multicast & MLD on LLN

"Turner, Randy" <Randy.Turner@landisgyr.com> Wed, 15 October 2014 20:27 UTC

Return-Path: <Randy.Turner@landisgyr.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 AD49B1ACC82 for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 13:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 uSEPH2-60XrV for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 13:27:38 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0792.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::792]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D831A1A7001 for <roll@ietf.org>; Wed, 15 Oct 2014 13:27:37 -0700 (PDT)
Received: from DB4PR01MB0431.eurprd01.prod.exchangelabs.com (10.242.221.22) by DB4PR01MB0431.eurprd01.prod.exchangelabs.com (10.242.221.22) with Microsoft SMTP Server (TLS) id 15.0.1049.19; Wed, 15 Oct 2014 20:27:15 +0000
Received: from DB4PR01MB0431.eurprd01.prod.exchangelabs.com ([10.242.221.22]) by DB4PR01MB0431.eurprd01.prod.exchangelabs.com ([10.242.221.22]) with mapi id 15.00.1049.012; Wed, 15 Oct 2014 20:27:14 +0000
From: "Turner, Randy" <Randy.Turner@landisgyr.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] multicast & MLD on LLN
Thread-Index: Ac/kvGg9glP5Rg5dTyCqZKTLnjPO8AAX0deAAACcwoAA3HB9gAAAUc4AAADViYAAAH71gAAArNuAAAaploD//8ISAA==
Date: Wed, 15 Oct 2014 20:27:14 +0000
Message-ID: <D0644F3D.303D%randy.turner@landisgyr.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> <73405C1D-6BD2-4030-8AE9-11B0EDBCE308@tzi.org>
In-Reply-To: <73405C1D-6BD2-4030-8AE9-11B0EDBCE308@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2.228.114.172]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR01MB0431;
x-exchange-antispam-report-test: UriScan:;
x-forefront-prvs: 0365C0E14B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(479174003)(377454003)(189002)(199003)(24454002)(129404003)(51704005)(31966008)(36756003)(83506001)(15975445006)(19580395003)(19580405001)(80022003)(21056001)(107886001)(93886004)(2656002)(64706001)(66066001)(20776003)(97736003)(87936001)(85306004)(110136001)(40100003)(107046002)(76176999)(106356001)(54356999)(50986999)(92566001)(122556002)(92726001)(85852003)(86362001)(101416001)(105586002)(4396001)(99396003)(120916001)(95666004)(46102003)(76482002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR01MB0431; H:DB4PR01MB0431.eurprd01.prod.exchangelabs.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <CEA7AF8009ED254AB0781D1692018A91@eurprd01.prod.exchangelabs.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: landisgyr.com
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/RJ768S9xPa6fGlkalTKDz3tNwvI
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 20:27:43 -0000

Hi Pascal,

This multicast use-case is similar to the street light group use-case,
except aimed at the AMI grid network:

There is of course a need to multicast firmware updates to devices in the
smart grid. In that example (and in other AMR use-cases) all devices in
the network subscribe to a common multicast address ‹ it¹s really a
broadcast, if all devices need to be updated at the same time, with the
same firmware.

Then there is a multicast group scenario where, say, only 500 of 5000
nodes need to be updated (possibly associated with a geographic region of
the grid)

THere¹s also a region-oriented multicast group address that could be used
to send control/management information to a particular set of smart meters
in the field. For instance if there is problem with a substation
controlling a particular geographic region of homes, the grid head-end
systems may elect to send a particular command to this region of home
meters to adjust their operation in light of upstream grid issues.

There may be some mapping of multicast address to geographic region so
that meters can use their GPS location to automatically derive what
multicast address to subscribe to.


Hope this helps
Randy


On 10/15/14, 4:08 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>Hi Don,
>
>this sounds exactly like a use case our multicasting approach can solve.
>
>Two questions:
>
>1) Are you using storing or non-storing mode for RPL?
>
>2) For the kinds of groups below, was is the likely distribution of group
>sizes?
>
>Grüße, Carsten
>
>On 15 Oct 2014, at 18:58, Don Sturek <d.sturek@att.net> wrote:
>
>> 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)
>
>_______________________________________________
>Roll mailing list
>Roll@ietf.org
>https://www.ietf.org/mailman/listinfo/roll


P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.