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

Michael Koster <michaeljohnkoster@gmail.com> Tue, 09 July 2019 23:34 UTC

Return-Path: <michaeljohnkoster@gmail.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 3AC15120298 for <core@ietfa.amsl.com>; Tue, 9 Jul 2019 16:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SYnJGuqpes3Q for <core@ietfa.amsl.com>; Tue, 9 Jul 2019 16:34:38 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CCF31202D5 for <core@ietf.org>; Tue, 9 Jul 2019 16:34:36 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id g15so231507pgi.4 for <core@ietf.org>; Tue, 09 Jul 2019 16:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0hR6subQWHkwZPM52tDKhSAv9rf4d2inIus/r9lLdl4=; b=FtB7RlW68uCI5XJ9ZtfYzz+xLV8rSo61NY5TzU2NJ8dAIygWBg8jK6y/5On0Oejj/L XKtd8UW/YVPP9/IEsHyroPhCJXxZe+AIiThwQPJw9K7dtxqUMsDMIGfzdPl5hjsEuXAq qFUQhZzNbvp+m4GQ6TPz/D7lXMGQ+3LwE+dFEy6hT4HeB/P62ZBHZSrH9S+AmOsAEdBh xpwouNHdGfeXn6+uUrs9Ti7KPyCISBPS0YZMwtTlRVPc1ffnlgjfoyzWG4CdS2czQxJ2 Ne6h9P0XGP0zPinNsuEHwlH6KMVhxCB6LppxEEZ7ONnHhTdtpbuVre72q8M1ElKleCVm Esdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0hR6subQWHkwZPM52tDKhSAv9rf4d2inIus/r9lLdl4=; b=rvv/fpnGO01MX/JrTFoKV77eOSsnHsozeNiX9Ilm4o6pJFZacM345RV8T2iQBYQOvX Msp3UJdy1CZlgm5TVCHoRNXxXjPxYXAgOALAw9d5tAjWtixFe08fbNE6sLCEAScHYhnN U9mkDWTfLhbNbynXwLfKedkCi5rdJ1r1OTDZOZUws8I/fOW2yWUrPSWP1MwVAKRGGF4F gMGggqNm9iCydUqOr9hCOYC8ezxOalVbYJLgcuOlcgOkMY18zjo9IHXrQhO0utwCOQvh 5DgoxPumz8XGY5rimjOi3HTaMAijSOZ8hepqatNOgLgZGjjSfgmY/ZuxFdisrHl9rZ5S NrBg==
X-Gm-Message-State: APjAAAX9rWNixO73drPEsLDL3U8c6MQ0PvM3etwlixZyakGO/bBS0/i6 jhPTIKtVIXXJa91QjnQVsIY=
X-Google-Smtp-Source: APXvYqytZk1m+pYPLjGx1xlzdrVgIpy1VHoRROkw3588hSS9+Olg5Gjqrz9MpzfTz62vdZGQmOG6sg==
X-Received: by 2002:a63:9245:: with SMTP id s5mr18755836pgn.123.1562715275483; Tue, 09 Jul 2019 16:34:35 -0700 (PDT)
Received: from [172.16.0.7] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id s22sm177933pfh.107.2019.07.09.16.34.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jul 2019 16:34:34 -0700 (PDT)
From: Michael Koster <michaeljohnkoster@gmail.com>
Message-Id: <E74FBEFC-D7CA-48E4-BB71-6031BAB830FA@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5E3BFB4F-D570-4EE9-AF70-8FBD2096E915"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 09 Jul 2019 16:34:31 -0700
In-Reply-To: <CAAzbHvYGVtNiw5taGMaVVRe4RuN9s2y4Y6RkJxR06Nk=w3CiTQ@mail.gmail.com>
Cc: Michael Koster <michael.koster=40smartthings.com@dmarc.ietf.org>, "t2trg@irtf.org" <t2trg@irtf.org>, core <core@ietf.org>
To: Klaus Hartke <hartke@projectcool.de>
References: <166B0435-8C96-4B83-98CB-A1D6F0838335@smartthings.com> <CAAzbHvYGVtNiw5taGMaVVRe4RuN9s2y4Y6RkJxR06Nk=w3CiTQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/VOM2KC7lGdnUMTUNFYyC3dD-kyc>
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: Tue, 09 Jul 2019 23:34:44 -0000

Thank you, Klaus.

> On Jul 9, 2019, at 3:24 PM, Klaus Hartke <hartke@projectcool.de> wrote:
> 
> When observing a resource with a rather large representation, it might
> often make more sense to observe a projection of that resource. That
> is, to observe a resource X whose state depends on the state of
> another resource Y.

This is already the intention with providing the alternate URI through the use of the query parameter. It is a different resource which is a projection of the state of the base resource.

klaus> * The state of X is a list of the last 10 additions/removals to that list.

Or perhaps the last one addition or removal...

What we are doing is not that different.

Best regards,

Michael