IETF Logo Mail Archive

Re: [6lo] Adopting draft-ietf-6lowpan-btle

<teemu.savolainen@nokia.com> Mon, 14 October 2013 18:25 UTC

Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF44C21E80B3 for <6lo@ietfa.amsl.com>; Mon, 14 Oct 2013 11:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEn2WvNaJyU5 for <6lo@ietfa.amsl.com>; Mon, 14 Oct 2013 11:25:33 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 6440521E809F for <6lo@ietf.org>; Mon, 14 Oct 2013 11:25:29 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.57]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r9EII7Id022034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 14 Oct 2013 21:18:09 +0300
Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.205]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.03.0136.001; Mon, 14 Oct 2013 18:18:06 +0000
From: teemu.savolainen@nokia.com
To: brian@innovationslab.net, 6lo@ietf.org
Thread-Topic: [6lo] Adopting draft-ietf-6lowpan-btle
Thread-Index: AQHOyP5pMMvRsaqQC0W3i8mhUExSVpn0e0FA
Date: Mon, 14 Oct 2013 18:18:06 +0000
Message-ID: <916CE6CF87173740BC8A2CE443096962048AD7A5@008-AM1MPN1-053.mgdnok.nokia.com>
References: <525C2253.8080300@innovationslab.net>
In-Reply-To: <525C2253.8080300@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.163.163.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
Subject: Re: [6lo] Adopting draft-ietf-6lowpan-btle
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discussion of a WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lo>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2013 18:25:56 -0000

Hi Brian, 6lo,

As 6lo participant, but more so as one of the authors of the draft in question, I'm fine for reassigning the draft to 6lo. I can post draft-ietf-6lo-btle-00 as soon as you ask.

I would also like to communicate to this WG that we have multiple active authors on the draft, and hence this work item would come with editors attached:-D

I am (and have been) actually working on this topic in BT SIG, and I believe it is highly likely that we need to touch the draft a bit more than just add the L2CAP channel identifier that IETF requested from BT SIG. However, the changes should be quite straightforward. After the BT SIG has advanced and needed changes are known, a decision needs to be made whether the document should drop back to WG(LC) or not. For now the IETF side of the actual work needs to stay in holding pattern waiting for BT SIG.

Best regards,

Teemu

-----Original Message-----
From: 6lo-bounces@ietf.org [mailto:6lo-bounces@ietf.org] On Behalf Of ext Brian Haberman
Sent: 14. lokakuuta 2013 19.57
To: 6lo@ietf.org
Subject: [6lo] Adopting draft-ietf-6lowpan-btle

All,
     Now that 6lo is an official WG, Ted and I would like to move forward on closing the 6lowpan WG.  However, there is a draft
(draft-ietf-6lowpan-btle) that originated in 6lowpan, but has not been published yet.  It currently sits in IESG Evaluation awaiting feedback from the Bluetooth SIG.

     I would like to ask the 6lo group if anyone would have an objection to me assigning draft-ietf-6lowpan-btle to the 6lo WG.  There are two potential directions such an adoption could take.  The first is that there are no issues with the draft as it relates to the Bluetooth SIG and no work would be needed on the draft.  The other is that issues arise and the IESG needs to send the draft back to the WG for fixes/revisions.

     Can WG participants please respond negatively or positively to the reassignment of draft-ietf-6lowpan-btle to the 6lo WG?  I will take feedback until Oct. 28th, 2013.

Regards,
Brian

v2.23.0 | Report a Bug | By Email