Re: [6lowapp] BOF proposal: update

Sam Roberts <vieuxtech@gmail.com> Mon, 28 September 2009 19:27 UTC

Return-Path: <vieuxtech@gmail.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 966173A691C for <6lowapp@core3.amsl.com>; Mon, 28 Sep 2009 12:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 nEQIP4kDxP8Z for <6lowapp@core3.amsl.com>; Mon, 28 Sep 2009 12:27:31 -0700 (PDT)
Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by core3.amsl.com (Postfix) with ESMTP id DC8E43A67B3 for <6lowapp@ietf.org>; Mon, 28 Sep 2009 12:27:31 -0700 (PDT)
Received: by pzk35 with SMTP id 35so4272283pzk.29 for <6lowapp@ietf.org>; Mon, 28 Sep 2009 12:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=dRm0ao46GlQd2vyzTImnD6vY88BDnbpbK6L3hqs+Q0E=; b=mBeo50v8hhDJEaZctY1OzJ8pzzBNWiydCy2PGi9gDVDilawVrAbyP3ukpqIt2SUONu 8LCeehyvQKI0piDBGzMbPAobvxbCcOnwbCeH4CVxhJVLP70p7K19g7agzxhGjzLt0ujh PslhYT06sy1lWTMDJjBlwSSxrFvAOWE/DgnJU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=G9XwqfgHrCgAgYsqizHN92pcy0E3ju39quyhcd5SheUnkQNIFbZ7+65O+Y97NMejIm jXZrLmD5784q6kr07uFsxZ4i7CCkOfYzPBJALLWIFfYzLlN1RQRtTuOf7udCk1ySV4i3 8y/T2INcYJzn7+3U11KHVyr2gfOmrQVGPJnL0=
MIME-Version: 1.0
Received: by 10.143.154.14 with SMTP id g14mr282633wfo.266.1254166128536; Mon, 28 Sep 2009 12:28:48 -0700 (PDT)
In-Reply-To: <7b191a110909281104k10f3869bg534bbfaef0bf8322@mail.gmail.com>
References: <D9BF98E0-72D4-49BA-9542-3264EE96F8E8@tzi.org> <334E7C18-7C0B-4BC3-ADE9-9D30FBA0F7D7@tzi.org> <7b191a110909281104k10f3869bg534bbfaef0bf8322@mail.gmail.com>
Date: Mon, 28 Sep 2009 12:28:48 -0700
Message-ID: <17eac67c0909281228m339084c9u4e27decdd2271af8@mail.gmail.com>
From: Sam Roberts <vieuxtech@gmail.com>
To: 6lowapp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [6lowapp] BOF proposal: update
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: Mon, 28 Sep 2009 19:27:32 -0000

On Mon, Sep 28, 2009 at 11:04 AM, Brian Frank <brian.tridium@gmail.com> wrote:
> Couple of my thoughts to echo what some others have said:
> - I believe the application protocol should be format agnostic.  I suspect
> that it will be difficult to achieve consensus on data formats. I am not
> sure how that might limit the scope of 6lowapp, but certainly I hope that a
> debate on formats doesn't derail the transport protocol itself

I share the hope that format discussions won't bog things down.

Perhaps I misunderstand what you mean by "format agnostic", won't
non-specification of such an important aspect prevent independantly
developed implementations of the protocol from interoperating?

> - I personally believe that naming should be based on URIs; however it seems
> as this is already presumed as a requirement?

Have I missed discussion of this, or has rehosting the zigbee
application support layer and cluster library on top of IPv6 over
802.15.4 already been discussed and/or discarded as a possibility?

A profile supporting RESTful URI based request/response could exit at
a zigbee endpoint.

Cheers,
Sam