IETF Logo Mail Archive

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

<johanna.1.nieminen@nokia.com> Fri, 01 April 2011 10:47 UTC

Return-Path: <johanna.1.nieminen@nokia.com>
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 87A5C3A67E1 for <6lowpan@core3.amsl.com>; Fri, 1 Apr 2011 03:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[AWL=0.888, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 z0r6o0H2rxqj for <6lowpan@core3.amsl.com>; Fri, 1 Apr 2011 03:47:24 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id AF4403A67D3 for <6lowpan@ietf.org>; Fri, 1 Apr 2011 03:47:24 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p31Amaf9015383; Fri, 1 Apr 2011 13:49:01 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Apr 2011 13:48:45 +0300
Received: from 008-AM1MMR1-006.mgdnok.nokia.com (65.54.30.61) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 1 Apr 2011 12:48:44 +0200
Received: from 008-AM1MPN1-002.mgdnok.nokia.com ([169.254.2.164]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0270.002; Fri, 1 Apr 2011 12:48:38 +0200
From: johanna.1.nieminen@nokia.com
To: alexandru.petrescu@gmail.com, cabo@tzi.org
Thread-Topic: Re: [6lowpan] WG adoption of draft-patil-6lowpan-v6over-btle-0 1.txt
Thread-Index: AQHL8FpbPwaOwcVfmk2MePYwCi1T7Q==
Date: Fri, 01 Apr 2011 10:48:38 +0000
Message-ID: <RcwsGdkYYMM2@F5DFnfTg>
References: <1301488616.3846.752.camel@d430> <FC26D804-9CB3-466E-88A2-95ABFDFA6E63@tzi.org> <4D95A2E4.50609@gmail.com> <6C1C71A8-FC22-4751-A8C9-3320F90081A0@tzi.org>, <4D95A9EF.2080406@gmail.com>
In-Reply-To: <4D95A9EF.2080406@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Apr 2011 10:48:45.0571 (UTC) FILETIME=[5FD50530:01CBF05A]
X-Nokia-AV: Clean
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] WG adoption of draft-patil-6lowpan-v6over-btle-0 1.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: Fri, 01 Apr 2011 10:47:25 -0000

Hi,
There are major differences between 802.15.4 and bt-le in the link and phy layers, topology etc. In fact, there are major differences between Bt and Bt-le as well. 802.15.4 can not be considered as a generalization of  Bluetooth modifications.
Johanna
--- alkuperäinen viesti ---
Lähettäjä: "ext Alexandru Petrescu" <alexandru.petrescu@gmail.com>
Aihe: Re: [6lowpan] WG adoption of draft-patil-6lowpan-v6over-btle-01.txt
Päivämäärä: 1. huhtikuuta 2011
Aika: 12:33:43


Le 01/04/2011 12:12, Carsten Bormann a écrit :
>> It seems to me IMHO bt-le is just a new phy, but same mac, hence ip
>> would not be affected.
>
> From the presentation, I had a different impression.
>
>> But of course, a document stating we do things over bt-le as
>> usually as over bt, would not hurt.
>
> Actually, it is required, as RFC4944 and its updates only define
> 6LoWPAN for IEEE 802.15.4. If two people took these documents and
> tried to apply them to BT-LE, they wouldn't necessarily arrive at
> interoperable specifications.

To me IMHO bluetooth is to 802.15.4 what wifi is to 802.11 - a marketing
name.  It seems sufficient to specify ipv6 over 802.15.4  and that would
cover all variants of bluetooth.  There is no ipv6-over-802.11n, nor
ipv6-over-wifilowpower, for example.

I may be wrong though about bluetooth being mostly 802.15.4 rfc4944 and
rfc2460.

>> Is the WG re-opened?
>
> No, it is alive and well until such a time when it is actually being
> closed. All that was said is that the Prague meeting will be the last
> physical meeting of the WG. We want to close our unfinished business,
> and a number of documents are based on discussions that went on at
> least since Beijing, so if they fit our charter and we have energy to
> work on them, there is no problem doing that.

sounds like doing new work without physical meetings... ok...

Alex

>
> Gruesse, Carsten
>

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan

v2.23.0 | Report a Bug | By Email