Re: [6lowapp] Proposed charter for 6LoWAPP BOF

Cullen Jennings <fluffy@cisco.com> Sat, 31 October 2009 17:29 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC83B3A6935 for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.325
X-Spam-Level:
X-Spam-Status: No, score=-110.325 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 XetPXEtfr0-S for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:29:36 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 9D4393A67EC for <6lowapp@ietf.org>; Sat, 31 Oct 2009 10:29:35 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgAAH8Q7EqQ/uCWe2dsb2JhbACbUwEBFiQGqCKXeYI3ggIE
X-IronPort-AV: E=Sophos;i="4.44,659,1249257600"; d="scan'208";a="53281355"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2009 17:29:52 +0000
Received: from ams3-vpn-dhcp4750.cisco.com (ams3-vpn-dhcp4750.cisco.com [10.61.82.141]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9VHT0bA024147; Sat, 31 Oct 2009 17:29:51 GMT
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <a9994e940910291225w1064dad4i6799a5b86fa35ea7@mail.gmail.com>
Date: Sat, 31 Oct 2009 11:29:51 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <6661C9D7-9CD3-4D66-8D1F-7F842921C1DA@cisco.com>
References: <B27B00F8-1A4F-4258-86FC-C02E78778E45@cisco.com> <184E130A-881A-4E1F-8408-FB03A7849A82@sensinode.com> <CE5B892A-3699-4CBF-8B6A-588F5A7DE99A@cisco.com> <EB735931-0D15-4017-94F1-3B10A0EC814D@sensinode.com> <843F0B9E-8C62-47A6-AFEC-4BE31D62CDB5@cisco.com> <2AA1E2A3-9EA9-4B94-85BA-834C66826A85@tzi.org> <C93E77B9-349F-451C-BAED-273555EEE5DE@cisco.com> <a9994e940910291111r5523e6eer581313f8fee12cba@mail.gmail.com> <ca722a9e0910291210u3898dda6p4752b3cd5f000ba7@mail.gmail.com> <a9994e940910291225w1064dad4i6799a5b86fa35ea7@mail.gmail.com>
To: arjun.lists@hsc.com
X-Mailer: Apple Mail (2.1076)
Cc: Don Sturek <donsturek@grid2home.com>, 6lowapp@ietf.org
Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2009 17:29:36 -0000

On Oct 29, 2009, at 13:25 , Arjun Roychowdhury wrote:

>
> On Thu, Oct 29, 2009 at 3:10 PM, Lisa Dusseault <lisa.dusseault@gmail.com 
> > wrote:
>
> focused WG charter because this isn't "the charter for low-power IP
> applications protocols" it's merely *a* charter for a subset of those
> things.  We can't boil the ocean in one WG or even come to agreement
> on forming a WG if the scope is too big.  Besides considering that
> other WGs can tackle this larger space, consider that this WG could
> always go on to more complex use cases after solving simple ones.
>
> ARC> I think this comment pretty much summarizes the difference of  
> thought between what I thought 6lowapp vs doing vs what you are  
> describing. The group name itself, "6lowapp" seems to specify it is  
> a group to to specificy low-power IP app protocols, and not a  
> subset. draft-bormann-6lowpan-6lowapp-problem-01 also seems to  
> indicate this group is dealing with the larger set.
>
> So my comment would be if this is not so, then it needs to be  
> explicitly stated, otherwise the natural understanding is 6lowapp is  
> the application protocol group for 6lowpan devices - and what comes  
> out of here, would likely be adopted going forward in deployments,
>
> I can respond to your other comments in more detail, but then again,  
> if the scope is going to be limited, then so be it.
>

This is a good point about the name. When I started talking to people  
about the use cases and requirements for this WG, it became clear to  
me that we might want a name that was different than 6LoAPP. By the  
time I figured this out the name of the BOF had already been submitted  
in the the scheduling for IETF 76 so the BOF name was somewhat locked  
down but we really need to talk about the name of the WG. We would not  
want a name that caused people to daw the wrong conclusions.

So to comment on scope for a second