Re: [core] COMI: Basic Operations

["Turner, Randy" <[e-mail]>]

Are we allowed to ‘DELETE’ object instances ?

What about OBSERVE semantics ?

R.

From: core [mailto:[e-mail]] On Behalf Of Michel Veillette
Sent: Tuesday, June 21, 2016 1:13 PM
To: Hannes Tschofenig; [e-mail] 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:[e-mail]] On Behalf Of Hannes Tschofenig
Sent: Tuesday, June 21, 2016 4:05 AM
To: [e-mail]<mailto:[e-mail]> WG <[e-mail]<mailto:[e-mail]>>
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