IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Fri, 20 April 2012 15:12 UTC

Return-Path: <cabo@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 9990821F8797 for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 08:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.021
X-Spam-Level:
X-Spam-Status: No, score=-106.021 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 C2R0TxzuvIrA for <core@ietfa.amsl.com>; Fri, 20 Apr 2012 08:12:29 -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 84B9D21F877A for <core@ietf.org>; Fri, 20 Apr 2012 08:12:28 -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 q3KFCJIE028567 for <core@ietf.org>; Fri, 20 Apr 2012 17:12:19 +0200 (CEST)
Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 107401CB; Fri, 20 Apr 2012 17:12:19 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAB6izERzSzRy53K18CkEJ_KUH_saJcXjsyYR8vSy4_8Pej7Q4g@mail.gmail.com>
Date: Fri, 20 Apr 2012 17:12:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC36FC0B-AB83-491F-AA47-7A33AB6AF8C6@tzi.org>
References: <CAB6izERzSzRy53K18CkEJ_KUH_saJcXjsyYR8vSy4_8Pej7Q4g@mail.gmail.com>
To: Klaus Hartke <hartke@tzi.org>
X-Mailer: Apple Mail (2.1257)
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: Fri, 20 Apr 2012 15:12:29 -0000

On Apr 17, 2012, at 02:14, Klaus Hartke wrote:

> Do we really need the "obs" link attribute?

Today?  No.
A client can always simply send the Observe option and see what the server does.
(Well, maybe obs also is a hint what *kind* of resource this is.)

In the future, we might have a number of extensions like (or unlike) -observe that a server can offer.  I think it is generally better to clarify the presence or absence of an extension at the discovery stage than requiring all those extension options (the ones that would make sense for the client) to be sent with the request.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email