linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <aring@mojatatu.com>
To: Sujay G <sujay.g@hcl.com>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: about openthread and 6lowpan
Date: Mon, 10 Sep 2018 11:18:43 -0400	[thread overview]
Message-ID: <20180910151843.dqdlhnttlh7gdsmi@x220t> (raw)
In-Reply-To: <SG2PR04MB315811F19F2A13136294C6A9EF060@SG2PR04MB3158.apcprd04.prod.outlook.com>

Hi,

On Sun, Sep 09, 2018 at 03:05:50PM +0000, Sujay G wrote:
>  Hi,
> 
> I have been testing openThread on Docker. I wanted to use 6Lowpan with openthread.
> I assumed openThread would interact with wpan interfaces  and added  wpan interfaces in container namespace  but it did not work.
> 
> Then I came across change for 6Lowpan.  Comparison yielded changes in 7 files  vs the latest openThread repositiry
> github.com/openthread/openthread/compare/master...linux-wpan:af802154
> 
> I manually merged the files and am trying to resolve the errors.
> 
> Had few queries regarding the openThread and 6Lowpan
> 
> Why was the project (af802154) abandoned ?

I am personally not interested to run openthread as a user space
solution which can be sold as "not use Linux, use mine software".

> Was openThread working with the above 6Lowpan changes ?

With limitations, which can be improved to support more user space
stacks in the wpan subsystem. I used only do testing against their "MLE"
implementation.

> Does the current openThread stack support 6Lowpan ? any configuration needs to be enabled ?    or is it the right way to port the  af802154 to current implementation of openthread ?
> 

"openThread stack support 6Lowpan"

I asking me this question myself. According their MLE implementation
it's a forked standard from IETF draft. So you can't be sure if they ever
changed something in IETF 6LoWPAN, foo which is then a forked standard.

Also according to "MLE", they sold it with the words "MLE" but it wasn't "MLE",
so you can't be sure in any 6LoWPAN protocols as well.

I think openthread are still "good people" because they have an open
implementation. It's totally weird that the standard is closed but there
exist open implementation which seems to be Thread certificated.

Thread works in this case only as user space stack with openthread and a
RAW L2 frame socket layer as AF_PACKET offers you and not in any
productive case because limitations.

---

The right way? It's not, see my other post about my complain why I don't
want to work on openthread as user space stack. [0]

We need to make some library wrapper around openthread and map it to Linux
6LoWPAN/802.15.4 stack.

- Alex

[0] https://www.spinics.net/lists/linux-wpan/msg04949.html

      parent reply	other threads:[~2018-09-10 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SG2PR04MB31586E124C6C9A919150F826EF000@SG2PR04MB3158.apcprd04.prod.outlook.com>
     [not found] ` <SG2PR04MB3158366EFF8CBC241C84FFD5EF060@SG2PR04MB3158.apcprd04.prod.outlook.com>
2018-09-09 15:05   ` about openthread and 6lowpan Sujay G
2018-09-09 20:49     ` Michael Richardson
2018-09-10 15:06       ` Alexander Aring
2018-09-20  6:06         ` Sujay G
2018-09-20  6:57           ` Sujay G
2018-09-24 20:56             ` Alexander Aring
2018-09-26 13:28               ` Sujay G
2018-09-26 19:41                 ` Alexander Aring
2018-09-24 20:52           ` Alexander Aring
2018-09-10 15:18     ` Alexander Aring [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=20180910151843.dqdlhnttlh7gdsmi@x220t \
    --to=aring@mojatatu.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=sujay.g@hcl.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).