On Fri, Jun 26, 2015 at 3:32 PM, Thomas Watteyne <[email protected] > wrote:
> In the 6TiSCH context, CoMI can be used to manage a TSCH schedule, which > involves adding/removing cells (atomic layer 2 resources). > > Cells are represented in the 6top YANG model as a list called "CellList" ( > https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface-03#section-4.1). > The way CoMI is written now (draft-vanderstok-core-comi-06), one CoMI > request is needed for each operation. That is, if I want to schedule 10 > cells between nodes A and B, I will need 10 PUT requests to node A, and 10 > to node B. If these are confirmable CoAP packets, that's a lot of packets. > These will be short requests, but will eat up an enormous amount of > bandwidth. > > I'd like to be able to issue a single request to node A and a single > request to node B to carry out all of these operations, by aggregating > multiple "operations" in a single CoMI request (a single/small number of > CoAP packets). > > What does CoMI offer me today to do this? Should we write the YANG model > in some particular way? What is envisioned in a future revision of CoMI to > answer this need. > > I think the YANG Patch media type could be used with CoMI. This allows multiple edits on different target resources. You could also do a plain PATCH on the datastore root, and provide the subtrees you want to change. > Thanks, > Thomas > Andy > > _______________________________________________ > core mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/core > >
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
