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

Cullen Jennings <fluffy@cisco.com> Sat, 31 October 2009 17:30 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 8C8263A692C for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.337
X-Spam-Level:
X-Spam-Status: No, score=-110.337 tagged_above=-999 required=5 tests=[AWL=0.262, 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 YxTRhmomZI8F for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:30:13 -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 4D4803A6928 for <6lowapp@ietf.org>; Sat, 31 Oct 2009 10:30:13 -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: AjgAAKoR7EqQ/uCWe2dsb2JhbACbUwEBFiQGqBaXeIQ5BA
X-IronPort-AV: E=Sophos;i="4.44,659,1249257600"; d="scan'208";a="53281374"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2009 17:30:17 +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 n9VHT0bC024147; Sat, 31 Oct 2009 17:30:16 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: <A4C590B945EF374AB02BB6A2EAA4485808B4C76271@EXMBX01.apps4rent.net>
Date: Sat, 31 Oct 2009 11:30:16 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <6C14D98B-4B4D-44B8-B8A5-1BEA5A8F443C@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> <A4C590B945EF374AB02BB6A2EAA4485808B4C76271@EXMBX01.apps4rent.net>
To: Don Sturek <d.sturek@att.net>
X-Mailer: Apple Mail (2.1076)
Cc: "6lowapp@ietf.org" <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:30:14 -0000

On Oct 29, 2009, at 8:37 , Don Sturek wrote:

> Hi Cullen,
>
> Overall, the proposed charter looks interesting.
>
> On the Commissioning methods, I think making the "Duckling" mode  
> mandatory as indicated in the text below should not be decided in  
> the charter.

Fair enough. Let me start a separate thread on this.

>  Unless this commissioning method has undergone some form of  
> security review, it could well be something we (at least in Smart  
> Energy) cannot use.

Agree, but even worse. The IETF is not going to publish any of this as  
an RFC until it has had reasonable security review so I certainly  
don't want anything that would be a significant innovation in security  
or is broken from a security point of view.

> It would be a shame to waste code space for something like this.
>
> While we (again Smart Energy) are looking at a RESTfull HTTP  
> architecture, it would be good to point out that this is only one  
> option.  It would be nice to see if other popular communication  
> solutions can work as well.

Yep - several other people have told me this too. What other popular  
protocols should we consider?

>
> One more thng:   The discussion below indicates two level of  
> communication:   PEPs and CoAps.   I would hope we could avoid  
> this.  It would be nice to address and communicate with CoAp devices  
> as you would with any other device on the internet whether a PEP was  
> present or not.  I would not want to have the group focused on this  
> type of gateway approach.

Agree - I was trying to make it clear any computer on the internet  
could talk CoAp directly to Device but failed to express that. Could  
you suggest some text to make that clear?

>
> Overall though this was a good start for the charter.
>
> Don
>