Re: [Roll] multicast & MLD on LLN

"Turner, Randy" <Randy.Turner@landisgyr.com> Wed, 15 October 2014 21:49 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 8A55B1ACDD8 for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 14:49:06 -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 8xoOXq7LLGcf for <roll@ietfa.amsl.com>; Wed, 15 Oct 2014 14:49:04 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0709.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::709]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1311ACDC3 for <roll@ietf.org>; Wed, 15 Oct 2014 14:49:04 -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 21:48:41 +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 21:48:41 +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//8ISAIAARkAAgAAKrYD//8XSgA==
Date: Wed, 15 Oct 2014 21:48:40 +0000
Message-ID: <D0646392.3058%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> <CABOxzu2kgCjqUk2qv0y7Yw4E7_wP0L_qTTTpvoTeH+Enxic=EA@mail.gmail.com> <FD45410F-4485-46E5-9C7B-E7675E30128F@tzi.org>
In-Reply-To: <FD45410F-4485-46E5-9C7B-E7675E30128F@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)(199003)(24454002)(51704005)(377454003)(479174003)(189002)(120916001)(95666004)(4396001)(99396003)(76482002)(46102003)(20776003)(93886004)(64706001)(66066001)(2656002)(85306004)(87936001)(97736003)(83506001)(15975445006)(19580405001)(19580395003)(31966008)(36756003)(21056001)(80022003)(107886001)(122556002)(92726001)(85852003)(105586002)(86362001)(101416001)(106356001)(76176999)(40100003)(110136001)(107046002)(92566001)(50986999)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR01MB0431; H:DB4PR01MB0431.eurprd01.prod.exchangelabs.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F95B8BC764113F4FA44038DA7324DCC0@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/zEFkIUq5mswLgPZGMMLUiHINTGk
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 21:49:06 -0000

I¹m not saying confidentiality isn¹t an issue with updates, but I think
it¹s more important that the integrity of the image be correct, and that
the image is appropriate for the target ‹- both of these concerns can be
handled at the application layer ‹ multicast is just the transport.

Randy

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

>On 15 Oct 2014, at 22:38, Kerry Lynn <kerlyn@ieee.org> wrote:
>
>> Surely you'd want to do OTA updates in a secure fashion?  Does this
>>highlight
>> a need for secure multicast?
>
>What is the security objective here?
>If it is integrity/authenticity, this is best done with object security
>on the OTA image, which also can provide confidentiality for the bits in
>the OTA image.
>(I don¹t think there is a need [or even a way] to keep the fact that an
>OTA update is occurring confidential.)
>
>Grüße, Carsten
>
>_______________________________________________
>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.