From: Alexander Aring <alex.aring@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: Bluetooth 6LoWPAN and routing
Date: Thu, 24 Oct 2013 14:25:14 +0200 [thread overview]
Message-ID: <20131024122452.GA5491@omega> (raw)
In-Reply-To: <5268C214.2040307@linux.intel.com>
Hi Jukka,
On Thu, Oct 24, 2013 at 09:45:40AM +0300, Jukka Rissanen wrote:
> Hi,
>
> I have been prototyping with BT 6LoWPAN support (using this draft
> http://tools.ietf.org/html/draft-ietf-6lowpan-btle-12 as a
> reference). I sent first version yesterday to linux-bluetooth ml
> http://thread.gmane.org/gmane.linux.bluez.kernel/39394
>
I see you take many code from the 6lowpan ieee802154 implementation.
(Just notice you drop the original authors from there)
I have a couple of patches to fix a lot of bugs in the current 6LoWPAN
ieee802154 implementation.
Some bugs which I found:
- Fix race conditions in fragmentation handling
- Fix UDP compression/uncompressionm, which is completly broken
- Fragmentation handling isn't rfc4944 compatible
And some other improvements. I see your rfc has the same issues (e.g.
fragmentation race conditions).
Currently I preparing these patches for mainlining.
But my question is:
What we do now, make a generic 6LoWPAN implementation. Or bluetooth,
ieee802154 makes his own implementation?
- Alex
next prev parent reply other threads:[~2013-10-24 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 6:45 Bluetooth 6LoWPAN and routing Jukka Rissanen
2013-10-24 11:55 ` Hannes Frederic Sowa
2013-10-24 12:25 ` Alexander Aring [this message]
2013-10-24 12:48 ` Jukka Rissanen
2013-11-04 21:46 ` Claudio Takahasi
2013-11-04 22:53 ` Alexander Aring
2013-11-05 8:36 ` Jukka Rissanen
2013-11-05 8:52 ` Alexander Aring
2013-11-05 8:55 ` Alexander Aring
2013-11-06 14:17 ` Claudio Takahasi
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=20131024122452.GA5491@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=netdev@vger.kernel.org \
/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).