linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: Alexander Aring <aar@pengutronix.de>,
	Linux Bluetooth <linux-bluetooth@vger.kernel.org>,
	linux-wpan@vger.kernel.org, kernel@pengutronix.de,
	patrik.flykt@linux.intel.com
Subject: Re: current btle 6lowpan issues
Date: Tue, 05 Jul 2016 09:13:15 -0400	[thread overview]
Message-ID: <2525.1467724395@dooku.sandelman.ca> (raw)
In-Reply-To: <1466071258.31678.12.camel@linux.intel.com>

Jukka Rissanen <jukka.rissanen@linux.intel.com> 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...

      parent reply	other threads:[~2016-07-05 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 18:02 current btle 6lowpan issues Alexander Aring
2016-06-16 10:00 ` Jukka Rissanen
2016-06-16 13:41   ` Patrik Flykt
2016-06-16 21:38     ` Alexander Aring
2016-06-20  7:07       ` Jukka Rissanen
2016-07-05 13:13   ` Michael Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2525.1467724395@dooku.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=aar@pengutronix.de \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=patrik.flykt@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).