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

"Dijk, Esko" <esko.dijk@philips.com> Wed, 21 August 2013 12:50 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 BD4A211E839B for <roll@ietfa.amsl.com>; Wed, 21 Aug 2013 05:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uRTTmKwjezQB for <roll@ietfa.amsl.com>; Wed, 21 Aug 2013 05:50:27 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6BED711E839A for <roll@ietf.org>; Wed, 21 Aug 2013 05:50:25 -0700 (PDT)
Received: from mail99-co9-R.bigfish.com (10.236.132.235) by CO9EHSOBE007.bigfish.com (10.236.130.70) with Microsoft SMTP Server id 14.1.225.22; Wed, 21 Aug 2013 12:50:25 +0000
Received: from mail99-co9 (localhost [127.0.0.1]) by mail99-co9-R.bigfish.com (Postfix) with ESMTP id 402E448012C; Wed, 21 Aug 2013 12:50:25 +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(zz15d6O1432I9251I217bIdd85kzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzzz2dh2a8h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h1155h)
Received: from mail99-co9 (localhost.localdomain [127.0.0.1]) by mail99-co9 (MessageSwitch) id 1377089423296932_29419; Wed, 21 Aug 2013 12:50:23 +0000 (UTC)
Received: from CO9EHSMHS023.bigfish.com (unknown [10.236.132.238]) by mail99-co9.bigfish.com (Postfix) with ESMTP id 438D624004A; Wed, 21 Aug 2013 12:50:23 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by CO9EHSMHS023.bigfish.com (10.236.130.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 21 Aug 2013 12:50:22 +0000
Received: from 011-DB3MMR1-020.MGDPHG.emi.philips.com (10.128.28.101) by 011-DB3MMR1-005.MGDPHG.emi.philips.com (10.128.28.55) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 21 Aug 2013 12:50:00 +0000
Received: from 011-DB3MPN2-083.MGDPHG.emi.philips.com ([169.254.3.216]) by 011-DB3MMR1-020.MGDPHG.emi.philips.com ([fe80::65e7:4d4c:4c67:daa9%11]) with mapi id 14.03.0146.002; Wed, 21 Aug 2013 12:50:01 +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>, Adrian Farrel <adrian@olddog.co.uk>
Thread-Topic: [Roll] [roll] #128: Trickle multicast could be considered in other applications?
Thread-Index: AQHOnGBYx9PCJyaoF0yT9B4yI41o8JmfmAwg
Date: Wed, 21 Aug 2013 12:50:00 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618CE7376@011-DB3MPN2-083.MGDPHG.emi.philips.com>
References: <067.081907fd6195c3034e6e8c71a7eb4a93@trac.tools.ietf.org> <7297.1376772612@sandelman.ca>
In-Reply-To: <7297.1376772612@sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.138.224.32]
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: Wed, 21 Aug 2013 12:50:34 -0000

>    adrian> - do the hosts need to be in any way aware
>    adrian> that their mcast is supported by MPL?
>
> At some point the answer has been yes and at other points it has been no, and I guess I have to back to the document to remember what we concluded.

I believe that MPL-04 does not answer this, and perhaps even cannot, because it is out of scope in the current text.
It is not described how a non-MPL host can 'inject' its multicast packet into an MPL domain, or how an MPL Forwarder should 'demux' a multicast packet out from the MPL Domain so that nearby listening non-MPL hosts can receive the multicast.

Solutions for this exist that require a host to be aware of MPL, and solutions exist as well that don't require this.

If Section 3 (Applicability Statement) could just mention this, plus the other questions from ticket #128 that are now answered, I believe the ticket can be closed.

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.