[6lowpan] Mesh under routing and Neighbor Discovery

Damien Roth <d42roth@gmail.com> Mon, 04 June 2012 12:03 UTC

Return-Path: <d42roth@gmail.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 24CA521F877E for <6lowpan@ietfa.amsl.com>; Mon, 4 Jun 2012 05:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id nCRgyK0pmzHz for <6lowpan@ietfa.amsl.com>; Mon, 4 Jun 2012 05:03:21 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 65B0021F86BE for <6lowpan@ietf.org>; Mon, 4 Jun 2012 05:03:21 -0700 (PDT)
Received: by werb13 with SMTP id b13so3215321wer.31 for <6lowpan@ietf.org>; Mon, 04 Jun 2012 05:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer; bh=eaffP8nd7cvAIpEAlUJaUkCcISQKeqTicHxao/x8z+c=; b=gp9eRjMl2j4zlfdG9oKVn84POsLkhQfb6aL8E0SdmxNMgs9qvWfbwSVS4X3PjDOawL R76XqyohkNBYOiBQTZ7/gB/XSh3YrtoZtPfFi3TlxaaFd6dcv+QWmTSMQObdJVdqJpId I63Tlt+anBvAPKMDoHtlG3cqvTNeBvw3rmKcs5agwZG7vtBbaYe9I2B1V4LCaQ+tV5UQ WblKCEUJl9CkZY8Lmlf+OFanZaf8PGpDoNRPb/au+kg7lKsVk3jQKLosRDELShueq1PS RevG0JioX377Ls0IMQ72jwFTAV73fg75n52HIo2NA242hRG4pBt2lbALC+2RzT2VXaCe ucyA==
Received: by with SMTP id p21mr11045504wej.1.1338811400504; Mon, 04 Jun 2012 05:03:20 -0700 (PDT)
Received: from holonet.u-strasbg.fr (holonet.u-strasbg.fr. []) by mx.google.com with ESMTPS id eb8sm19771596wib.11.2012. (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 05:03:20 -0700 (PDT)
From: Damien Roth <d42roth@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_40717A3F-8094-42F9-8ED9-670CBE02D3B6"
Date: Mon, 4 Jun 2012 14:03:19 +0200
Message-Id: <1DBF40D7-49EA-458B-AED7-0B34FBCB9FB2@gmail.com>
To: 6lowpan@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [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: Mon, 04 Jun 2012 12:03:22 -0000


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.

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 ?


Damien ROTH - PhD student
Strasbourg University, France