Re: [core] COMI: Basic Operations

Michel Veillette <Michel.Veillette@trilliantinc.com> Tue, 21 June 2016 18:16 UTC

Return-Path: <Michel.Veillette@trilliantinc.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 CD26612DBFD for <core@ietfa.amsl.com>; Tue, 21 Jun 2016 11:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.onmicrosoft.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 WrUh8Zjwx5Rn for <core@ietfa.amsl.com>; Tue, 21 Jun 2016 11:16:47 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0736.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:736]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A45B312DBF7 for <core@ietf.org>; Tue, 21 Jun 2016 11:16:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-trilliantinc-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yY5ODUTjn8jJao42D7m6n6hKsnzmJ/9tMdrQxcU7SEM=; b=ON9y3aiZKxD6h8p8/5wX6/PjMaa9C4MyRqyjPrUby2+3rqxkkioxnY6/Km5l5fb8h9Lk+flmzT/svBL5XfY3CXLA1+meB8HEoy7awHa/9Evh9XK8crzWCxQhF17fMQS1sVTq3LDGqFEjqluGqyeXgKqFS8HrncW6okqxXM2iahg=
Received: from BLUPR06MB1763.namprd06.prod.outlook.com (10.162.224.149) by BLUPR06MB1761.namprd06.prod.outlook.com (10.162.224.147) with Microsoft SMTP Server (TLS) id 15.1.523.12; Tue, 21 Jun 2016 18:16:26 +0000
Received: from BLUPR06MB1763.namprd06.prod.outlook.com ([10.162.224.149]) by BLUPR06MB1763.namprd06.prod.outlook.com ([10.162.224.149]) with mapi id 15.01.0523.015; Tue, 21 Jun 2016 18:16:26 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: "Turner, Randy" <Randy.Turner@landisgyr.com>, "core@ietf.org WG" <core@ietf.org>
Thread-Topic: [core] COMI: Basic Operations
Thread-Index: AQHRy5OrVYz50ufs9ESY69BFKOWJoJ/0J15wgAAMXQCAAAYdQA==
Date: Tue, 21 Jun 2016 18:16:26 +0000
Message-ID: <BLUPR06MB1763290C58E3756B21325BC9FE2B0@BLUPR06MB1763.namprd06.prod.outlook.com>
References: <5768F53B.6010109@gmx.net> <BLUPR06MB176396014689D95A8B5F58D3FE2B0@BLUPR06MB1763.namprd06.prod.outlook.com> <DB5PR01MB1815C7D3FF8BC77A66AC5A58802B0@DB5PR01MB1815.eurprd01.prod.exchangelabs.com>
In-Reply-To: <DB5PR01MB1815C7D3FF8BC77A66AC5A58802B0@DB5PR01MB1815.eurprd01.prod.exchangelabs.com>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliantinc.com;
x-originating-ip: [207.96.192.122]
x-ms-office365-filtering-correlation-id: 6a11d153-e451-4b5c-7b94-08d39a0028fb
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1761; 6:xOFasqutPaG4qLR74PTxJvO2jte4NZG5QdcVQ77F67X6PtgJQixybtOIfM64wOhh1HPozHsZ4jmUJ6LP55BFz1YjmKtJmrg/buMwrnmeBJtNhRgVYu8HFjr3x7ToHVqsaV/57oQy/MC152hT0yP5Zx6McceG+xmXE6kYU6+XLA0cE4bQIjpP9NddrYNebf8FPYCAkLnM4+chHedBy+ZqVkvoNZRhefKSH6H5mOPirATY+4lOnyIuKicN9yktzp/4UmQylbBlcmaB5ONFlEEZEZh4pDU6Ehhzdc8zke7nIzI=; 5:Ni+8L05yg+6F2O6Nw6T3Q1I1mvXkEfFt6KXkUDA3p57gp7DWqCycPoQh+RGnVMPPi5eotZuPKvBUgLE2WFJLnZdzwqcIyjwFJsjHhA2sYyYlIZ8Xn5zzoD2fvcQzsuHxoSRZ5CS9J62TDVt7emWMaA==; 24:0+O55PrnzNw3FmWcSQQF4ZWfUbmkgVOwwIk0Fka9GYR96vakOEZefSVe6r5BpN9Md3oGz64HDgnEIhavFs1CMucJ+0QfPbXJnGZqdEI1IwM=; 7:tUx3xNrjxWLEhWRcp7yHsVhMwl4nAPZ+y3StqcVvGHkQQVcK97tUPST0ModqnnNdvQPWyKkGtSXOlbTmKdf9C9wydQrBWEOmloHJD6foZoKHU/unsn1r4Ws3+gsQ3ZtH6wVvKTjwVFrM6mUnvW69JKrtgXjYlvvat5ZNLJqWCcsKJxG2NpGHRVyaNCYXfUq4hvXKqJOxYGtC45g0m83m29ovaYf0QLXPZXOg0F4iHFibqWGiIcyFNK5y/42tsUdt
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR06MB1761;
x-microsoft-antispam-prvs: <BLUPR06MB176129FF3535433C00189396FE2B0@BLUPR06MB1761.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(190756311086443)(158342451672863)(144836121648609)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:BLUPR06MB1761; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB1761;
x-forefront-prvs: 098076C36C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(13464003)(189002)(199003)(377454003)(586003)(77096005)(102836003)(790700001)(3846002)(6116002)(19300405004)(81156014)(10400500002)(33656002)(19625215002)(99286002)(5890100001)(551934003)(8666005)(19580405001)(122556002)(54356999)(81166006)(101416001)(7846002)(15975445007)(76176999)(5003600100003)(7696003)(8676002)(9686002)(8936002)(68736007)(50986999)(2906002)(3280700002)(2950100001)(11100500001)(3660700001)(7906002)(87936001)(2900100001)(74316001)(19580395003)(97736004)(92566002)(76576001)(5001770100001)(19617315012)(106116001)(106356001)(107886002)(105586002)(5002640100001)(66066001)(7736002)(189998001)(16236675004)(86362001)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR06MB1761; H:BLUPR06MB1763.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: trilliantinc.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BLUPR06MB1763290C58E3756B21325BC9FE2B0BLUPR06MB1763namp_"
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2016 18:16:26.0172 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1761
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/GEFJB1X26LozQUqDA5viN6lok8I>
Subject: Re: [core] COMI: Basic Operations
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Jun 2016 18:16:51 -0000

Hi Andy

About your first question, data node instances can be deleted using the iPATCH.
Alternatively, the entire datastore can be replaced using the PUT method.

About "What about OBSERVE semantics"
As mentioned at http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.6.8, the "observe" CoAP option is supported to observe data node instance.

Regards,
Michel

From: Turner, Randy [mailto:Randy.Turner@landisgyr.com]
Sent: Tuesday, June 21, 2016 1:51 PM
To: Michel Veillette <Michel.Veillette@trilliantinc.com>; core@ietf.org WG <core@ietf.org>
Subject: RE: [core] COMI: Basic Operations

Are we allowed to ‘DELETE’ object instances ?

What about OBSERVE semantics ?

R.

From: core [mailto:core-bounces@ietf.org] On Behalf Of Michel Veillette
Sent: Tuesday, June 21, 2016 1:13 PM
To: Hannes Tschofenig; core@ietf.org<mailto:core@ietf.org> WG
Subject: Re: [core] COMI: Basic Operations


Hi Hannes



Good timing.

On the agenda of our weekly call tomorrow, we have an item to review the proposed function set.

I have included in attachment the invite for this meeting in case you want to participate.

Following is a list of the CoAP methods, associated use cases, message content summary and examples.

For the up to date version of the drafts, see http://core-wg.github.io/yang-cbor/



•         The GET method

o   Use to retrieve the content of a datastore

o   Can be used to implement a backup/restore use case

o   The request contains the URI of the targeted datastore (/c/r = running configuration, /c = current data & running configuration)

o   The response contains an array of pairs of (delta SID, associated values)

o   Example: http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.5.1



•         The PUT method

o   Use to load content of a datastore

o   Can be used to implement the provisioning, commissioning and restore use cases

o   The request contains the URI of the targeted datastore (/c/r = running configuration) and an array of pairs of (delta SID, associated value)

o   Example: http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.5.3



•         The FETCH method

o   Use to retrieve a subset of a datastore

o   Can be used to implement ad-hoc queries, recurrent data retrieval (e.g state and statistics)

o   The request contains the URI of the targeted datastore (/c/r = running configuration) and a list of instance-identifier

o   The response contains an array of associated values (value, CBOR undefined or CBOR default)

o   Examples: http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.5.2



•         The iPATCH method

o   Use to update a subset of a datastore

o   Can be used to update the configuration of a device using a atomic transaction

o   The request contains the URI of the targeted datastore (/c/r = running configuration) and an array of pairs of (instance-identifier, associated value)

o   Example: http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.5.4

o   A candidate datasotre (/c/c) and the "commit" RPC can be used to implement a schedules and/or confirmed update on one or multiple devices.
http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.appendix.A



•         The POST method

o   Use to execute a RPC or an Action

o   The request contains the URI of the targeted datastore (/c/r = running configuration) and an array with up to two entry, the RPC identification (SID) follow by the optional input

o   The request contains contain the optional output

o   Example: http://core-wg.github.io/yang-cbor/draft-veillette-core-cool-latest.html#rfc.section.5.5



Regards,

Michel



-----Original Message-----
From: core [mailto:core-bounces@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Tuesday, June 21, 2016 4:05 AM
To: core@ietf.org<mailto:core@ietf.org> WG <core@ietf.org<mailto:core@ietf.org>>
Subject: [core] COMI: Basic Operations



Hi COMI friends,



since you have for sure progressed your work quite a bit since we last meet in BA I am wondering whether you have a few simple message exchange examples using COMI for me.



For example, think about a typical IoT device lifecycle where the device starts and registers its resources with a server in the cloud, it then periodically sends sensor readings (to that server), and gets requests from a server as well.



How would this look like in COMI?



Ciao

Hannes