Re: [core] Fwd: New Version Notification for draft-hartke-coap-observe-00
Zach Shelby <zach@sensinode.com> Mon, 28 June 2010 19:36 UTC
Return-Path: <zach@sensinode.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB41B3A696C for <core@core3.amsl.com>; Mon, 28 Jun 2010 12:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.935
X-Spam-Level:
X-Spam-Status: No, score=-2.935 tagged_above=-999 required=5 tests=[AWL=0.664, 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 SZQ52nyz1FIX for <core@core3.amsl.com>; Mon, 28 Jun 2010 12:35:59 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id DFE613A691D for <core@ietf.org>; Mon, 28 Jun 2010 12:35:58 -0700 (PDT)
Received: from [192.168.1.3] (line-4648.dyn.kponet.fi [85.29.64.121]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id o5SJa35h002186 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Jun 2010 22:36:03 +0300
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <AANLkTimLt_VK2dAEbvbqq3x0yjEZEofZF-ekNV5UkdPY@mail.gmail.com>
Date: Mon, 28 Jun 2010 22:36:05 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2396D578-7E93-4108-9207-28D22B0A951A@sensinode.com>
References: <20100622203528.0519A28C0D0@core3.amsl.com> <A9654C45-840C-4682-AA1A-9EAF44D81138@tzi.org> <3A0432F2-457D-47B4-A826-9678E8F5DB57@sensinode.com> <AANLkTimLt_VK2dAEbvbqq3x0yjEZEofZF-ekNV5UkdPY@mail.gmail.com>
To: Klaus Hartke <klaus.hartke@googlemail.com>
X-Mailer: Apple Mail (2.1081)
Cc: core <core@ietf.org>
Subject: Re: [core] Fwd: New Version Notification for draft-hartke-coap-observe-00
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2010 19:36:00 -0000
Klaus, A few agreements in-line. On Jun 24, 2010, at 8:52 PM, Klaus Hartke wrote: > On 23 June 2010 17:24, Zach Shelby <zach@sensinode.com> wrote: >> - Are we sure we need all the requirements here, or are some nice-to-have? > > I believe that all requirements are needed to implement the > architecture. Whether all elements of the architecture are needed, > should be discussed. Good point. > >> For example: "A subscribing client must be able to influence the representation format in which the server supplies the resource state" I would hope this doesn't end up resulting in a bunch of Accept: style headers? Couldn't that be left to the application to offer URLs with different representation formats? I am not convinced this should be a transfer protocol requirement for CoAP. > > I think both options (/sensors/temperature.xml or Accept: > application/xml) are valid ways to satisfy this requirement. If we go > with the Accept header, we need to add a new option to CoAP. I'm in > favour of .xml in the URL. +1 > > There is another requirement related to the representation format, > which is probably more important: "The representation format used > during the lifetime of a subscription must not change." I think this > is a requirement that should be stated somewhere. +1 > >> - SUBSCRIBE, UNSUBSCRIBE, YIELD, BREAK, THROW are abstract concepts at this point, I would think these could be combined quite a bit in realization? What kind of realization do you guys have in mind (just for a sneak preview to see if this is nuts or not). > > Carsten and I are working on concrete message types. The result will > probably not be that different from what we have in coap-00 currently. Yep, this is what I thought. Zach > > Klaus > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core -- Zach Shelby, Chief Nerd, Sensinode Ltd. http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297
- [core] Fwd: New Version Notification for draft-ha… Carsten Bormann
- Re: [core] Fwd: New Version Notification for draf… Zach Shelby
- [core] Can all responses be instant? (Re: Fwd: Ne… Carsten Bormann
- Re: [core] Can all responses be instant? (Re: Fwd… Angelo P. Castellani
- Re: [core] Fwd: New Version Notification for draf… Klaus Hartke
- Re: [core] Fwd: New Version Notification fordraft… Simpson, Robby (GE Energy Services)
- Re: [core] Fwd: New Version Notification fordraft… Carsten Bormann
- Re: [core] Fwd: New Version Notification fordraft… Klaus Hartke
- Re: [core] Fwd: New Version Notification for draf… Zach Shelby
- Re: [core] Fwd: New Version Notification fordraft… Zach Shelby
- Re: [core] Fwd: New Version Notification fordraft… Simpson, Robby (GE Energy Services)
- Re: [core] Can all responses be instant? (Re: Fwd… Zach Shelby