From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Aring Subject: Re: Bluetooth 6LoWPAN and routing Date: Tue, 5 Nov 2013 09:55:55 +0100 Message-ID: <20131105085555.GA32080@omega> References: <5268C214.2040307@linux.intel.com> <20131024122452.GA5491@omega> <52691711.3010909@linux.intel.com> <1383640589.12691.36.camel@jrissane-mobl.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Claudio Takahasi , netdev@vger.kernel.org To: Jukka Rissanen Return-path: Received: from mail-ea0-f182.google.com ([209.85.215.182]:54110 "EHLO mail-ea0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753548Ab3KEI4C (ORCPT ); Tue, 5 Nov 2013 03:56:02 -0500 Received: by mail-ea0-f182.google.com with SMTP id o10so3958059eaj.41 for ; Tue, 05 Nov 2013 00:56:00 -0800 (PST) Content-Disposition: inline In-Reply-To: <1383640589.12691.36.camel@jrissane-mobl.ger.corp.intel.com> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Nov 05, 2013 at 10:36:29AM +0200, Jukka Rissanen wrote: > Hi Claudio, > > On ma, 2013-11-04 at 19:46 -0200, Claudio Takahasi wrote: > > Hi Jukka, > > > > On Thu, Oct 24, 2013 at 9:48 AM, Jukka Rissanen > > wrote: > > > Hi Alexander, > > > > > > > > > On 24.10.2013 15:25, Alexander Aring wrote: > > >> > > >> 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) > > > > > > > > > Hmm, those got dropped, I am sorry about that. I will add the original > > > authors information of course. > > > > > > > > >> > > >> 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. > > > > > > > > > Excellent news! > > > > > > Is it necessary to implement 6loWPAN fragmentation/reassembling? For > > Bluetooth, I thought L2CAP FAR (Fragmentation and Reassembling) could > > handle the transfer of IPv6 packets that doesn't fit in one single > > BTLE PDU. > > Yes, the Bluetooth 6lowpan code I sent handles the L2CAP FAR already. > The question is who handles the IPv6 packets that are larger than > IPV6_MIN_MTU (1280 bytes), or is that automatically done by other parts ahh I understand now, yes that's handled by the normal IPv6 Fragmentation. But you don't want a high payload like this. ;) - Alex