Re: [6lowpan] Use Cases Draft ready as WG document?
"Benjamin A. Rolfe" <ben@blindcreek.com> Wed, 24 September 2008 14:35 UTC
Return-Path: <6lowpan-bounces@ietf.org>
X-Original-To: 6lowpan-archive@megatron.ietf.org
Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3FC028C304; Wed, 24 Sep 2008 07:35:48 -0700 (PDT)
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 AAC4228C304 for <6lowpan@core3.amsl.com>; Wed, 24 Sep 2008 07:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 am9gjzA1j+h2 for <6lowpan@core3.amsl.com>; Wed, 24 Sep 2008 07:35:46 -0700 (PDT)
Received: from wilson.nswebhost.com (wilson.nswebhost.com [65.254.51.10]) by core3.amsl.com (Postfix) with ESMTP id AE65E3A67EE for <6lowpan@ietf.org>; Wed, 24 Sep 2008 07:35:46 -0700 (PDT)
Received: from [64.74.213.174] (helo=RunningDog2) by wilson.nswebhost.com with esmtpa (Exim 4.69) (envelope-from <ben@blindcreek.com>) id 1KiVSL-0005fk-MY for 6lowpan@ietf.org; Wed, 24 Sep 2008 09:35:07 -0500
Message-ID: <004e01c91e52$bc1edaa0$0efaa8c0@RunningDog2>
From: "Benjamin A. Rolfe" <ben@blindcreek.com>
To: 6lowpan@ietf.org
References: <99e1f5cb0809212052x66487ec4rf8f5b628fb3b2c10@mail.gmail.com><C4FD5754.52550%jvasseur@cisco.com><99e1f5cb0809222202s1dd7ca36n7353a1bbda2353c6@mail.gmail.com><2a3692de0809230956k6f5f8386k601a98c5bf1bdd21@mail.gmail.com> <54161.81.184.45.131.1222235810.squirrel@webmail.entel.upc.edu>
Date: Wed, 24 Sep 2008 07:35:01 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - wilson.nswebhost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - blindcreek.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [6lowpan] Use Cases Draft ready as WG document?
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: 6lowpan-bounces@ietf.org
Errors-To: 6lowpan-bounces@ietf.org
Is there a reason that this draft restricts itself to a subset of the currently defined PHYs in 802.15.4? As written, it refers only to the DSSS PHYs. There are currently 2 additional PHYs defined in the standard (802.15.4a-2007), and there are two more amendments nearing completion that define additional PHYs. I don't see any applications in these scenarios that require this restriction. Asset tracking, for example, is a likely application of the UWB PHYs (due to precision ranging, thus location, capability :-). The other PHYs have characteristics useful in some of these scenarios also. Is there a reason for limiting LoWPAN application to specific PHYs or is this just out of date text? Also, a typo in References [3]: "802.15.4-2006, October 2003" of course 15.4-2006 was not published in 2003 :0). 802.15.4-2006 alone is not the current version of the standard (802.15.4a-2007 was approved early 2007). A safer thing is to site "802.15.4-2006 as amended" unless there is some reason to be restrictive (in which case that reason should be explained in the text). -Ben ----- Original Message ----- From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu> To: "Geoff Mulligan" <geoff@mulligan.com>; <6lowpan@ietf.org> Sent: Tuesday, September 23, 2008 10:56 PM Subject: Re: [6lowpan] Use Cases Draft ready as WG document? > Hi all, > > I am also in favor. > > Carles > > > > >> Hi Geoff, >> >> As you mentioned, the Use Cases document has been stable for quite >> some time, and it has sparked a lot of interest. >> I am therefore "in favor of" Working Group adoption. >> >> Greetings, >> Dominik >> >> On Tue, Sep 23, 2008 at 7:02 AM, Geoff Mulligan <geoff@mulligan.com> >> wrote: >>> JP, >>> That was a mistake. I followed it up with a message to the list >>> asking >>> for responses on whether the document should become a WG doc. >>> >>> Please folks on the 6lowpan list respond and let us know if you think >>> the >>> Use Case document is ready to become a WG draft. >>> >>> geoff >>> >>> >>> On Mon, Sep 22, 2008 at 6:08 AM, JP Vasseur <jvasseur@cisco.com> wrote: >>>> >>>> Hi Geoff, >>>> >>>> In another email you wrote: >>>> >>>> " >>>> Jonathan please submit your draft draft-hui-6lowpan-hc-01 >>>> Eunsook please also submit your draft draft-ekim-6lowpan-scenarios-03" >>>> >>>> Is the second ID adopted as a WG (since below you asked for feed-back) >>>> ? >>>> >>>> Thanks. >>>> >>>> JP. >>>> >>>> On 9/22/08 5:52 AM, "Geoff Mulligan" <geoff@mulligan.com> wrote: >>>> >>>> The document draft-ekim-6lowpan-scenarios-03 has been stable for some >>>> time now and this is a chartered item. >>>> >>>> Are you "in favor of" or "opposed to" adopting >>>> draft-ekim-6lowpan-scenarios-03 >>>> (http://www.ietf.org/internet-drafts/draft-ekim-6lowpan-scenarios-03.txt) >>>> as a 6lowpan Working Group Document? >>>> >>>> Thanks, >>>> geoff >>>> >>>> >>>> >>>> ________________________________ >>>> _______________________________________________ >>>> 6lowpan mailing list >>>> 6lowpan@ietf.org >>>> https://www.ietf.org/mailman/listinfo/6lowpan >>> >>> >>> _______________________________________________ >>> 6lowpan mailing list >>> 6lowpan@ietf.org >>> https://www.ietf.org/mailman/listinfo/6lowpan >>> >>> >> _______________________________________________ >> 6lowpan mailing list >> 6lowpan@ietf.org >> https://www.ietf.org/mailman/listinfo/6lowpan >> > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan
- [6lowpan] Use Cases Draft ready as WG document? Geoff Mulligan
- Re: [6lowpan] Use Cases Draft ready as WG documen… JP Vasseur
- Re: [6lowpan] Use Cases Draft ready as WG documen… Geoff Mulligan
- Re: [6lowpan] Use Cases Draft ready as WG documen… Dominik Kaspar
- Re: [6lowpan] Use Cases Draft ready as WG documen… carl williams
- Re: [6lowpan] Use Cases Draft ready as WG documen… Carles Gomez Montenegro
- Re: [6lowpan] Use Cases Draft ready as WG documen… Benjamin A. Rolfe
- Re: [6lowpan] Use Cases Draft ready as WG documen… Kris Pister
- Re: [6lowpan] Use Cases Draft ready as WG documen… Pascal Thubert (pthubert)
- Re: [6lowpan] Use Cases Draft ready as WG documen… Eunsook "Eunah" Kim
- Re: [6lowpan] Use Cases Draft ready as WG documen… Eunsook "Eunah" Kim
- Re: [6lowpan] Use Cases Draft ready as WG documen… Eunsook "Eunah" Kim
- [6lowpan] Use Cases Draft ready as WG document? Behcet Sarikaya
- Re: [6lowpan] Use Cases Draft ready as WG documen… Dessalegn Mequanint