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

Zach Shelby <zach@sensinode.com> Wed, 04 November 2009 16:01 UTC

Return-Path: <zach@sensinode.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 882733A67E4 for <6lowapp@core3.amsl.com>; Wed, 4 Nov 2009 08:01:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 L3GRZaCK19jj for <6lowapp@core3.amsl.com>; Wed, 4 Nov 2009 08:01:06 -0800 (PST)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 31E183A67D9 for <6lowapp@ietf.org>; Wed, 4 Nov 2009 08:01:05 -0800 (PST)
Received: from [192.168.1.5] (line-5076.dyn.kponet.fi [85.29.66.39]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id nA4G1Hxq010520 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 4 Nov 2009 18:01:17 +0200
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <F78A8E6C-7523-4C62-A2CE-D94ABAA26C2B@archrock.com>
Date: Wed, 4 Nov 2009 18:01:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD8D8E47-60DF-4BFB-B139-B0EB5DC381EB@sensinode.com>
References: <OF164C5409.51429B82-ONC1257663.007E96BE-C1257663.008109C1@schneider-electric.com> <85BCBB91-0C20-4354-9EA1-4F055E4D186A@sensinode.com> <20091104143600.GA8772@elstar.local> <F78A8E6C-7523-4C62-A2CE-D94ABAA26C2B@archrock.com>
To: Jonathan Hui <jhui@archrock.com>
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: Wed, 04 Nov 2009 16:01:07 -0000

On Nov 4, 2009, at 17:54 , Jonathan Hui wrote:

> On Nov 4, 2009, at 6:36 AM, Juergen Schoenwaelder wrote:

>>
>>
>> In my experience, the IETF is working best by breaking things down in
>> manageable pieces and assigning priorities to them. I believe this
>> needs to be done sooner rather than later here as well. Building a
>> long wishlist of things CoAP is expected to nicely interface with
>> seems like moving into the wrong direction (except you take a rather
>> liberal interpretation of "interfacing nicely" - the hard stuff is
>> often in the detailed semantics and their mismatches).
>
>
> Exactly!  I have been advocating this and I'm glad others are  
> bumping into the same problem.  If we want to make quick forward  
> progress, we need to explicitly call out target applications (and  
> probably use cases) in the charter.
>
> SE 2 and Building Management applications seems like a good starting  
> list and I would be satisfied if we only focused on those two for  
> the time being.
>

+1!

We do need to specify which protocol we need to assume we can proxy  
with. I am satisfied with HTTP REST as the charter states now as a  
starting place as it covers those applications well. Others can come  
in the future as needed. We should though specifically list which  
standards organizations we will work with, and OASIS (e.g. oBIX, DPWS)  
is important there in addition to SE2 related organizations.

Zach

> --
> Jonathan Hui
>

-- 
http://www.sensinode.com
http://zachshelby.org - My blog “On the Internet of Things”
Mobile: +358 40 7796297

Zach Shelby
Head of Research
Sensinode Ltd.
Kidekuja 2
88610 Vuokatti, FINLAND

This e-mail and all attached material are confidential and may contain  
legally privileged information. If you are not the intended recipient,  
please contact the sender and delete the e-mail from your system  
without producing, distributing or retaining copies thereof.