Re: [6lowpan] WG adoption of draft-patil-6lowpan-v6over-btle-01.txt

Oliver Hahm <oliver.hahm@fu-berlin.de> Wed, 06 April 2011 13:18 UTC

Return-Path: <oliver.hahm@fu-berlin.de>
X-Original-To: 6lowpan@core3.amsl.com
Delivered-To: 6lowpan@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D396528C11A for <6lowpan@core3.amsl.com>; Wed, 6 Apr 2011 06:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNDA2nVQqf6Y for <6lowpan@core3.amsl.com>; Wed, 6 Apr 2011 06:18:42 -0700 (PDT)
Received: from stillroot.org (stillroot.org [85.10.195.133]) by core3.amsl.com (Postfix) with ESMTP id D770828C0EA for <6lowpan@ietf.org>; Wed, 6 Apr 2011 06:18:41 -0700 (PDT)
Received: by stillroot.org (Postfix, from userid 1007) id CD805544004; Wed, 6 Apr 2011 15:20:24 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by stillroot.org (Postfix) with ESMTP id 432EB544007; Wed, 6 Apr 2011 15:20:24 +0200 (CEST)
Received: from stillroot.org ([127.0.0.1]) by localhost (stillroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IxI31NZ86lvp; Wed, 6 Apr 2011 15:20:22 +0200 (CEST)
Received: from stedten.imp.fu-berlin.de (stedten.imp.fu-berlin.de [160.45.114.7]) by stillroot.org (Postfix) with ESMTPA id 2B1C3544004; Wed, 6 Apr 2011 15:20:21 +0200 (CEST)
Received: by stedten.imp.fu-berlin.de (sSMTP sendmail emulation); Wed, 06 Apr 2011 15:20:20 +0200
Date: Wed, 06 Apr 2011 15:20:20 +0200
From: Oliver Hahm <oliver.hahm@fu-berlin.de>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <20110406132020.GI7336@stillroot.org>
References: <C9BB1E4D.12A43%basavaraj.patil@nokia.com> <4D95B9DF.3030309@gmail.com> <4D95C1E9.1070901@gridmerge.com> <1301679639.6495.12.camel@Nokia-N900> <13C0FE6D-2E82-4534-BF3A-34CBE7B5A817@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <13C0FE6D-2E82-4534-BF3A-34CBE7B5A817@tzi.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.958814, version=1.1.7
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] WG adoption of draft-patil-6lowpan-v6over-btle-01.txt
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 13:18:42 -0000

Hi,

Am Mon, Apr 04, 2011 at 10:05:25PM +0200 schrieb Carsten Bormann:
> > Therefore, a more generic specification for IPv6 over low-power wireless
> > foo would be really interesting for us - and probably a lot of other
> > people as CC1020 and CC110x are very popular transceivers for WSN.
> 
> I think that is an interesting idea.  How much of such a specification could
> be generic and how much would need to be specific to each of the radios?
> Can you describe the decisions you had to take in applying 6LoWPAN to these
> radios?

for our current implementation we tried to change as little as possible in
comparison to RFC 4944.  Therefore, we also adapted the 802.15.4 frame format,
though this was not the optimum choice as we had to deal with a much smaller
packet size. (cc1100 supports natively only 64 byte packets.)

Besides, we have a different addressing scheme at the link layer and have no
PAN ids or anything comparable.

In addition, we could not use 802.15.4 at the physical layer due to hardware
limitations (neither DSSS nor PSSS are supported by the transceiver) and use a
different media access. However, this obviously does not affect 6LoWPAN
itself.
 
> And, even better, can you write a draft?

Okay, I'll try to do this and then we can see how generic such a specification
could be.

Regards
Oleg