Return-Path: From: Michael Richardson To: Jukka Rissanen cc: Alexander Aring , Linux Bluetooth , linux-wpan@vger.kernel.org, kernel@pengutronix.de, patrik.flykt@linux.intel.com Subject: Re: current btle 6lowpan issues In-reply-to: <1466071258.31678.12.camel@linux.intel.com> References: <1466071258.31678.12.camel@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 05 Jul 2016 09:13:15 -0400 Message-ID: <2525.1467724395@dooku.sandelman.ca> Sender: linux-wpan-owner@vger.kernel.org List-ID: Jukka Rissanen wrote: >> I started to work on this but the issue 2. is a big change in btle >> 6lowpan so I want to start the discussion about to fix that to doing >> it in the right way. >> >> Jukka, do you agree that this behaviour is currently broken in btle >> 6lowpan? > Yes you are right that there are issues. Fortunately the bt0 is > currently a point-to-point link in which case ND is not really done and > everything kind of "works" ok. I've read that btle 4.2, while it won't permit one to maintain multiple links at the same time, will permit a device to quickly cycle between multiple attachments. A device could therefore move from one btle star to another one several times per second, and route packets that way. This puts btle in the same space as time slotted -- 6tisch (802.15.4e). My gut is that btle will be *the* low-power mesh tech in ten years. (Unless it's DECT...) The other situation in which we might need more than ptp is when we have multiple btle radios, or when we are doing any kind of layer-3 mesh with multiple technologies...