Re: [Roll] [roll] #128: Trickle multicast could be considered in other applications?

"Dijk, Esko" <esko.dijk@philips.com> Mon, 26 August 2013 14:57 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35B911E81B4 for <roll@ietfa.amsl.com>; Mon, 26 Aug 2013 07:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FuFtwuZEzJbD for <roll@ietfa.amsl.com>; Mon, 26 Aug 2013 07:57:40 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0252.outbound.messaging.microsoft.com [213.199.154.252]) by ietfa.amsl.com (Postfix) with ESMTP id CB48221F9FE7 for <roll@ietf.org>; Mon, 26 Aug 2013 07:57:31 -0700 (PDT)
Received: from mail41-db9-R.bigfish.com (10.174.16.235) by DB9EHSOBE003.bigfish.com (10.174.14.66) with Microsoft SMTP Server id 14.1.225.22; Mon, 26 Aug 2013 14:57:30 +0000
Received: from mail41-db9 (localhost [127.0.0.1]) by mail41-db9-R.bigfish.com (Postfix) with ESMTP id 79B27C001C3; Mon, 26 Aug 2013 14:57:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -7
X-BigFish: VPS-7(zz15d6O146fI9251I217bIdd85kzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzzz2dh2a8h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h1155h)
Received: from mail41-db9 (localhost.localdomain [127.0.0.1]) by mail41-db9 (MessageSwitch) id 137752904784520_30985; Mon, 26 Aug 2013 14:57:27 +0000 (UTC)
Received: from DB9EHSMHS010.bigfish.com (unknown [10.174.16.247]) by mail41-db9.bigfish.com (Postfix) with ESMTP id 075CFC40046; Mon, 26 Aug 2013 14:57:27 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by DB9EHSMHS010.bigfish.com (10.174.14.20) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 26 Aug 2013 14:57:23 +0000
Received: from 011-DB3MPN2-083.MGDPHG.emi.philips.com ([169.254.3.104]) by 011-DB3MMR1-006.MGDPHG.emi.philips.com ([10.128.28.56]) with mapi id 14.03.0146.002; Mon, 26 Aug 2013 14:57:23 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "Michael Richardson <mcr+ietf@sandelman.ca> (mcr+ietf@sandelman.ca)" <mcr+ietf@sandelman.ca>
Thread-Topic: [Roll] [roll] #128: Trickle multicast could be considered in other applications?
Thread-Index: AQHOomLiWLQOe+5OH0qX8WENPNdGRZmnir1w
Date: Mon, 26 Aug 2013 14:57:22 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618CF9EF7@011-DB3MPN2-083.MGDPHG.emi.philips.com>
References: <031DD135F9160444ABBE3B0C36CED618CE7376@011-DB3MPN2-083.MGDPHG.emi.philips.com> <CE3A1504.22FF6%d.sturek@att.net> <031DD135F9160444ABBE3B0C36CED618CE748B@011-DB3MPN2-083.MGDPHG.emi.philips.com> <6504.1377480137@sandelman.ca>
In-Reply-To: <6504.1377480137@sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.103]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [Roll] [roll] #128: Trickle multicast could be considered in other applications?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 26 Aug 2013 14:57:46 -0000

> I really wonder about these MPL-ignorant nodes which are part of an LLN mesh (and therefore, I think), speak RPL.
> Can you tell me more about them so that I am less skeptical about them being mythical.

Nodes that are fully MPL-ignorant could be rightfully called mythical, at least I haven't seen an implementation or specification of such nodes within an MPL-enabled LLN mesh. I'm just considering the option that there could be Hosts that are unaware of the forwarding protocol used, whose multicast traffic needs to be interfaced to the MPL domain. If that is an option that no implementer would ever go for anyway, we can safely stop this discussion I think.

Background: A similar situation can be found in the ZigBee-IP specification, that defines "ZIP hosts" in the LLN mesh which do not implement the RPL routing protocol. These hosts send their IP packets to their parent "ZIP router" which further handles the packet using RPL. Sleepy Nodes are for example always ZIP hosts and never ZIP routers. In ZigBee-IP these Hosts are RPL-ignorant, but not MPL-ignorant.  My idea was that there could be another specification X that would define the Hosts also to be MPL-ignorant, for example to save energy in Sleepy Nodes.

regards,
Esko

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.