Re: [6lowpan] Mesh under routing and Neighbor Discovery

"Benjamin A. Rolfe" <ben@blindcreek.com> Fri, 08 June 2012 16:17 UTC

Return-Path: <ben@blindcreek.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013CD21F88E8 for <6lowpan@ietfa.amsl.com>; Fri, 8 Jun 2012 09:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.141
X-Spam-Level:
X-Spam-Status: No, score=-1.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
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 vOQmp-VWc0C9 for <6lowpan@ietfa.amsl.com>; Fri, 8 Jun 2012 09:17:14 -0700 (PDT)
Received: from wilson.nswebhost.com (wilson.nswebhost.com [209.217.228.59]) by ietfa.amsl.com (Postfix) with ESMTP id 9F80221F88C9 for <6lowpan@ietf.org>; Fri, 8 Jun 2012 09:17:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=blindcreek.com; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=LGQv1Gof5d9Q04JGLRRPS9350sbVm2UBs5yf0Vqk2yc=; b=HqewcldR2OymJlojTpKcr8uxohriHphUtVq1YhXTSnB08HtKkOEeAeYFO31/jzpsuueWaIg6teekWYa1jfIVqPo/49lv8HW5QlmnGdetl55HI5T4UBJI7Zu5/xt4C8RX;
Received: from [64.74.213.174] (port=53698 helo=[192.168.250.11]) by wilson.nswebhost.com with esmtpa (Exim 4.77) (envelope-from <ben@blindcreek.com>) id 1Sd1s7-0000Ql-Rx for 6lowpan@ietf.org; Fri, 08 Jun 2012 11:17:12 -0500
Message-ID: <4FD22597.3050808@blindcreek.com>
Date: Fri, 08 Jun 2012 09:17:27 -0700
From: "Benjamin A. Rolfe" <ben@blindcreek.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Lightning/1.0b2 Thunderbird/3.1.20
MIME-Version: 1.0
To: 6lowpan@ietf.org
References: <1DBF40D7-49EA-458B-AED7-0B34FBCB9FB2@gmail.com> <16D60F43CA0B724F8052D7E9323565D72AB46D2FCE@EUSAACMS0715.eamcs.ericsson.se> <CAOdYGf2VUFrg2LDBT0-XbY3RN6PdOoyA9RZiDC8i+9GWTSQBNw@mail.gmail.com> <4FD20710.4000404@labs.htt-consult.com>
In-Reply-To: <4FD20710.4000404@labs.htt-consult.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - wilson.nswebhost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - blindcreek.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [6lowpan] Mesh under routing and Neighbor Discovery
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 16:17:16 -0000

Thanks Myung and Robert for bringing attention to the work already done and being considered in 802.15. I would like to add a couple clarifying points to help people understand how to participate.

Robert correctly points out that there is a fee to attend 802 plenary meetings (face to face physical meetings).  In Working Group (WG) 802.15, there is also a fee for attending the interim meetings. The current rules require physical attendance to achieve voting status in a working group. However, that is not the only way one can participate and contribute.  Traditionally much of the work occurs between meetings via the email reflector and teleconferences, which are open to anyone who wishes to participate.   All contributions used during development of a draft are posted to the open document server, and WG 15 allows anyone to post documents (you need an IEEE "login" which you can free even if you are not an IEEE member). In the past many significant contributions have been made by folks unable to attend physical meetings.  Generally if a good idea is presented in any of the various mediums (physical, TC, email) the group will take it and run with it.

Establishment of an Interest Group (IG) is not an indication that the WG has decided if the proposed idea fits within scope of a particular standard or recommended practice.  At this point, it has not been decided if L2 routing is "in scope" of 802.15.4 PHY/MAC standard.  I expect we will hear more than on opinion on this, and perhaps some enthusiastic discussion.  There are several paths it may take, the IG is the first step in figuring out where to start. 

Hope this helps! 

-Ben


Further on this.

My understanding is that 802.15.5 is NOT being used by anyone. 

Zigbee has their own mesh methodology.  I do not have the documents, but as it was described to me, it is based on path discovery after network admission.

There is a new Mesh Under Routing Interest Group in 802.15, with a call for submissions for for the July 15th meeting.  This IG is not yet on the document server, it seems the submissions are being posted under the WNG SG:

https://mentor.ieee.org/802.15/documents?is_group=wng0" rel="nofollow">https://mentor.ieee.org/802.15/documents?is_group=wng0

So far there is one submission:

https://mentor.ieee.org/802.15/dcn/12/15-12-0268-01-wng0-l2-routing-demands-for-fan.ppt" rel="nofollow">https://mentor.ieee.org/802.15/dcn/12/15-12-0268-01-wng0-l2-routing-demands-for-fan.ppt

Mesh under IS out of scope for IETF and 6lowpan.  It IS in scope for 802.15.  Unfortunately to play in IEEE, you have to pay.  That is attend a meeting. Though the document server is publicly available.

Oh the chair for this study group is Clint Powell, cpowell@ieee.org.

On 06/04/2012 11:40 PM, Myung Jong Lee wrote:
Hi Damien and all,

Though I am not an active member for 6lowpan, I just like to note that there  is a "mesh under" routing standard, IEEE 802.15.5 a recommended practice, completed in 2009. You may take a look at it. It is built on IEEE 802.15.4b and sitting below IP layer.    I believe it could be one of the feasible approaches for mesh under technologies. For the details, you may refer to the standard itself or the paper, " IEEE 802.15.5 WPAN mesh standard-low rate part: meshing the wireless sensor networks," IEEE JSAC, Vol 28, No. 7, 2010 .

Thanks,

Myung


On Tue, Jun 5, 2012 at 9:10 AM, Samita Chakrabarti <samita.chakrabarti@ericsson.com> wrote:
Hi Damien,
 
Please find responses in-line.
 


From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf Of Damien Roth
Sent: Monday, June 04, 2012 5:03 AM
To: 6lowpan@ietf.org
Subject: [6lowpan] Mesh under routing and Neighbor Discovery

Hello,

I continue my investigations the neighbor discovery protocol for 6LoWPAN (draft-ietf-6lowpan-nd-18), and there is one point that remains unclear to me.

With 6LoWPAN, two routing mechanisms can be used : route over and mesh under. Everything is OK with the route over mechanism but I'm locked with mesh-under. In mesh-under routing, there is only two entities, the 6LBR (border router) and the hosts. Multiple hops may be needed to for hosts to reach the 6LBR. 
 
====> In mesh under case, the assumption is that all hosts are directly IP-reachable from 6LBR. How the packets are flown from a host to the 6LBR ( using a L2-mechanism) is out of scope of the document. Currently I don't know of  L2-routing protocols for mesh-under network - however, there might be some proprietary ones.

My problem is in multihop configuration : how the multicast Router Solicitation messages, used by the neighbor discovery protocol, can reach the 6LBR ?
Does it depends on the routing protocol used ?  
 
 
====>  Please check the section 10 (Examples) to get an understanding how the routers and hosts bootstrap in the multi-hop 6lowpan networks.  Initial multicast RS is sent only to the local subnet  and taken care by the local 6LR router in case of route-over scenario.
 
 
 
-Samita

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/6lowpan




--
Myung J. Lee, Ph.D
Professor
Dept. of Electrical and Computer Engineering
City University of New York, City College
140th Street, New York, NY 10031
(O)+1-212-650-7260
(E) lee@ccny.cuny.edu


_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan" rel="nofollow">https://www.ietf.org/mailman/listinfo/6lowpan

--
Standard Robert Moskowitz
Senior Technical Advisor
Security & Standards
Verizon Business Systems
C:      248-219-2059
F:      248-968-2824
E:      robert.moskowitz@verizonbusiness.com

There's no limit to what can be accomplished if it doesn't matter who gets the credit
_______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan" rel="nofollow">https://www.ietf.org/mailman/listinfo/6lowpan