IETF Logo Mail Archive

Re: [core] draft-ietf-core-observe-05 - "obs"

Zach Shelby <zach@sensinode.com> Sat, 21 April 2012 06:27 UTC

Return-Path: <zach@sensinode.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB5C121F85A5 for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 23:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zG0caLwefbeK for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 23:27:46 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 8F80B21F85A4 for <core@ietf.org>; Fri, 20 Apr 2012 23:27:45 -0700 (PDT)
Received: from [192.168.1.102] (87-93-1-88.bb.dnainternet.fi [87.93.1.88]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q3L6Rfdf016368; Sat, 21 Apr 2012 09:27:42 +0300
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <CAB6izEShTX9USqfQ_R2sPO_UrjhQOD0Yo5WwWryyatpweL0-+g@mail.gmail.com>
Date: Sat, 21 Apr 2012 09:27:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C8DF5A0-F915-48F1-B5CB-C20F5851AC2C@sensinode.com>
References: <CAB6izERzSzRy53K18CkEJ_KUH_saJcXjsyYR8vSy4_8Pej7Q4g@mail.gmail.com> <FFAC5E76-C45D-4331-8B44-14C5CB67B485@sensinode.com> <CAB6izEShTX9USqfQ_R2sPO_UrjhQOD0Yo5WwWryyatpweL0-+g@mail.gmail.com>
To: Klaus Hartke <hartke@tzi.org>
X-Mailer: Apple Mail (2.1084)
Cc: core@ietf.org
Subject: Re: [core] draft-ietf-core-observe-05 - "obs"
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 21 Apr 2012 06:27:51 -0000

On Apr 21, 2012, at 5:52 AM, Klaus Hartke wrote:

> Zach Shelby <zach@sensinode.com> wrote:
>> The behavior of dealing with a polling-only resource vs. an observable resource is pretty different, and an observable resource might result in a different graphical representation to the user which needs to be known already during discovery.
> 
> That's an aspect I hadn't considered so far and find very useful.
> 
> Maybe we could expand section 7 of -observe a bit to give advice in
> this direction?

Sure. A couple sentences on where an indication of 'obs' can be useful is a good addition. 

Zach

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297

v2.23.0 | Report a Bug | By Email