IETF Logo Mail Archive

Re: [core] [T2TRG] OCF Observe on special interfaces, design question, RFC requirements?

Carsten Bormann <cabo@tzi.org> Wed, 10 July 2019 06:05 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 460B41200FD for <core@ietfa.amsl.com>; Tue, 9 Jul 2019 23:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFs9fIECRTDB for <core@ietfa.amsl.com>; Tue, 9 Jul 2019 23:05:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 862B61200DB for <core@ietf.org>; Tue, 9 Jul 2019 23:05:38 -0700 (PDT)
Received: from [192.168.217.110] (p548DC676.dip0.t-ipconnect.de [84.141.198.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 45k7cS4Wbzz14XR; Wed, 10 Jul 2019 07:52:08 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAAzbHvYGVtNiw5taGMaVVRe4RuN9s2y4Y6RkJxR06Nk=w3CiTQ@mail.gmail.com>
Date: Wed, 10 Jul 2019 07:52:08 +0200
Cc: Michael Koster <michael.koster=40smartthings.com@dmarc.ietf.org>, "t2trg@irtf.org" <t2trg@irtf.org>, core <core@ietf.org>
X-Mao-Original-Outgoing-Id: 584430725.7802449-540d7a4c94d69cfc6e4be692de538e51
Content-Transfer-Encoding: quoted-printable
Message-Id: <683B27F7-F738-4B80-A27E-B65B75EFCDA6@tzi.org>
References: <166B0435-8C96-4B83-98CB-A1D6F0838335@smartthings.com> <CAAzbHvYGVtNiw5taGMaVVRe4RuN9s2y4Y6RkJxR06Nk=w3CiTQ@mail.gmail.com>
To: Klaus Hartke <hartke@projectcool.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/cHT3Vjkz4V9HKknWMvYIxno3yBI>
Subject: Re: [core] [T2TRG] OCF Observe on special interfaces, design question, RFC requirements?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 10 Jul 2019 06:05:41 -0000

There is, of course, nothing wrong with observing a resource that is the “last change” of another resource.  This just doesn’t give you a reliable sequence of all changes; that requires something like the “Series Transfer Pattern”, https://tools.ietf.org/html/draft-bormann-t2trg-stp

Grüße, Carsten

v2.23.0 | Report a Bug | By Email