[core] Using CoMI to change resource attributes

Christian Amsüss <c.amsuess@energyharvesting.at> Wed, 03 January 2018 09:43 UTC

Return-Path: <c.amsuess@energyharvesting.at>
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 F1F3712D86E for <core@ietfa.amsl.com>; Wed, 3 Jan 2018 01:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham 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 62iv1fNjfr4I for <core@ietfa.amsl.com>; Wed, 3 Jan 2018 01:43:36 -0800 (PST)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9368D12D86D for <core@ietf.org>; Wed, 3 Jan 2018 01:43:36 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 5D02448F05 for <core@ietf.org>; Wed, 3 Jan 2018 10:43:32 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [10.13.13.231]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id A44D939 for <core@ietf.org>; Wed, 3 Jan 2018 10:43:31 +0100 (CET)
Received: from hephaistos.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 7824738 for <core@ietf.org>; Wed, 3 Jan 2018 10:43:31 +0100 (CET)
Received: (nullmailer pid 30514 invoked by uid 1000); Wed, 03 Jan 2018 09:43:30 -0000
Date: Wed, 03 Jan 2018 10:43:30 +0100
From: Christian Amsüss <c.amsuess@energyharvesting.at>
To: core@ietf.org
Message-ID: <20180103094329.GA25309@hephaistos>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg"
Content-Disposition: inline
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/vwEtw_BeetJewoLyVFvG82Q4MiU>
Subject: [core] Using CoMI to change resource attributes
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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, 03 Jan 2018 09:43:38 -0000

Hello people in the CoMI area,

in one open issue[1] of the RD-DNS-SD document, we could come to the
point that as .well-known/core is typically a read-only resource,
authorized clients could want to change attributes of some advertised
resources, in particular the title= or ins= attribute values.

How that is done will be out of scope for RD-DNS-SD.

It would, however, be nice if other current WG documents can provide a
means to do that which could be referenced in an non-normative way. My
impression is that the documents around CoMI could be used to do that,
but I have bitter little overview of that area. Can the documents be
pieced together in such a way that a client could do something like

* Find out that a device is CoMI managed,
* find which attribute governs the value of a particular resource's
  "ins=" attribute, and
* assign a new value to that?

and if yes, where do I need to look?

Thanks
Christian

[1]: https://github.com/core-wg/rd-dns-sd/issues/2

-- 
I shouldn't have written all those tank programs.
  -- Kevin Flynn