Re: [Roll] multicast & MLD on LLN

Kerry Lynn <kerlyn@ieee.org> Wed, 15 October 2014 20:38 UTC

Return-Path: <kerlyn2001@gmail.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 253D61ACCEE for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 13:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 Yy26X3u8nbDc for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 13:38:41 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30ADC1ACD0F for <roll@ietf.org>; Wed, 15 Oct 2014 13:38:41 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id uy5so1749605obc.13 for <roll@ietf.org>; Wed, 15 Oct 2014 13:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=jioFb873K3mryi2ughIRA6eR03J5SHZ8PUkawI8hdwQ=; b=A74FDYbeqftltc9WBfi8e2xSGeW0OlIK1dB4+o+cAg+ZBwZLYYG38fs2P56dMomt4h 2MGQYK5FcXV66I3vxGZYb4XHIxwWqiMQknVauHdQ1Qepu+J3pydhdyAjmQGcH7qU92Yh cbEyi1tTM+cGMIHt/CygMYsYrofEbwqnqs9JQC9olWZrdwMvRPaAc/Ij21yge0nSS2gS yn/2qVb0coA4jU4lTOlmiN3XaN1t3xgH5Ub0OmmaT4BoM+RnFAMcpEWCLulvsa8Y+M9T z0V5e3Q1IpDRHfmmkNZIBGgnC+3Fgcu8TIhxgETX/59Z4CAKfTcMpPv1+8Y7aGh5cZB4 BT5g==
MIME-Version: 1.0
X-Received: by 10.202.179.10 with SMTP id c10mr2852795oif.102.1413405520533; Wed, 15 Oct 2014 13:38:40 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.15.129 with HTTP; Wed, 15 Oct 2014 13:38:40 -0700 (PDT)
In-Reply-To: <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> <D0644F3D.303D%randy.turner@landisgyr.com>
Date: Wed, 15 Oct 2014 16:38:40 -0400
X-Google-Sender-Auth: QqHnjbc-1rpbaDjAmr3DnIYDG0M
Message-ID: <CABOxzu2kgCjqUk2qv0y7Yw4E7_wP0L_qTTTpvoTeH+Enxic=EA@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ce148f9a77f05057c1d36
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/hVQnN9UM-e-dS8iW1ot-A22PC68
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:38:43 -0000

On Wed, Oct 15, 2014 at 4:27 PM, Turner, Randy <Randy.Turner@landisgyr.com>
wrote:

> 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.
>
> Surely you'd want to do OTA updates in a secure fashion?  Does this
highlight
a need for secure multicast?


> 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.
>
> Is the GPS position manually configured in the meter?  If so, perhaps
manual
configuration of multicast group address is just marginally more expensive.

It could also be the case that multicast group addresses are named objects.
For example, one could assign DNS names to groups and resolve this to a
AAAA record (just as with unicast addresses) or use DNS-SD to find a
multicast service binding.

-K-

>
> 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.
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>