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 36FEF3A692B for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.298
X-Spam-Level:
X-Spam-Status: No, score=-110.298 tagged_above=-999 required=5 tests=[AWL=0.301, 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 9M7Um446nBmF for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:29:11 -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 EDDA53A67EC for <6lowapp@ietf.org>; Sat, 31 Oct 2009 10:29:10 -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/uCWe2dsb2JhbACbUwEBFiQGqCKXeYQ5BA
X-IronPort-AV: E=Sophos;i="4.44,659,1249257600"; d="scan'208";a="53281349"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2009 17:29:29 +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 n9VHT0b8024147; Sat, 31 Oct 2009 17:29:28 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: <4AE9A4C8.4030402@tkk.fi>
Date: Sat, 31 Oct 2009 11:29:27 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <241682EE-2552-412D-975E-ED533FDED68D@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> <25465_1256798603_ZZ0KS9006DTK09O4.00_C93E77B9-349F-451C-BAED-273555EEE5DE@cisco.com> <4AE9A4C8.4030402@tkk.fi>
To: Jukka Manner <jukka.manner@tkk.fi>
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:12 -0000

On Oct 29, 2009, at 8:20 , Jukka Manner wrote:

> 1. This seems to indicate that 6lowapp will not be tied to any  
> existing work, it will work on its own goals, but in collaboration  
> with others (which is somewhat open as what it means). I would have  
> expected that 6lowapp would specifically look at existing work in  
> related WGs and see how build on top of that.

My mistake - I did not mean to imply that it was not layered on top of  
closely related existing work. I think most people assumed that this  
would run on top of a LoPAN but it seemed they also wanted it to be  
able to run on top of a other things including a normal IP LAN and  
WAN. Clearly this is all about same use cases as 6LoPAN and ties  
closing with 6LoPAN and ROLL as well as work going on at many other  
SDOs. However, I'm not sure what needs to be said. Are WG drafts with  
use case / requirements from other WG that we should be referencing?  
Give me ideas on what things you were thinking here. Clearly the IESG  
would not be keen on chartering a new WG to do something another WG  
was already charted to do - repeating work in two places seldom ends  
well :-) Can you suggest some specific text for the charter that you  
think would have fairly wide consent and captures what you are looking  
for here?