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

peter van der Stok <stokcons@xs4all.nl> Thu, 15 November 2012 10:01 UTC

Return-Path: <stokcons@xs4all.nl>
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 4A7C121F8530 for <roll@ietfa.amsl.com>; Thu, 15 Nov 2012 02:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.297
X-Spam-Level:
X-Spam-Status: No, score=-0.297 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 6o6VI2rV99-h for <roll@ietfa.amsl.com>; Thu, 15 Nov 2012 02:01:58 -0800 (PST)
Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFB321F84DB for <roll@ietf.org>; Thu, 15 Nov 2012 02:01:58 -0800 (PST)
Received: from roundcube.xs4all.nl (roundcube6.xs4all.net [194.109.20.204]) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id qAFA1Qnl005331; Thu, 15 Nov 2012 11:01:26 +0100 (CET) (envelope-from stokcons@xs4all.nl)
Received: from a82-95-140-48.adsl.xs4all.nl ([82.95.140.48]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Thu, 15 Nov 2012 11:01:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Thu, 15 Nov 2012 11:01:25 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: "Dijk, Esko" <esko.dijk@philips.com>
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <031DD135F9160444ABBE3B0C36CED618B0C67D@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>
Message-ID: <717524bfa3e3bcd7b8e99d632178d95c@xs4all.nl>
X-Sender: stokcons@xs4all.nl (wZ/eM00kM1/deZngrTA04Sj+t9zxnuby)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Cc: roll@ietf.org
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
Reply-To: consultancy@vanderstok.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: Thu, 15 Nov 2012 10:01:59 -0000

HI Esko,

The few LoWPAN implementations I have experience with, ignore the 
PANid.
Actually, this is great because when the original PANid node is removed 
the network continues to exist.
Contrary to Zigbee, where this is a problem and has led to 
standardization modifications.
So please do not start this discussion again.

So your implication (strange or not) is correct, and therfore I create 
these problems with unicast prefix based MC addresses.

Greetings,

Peter

Dijk, Esko schreef op 2012-11-15 10:46:
> Hi Peter, Michael,
>
> a question from your last 2 emails is the following:
> if multiple LoWPAN networks are assigned the same 802.15.4 channel
> (which is likely as Peter explained), would they not be assigned a
> different Pan-ID to logically separate them? So for the drawing that
> shows the 6 border routers case, there would be no mutual 
> connectivity
> between dissemination regions anyway.
>
> A related question is whether nodes from different LoWPANs are
> allowed, or not, to mutually communicate. (I could not find text on
> this in RFC 6282 and RFC 6775 (6lowpan-nd) ).
> If they are allowed that leads to some strange implications, for
> example a node in LoWPAN1 sends a link-local packet which is received
> by a node in LoWPAN2 even though it is on a different link (and
> different IPv6 prefix).
>
> I can put this question on the 6lowpan list, if needed.
>
> regards,
> Esko
>
>
> -----Original Message-----
> From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf
> Of peter van der Stok
> Sent: Wednesday 14 November 2012 9:38
> To: Michael Richardson
> Cc: roll@ietf.org
> Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine
> scope of MPL domain
>
> Hi Michael,
>
> sorry to be confusing.
>
> Again, this is not a real installation, just an example of what to
> expect.
> Surface area can be something like 100x30 square meters.
>
> I show 6 border routers coinciding with 6 disseminatiuon areas due to 
> a
> remark by Dario where he asked if it is possible that multiple
> disseminations areas can be present in one PAN.
> The answer is yes, because giving a border router to each 
> dissemination
> area (6) is quite expensive.
>
> Concerning the use of the same channel.
> When we have one PAN, one channel is used, that is clear.
> Having several PANs, it perspires that often only 2 channels of the
> ones specified by 802.15.4 provide good communication ([presence of
> 802.11, etc.).
>
> Several other additional organisational boundary conditions can 
> dictate
> the channel numbers.
>
> Hope this helps,
>
> peter
>
>
> Michael Richardson schreef op 2012-11-12 23:07:
>> splitting up your text to emphasize a few things:
>>
>>>>>>> "peter" == peter van der Stok <stokcons@xs4all.nl> writes:
>>     peter> The nodes in all networks use the same communication
>> channel.
>>
>> ...
>>
>>     peter> not forward the message.  In this network configuration
>> the
>>     peter> dissemination area is identical with a network.  From a
>> cost
>>     peter> perspective (less border routers) it is more realistic if
>> one
>>     peter> network covers the whole floor.
>>
>> But, in your diagram, you have 6 border routers?!?
>>
>> I don't understand why nodes in area1 and area2 should use the same
>> communication channel.
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
> ________________________________
> 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.