IETF Logo Mail Archive

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

Klaus Hartke <hartke@tzi.org> Sat, 21 April 2012 02:52 UTC

Return-Path: <hartke@tzi.org>
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 DBE1D21E8019 for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 19:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level:
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 OpUdSJFKYJPm for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 19:52:57 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 2794221E8013 for <core@ietf.org>; Fri, 20 Apr 2012 19:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3L2qlWj005393 for <core@ietf.org>; Sat, 21 Apr 2012 04:52:47 +0200 (CEST)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0BDAD282 for <core@ietf.org>; Sat, 21 Apr 2012 04:52:46 +0200 (CEST)
Received: by dady13 with SMTP id y13so18395442dad.27 for <core@ietf.org>; Fri, 20 Apr 2012 19:52:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.224.228 with SMTP id rf4mr17432315pbc.22.1334976764756; Fri, 20 Apr 2012 19:52:44 -0700 (PDT)
Received: by 10.68.23.37 with HTTP; Fri, 20 Apr 2012 19:52:44 -0700 (PDT)
In-Reply-To: <FFAC5E76-C45D-4331-8B44-14C5CB67B485@sensinode.com>
References: <CAB6izERzSzRy53K18CkEJ_KUH_saJcXjsyYR8vSy4_8Pej7Q4g@mail.gmail.com> <FFAC5E76-C45D-4331-8B44-14C5CB67B485@sensinode.com>
Date: Sat, 21 Apr 2012 04:52:44 +0200
Message-ID: <CAB6izEShTX9USqfQ_R2sPO_UrjhQOD0Yo5WwWryyatpweL0-+g@mail.gmail.com>
From: Klaus Hartke <hartke@tzi.org>
To: core@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
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 02:52:58 -0000

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?


Klaus

v2.23.0 | Report a Bug | By Email