IETF Logo Mail Archive

Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain

"Dijk, Esko" <esko.dijk@philips.com> Tue, 04 December 2012 14:32 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 801C521F8AD0 for <roll@ietfa.amsl.com>; Tue, 4 Dec 2012 06:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekXMsIqshOw7 for <roll@ietfa.amsl.com>; Tue, 4 Dec 2012 06:32:46 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id 61B4F21F89DD for <roll@ietf.org>; Tue, 4 Dec 2012 06:32:46 -0800 (PST)
Received: from mail149-ch1-R.bigfish.com (10.43.68.245) by CH1EHSOBE006.bigfish.com (10.43.70.56) with Microsoft SMTP Server id 14.1.225.23; Tue, 4 Dec 2012 14:32:45 +0000
Received: from mail149-ch1 (localhost [127.0.0.1]) by mail149-ch1-R.bigfish.com (Postfix) with ESMTP id 5AE0A38014C; Tue, 4 Dec 2012 14:32:45 +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: -31
X-BigFish: VPS-31(zz217bI15d6O9251J542Izz1de0h1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1155h)
Received: from mail149-ch1 (localhost.localdomain [127.0.0.1]) by mail149-ch1 (MessageSwitch) id 1354631563373705_3241; Tue, 4 Dec 2012 14:32:43 +0000 (UTC)
Received: from CH1EHSMHS030.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.243]) by mail149-ch1.bigfish.com (Postfix) with ESMTP id 4F0F720071; Tue, 4 Dec 2012 14:32:43 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by CH1EHSMHS030.bigfish.com (10.43.70.30) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 4 Dec 2012 14:32:40 +0000
Received: from 011-DB3MMR1-019.MGDPHG.emi.philips.com (10.128.28.106) by 011-DB3MMR1-011.MGDPHG.emi.philips.com (10.128.28.50) with Microsoft SMTP Server (TLS) id 14.2.318.3; Tue, 4 Dec 2012 14:32:38 +0000
Received: from 011-DB3MPN2-082.MGDPHG.emi.philips.com ([169.254.2.225]) by 011-DB3MMR1-019.MGDPHG.emi.philips.com ([10.128.28.106]) with mapi id 14.02.0318.003; Tue, 4 Dec 2012 14:32:38 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "roll@ietf.org" <roll@ietf.org>
Thread-Topic: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
Thread-Index: AQHNwkOFtl9ztYUSrkiATuslfJmcUZfpG0MQgAVVjYCAAmIfMIAAeegAgAADkUCAAbgKAIAVyJ4Q
Date: Tue, 04 Dec 2012 14:32:37 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618B3646A@011-DB3MPN2-082.MGDPHG.emi.philips.com>
References: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org> <B50D0F163D52B74DA572DD345D5044AF0F6EFA99@xmb-rcd-x04.cisco.com> <50932647.3050509@exegin.com> <B50D0F163D52B74DA572DD345D5044AF0F6F2837@xmb-rcd-x04.cisco.com> <5094202F.4010805@exegin.com> <B50D0F163D52B74DA572DD345D5044AF0F6F874A@xmb-rcd-x04.cisco.com> <509C03C2.50809@exegin.com> <B50D0F163D52B74DA572DD345D5044AF0F714CBF@xmb-rcd-x04.cisco.com> <509C5F00.2050204@exegin.com> <109e9168af966b0ee543f13886fef7ef@xs4all.nl> <8796.1352758060@sandelman.ca> <895d55da5f389dc29760cd52aaf91d61@xs4all.nl> <031DD135F9160444ABBE3B0C36CED618B0C67D@011-DB3MPN2-082.MGDPHG.emi.philips.com> <6733.1353180917@obiwan.sandelman.ca> <031DD135F9160444ABBE3B0C36CED618B1D844@011-DB3MPN2-083.MGDPHG.emi.philips.com> <21170.1353338118@obiwan.sandelman.ca> <031DD135F9160444ABBE3B0C36CED618B20638@011-DB3MPN2-083.MGDPHG.emi.philips.com> <22106.1353433382@obiwan.sandelman.ca>
In-Reply-To: <22106.1353433382@obiwan.sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [62.140.132.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 04 Dec 2012 14:32:47 -0000

Just to check our current understanding of scope:

> How does a node determine what the scope of the MPL domain?
>From the I-D -02, it is "multicast scope of the IPv6 Destination Address of an MPL multicast packet". So it can be derived from the mcast address(es) that MPL uses which are defined in application code or in a config file or so.

> Is this an intrinsic (provisioned) property of a node?
- if encapsulation is used, I expect the outer IP address is configured in the node (e.g. FF05::MPL)
- if encapsulation is not used, the IP address where to send to or to receive on would be set by the application code i.e. it's also configured on the node (e.g. FF05::1234)

>From the IP address(es) the MPL scope follows.

Esko

-----Original Message-----
From: mcr@obiwan.sandelman.ca [mailto:mcr@obiwan.sandelman.ca] On Behalf Of Michael Richardson
Sent: Tuesday 20 November 2012 18:43
To: roll@ietf.org
Cc: consultancy@vanderstok.org; Dijk, Esko
Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain


okay, so we have the example of 6 offices with a single 6LBR.
They form a single PAN (PAN-ID is irrelevant).  There is a need to multicast within each of the offices.

How does a node determine what the scope of the MPL domain?
Is this an intrinsic (provisioned) property of a node?
Do we support non-convex MPL domains?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


________________________________
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.

v2.23.0 | Report a Bug | By Email