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

Samita Chakrabarti <> Tue, 05 June 2012 00:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B8CF521F8667 for <>; Mon, 4 Jun 2012 17:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2-GMA5cwmXmE for <>; Mon, 4 Jun 2012 17:10:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A617921F879C for <>; Mon, 4 Jun 2012 17:10:21 -0700 (PDT)
Received: from ([]) by (8.13.8/8.13.8) with ESMTP id q550AIiQ024896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Jun 2012 19:10:18 -0500
Received: from ([]) by ([]) with mapi; Mon, 4 Jun 2012 20:10:18 -0400
From: Samita Chakrabarti <>
To: Damien Roth <>, "" <>
Date: Mon, 4 Jun 2012 20:10:17 -0400
Thread-Topic: [6lowpan] Mesh under routing and Neighbor Discovery
Thread-Index: Ac1CShk3Q5xcIN67RM656HlMqlgbZAAYuk2w
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_16D60F43CA0B724F8052D7E9323565D72AB46D2FCEEUSAACMS0715e_"
MIME-Version: 1.0
Subject: Re: [6lowpan] Mesh under routing and Neighbor Discovery
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Jun 2012 00:10:29 -0000

Hi Damien,

Please find responses in-line.

From: [] On Behalf Of Damien Roth
Sent: Monday, June 04, 2012 5:03 AM
Subject: [6lowpan] Mesh under routing and Neighbor Discovery


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.