Re: [core] content-formats for cbor YANG

[Carsten Bormann <[e-mail]>]

On Apr 20, 2017, at 18:58, Michel Veillette <[e-mail]> wrote:
> 
> Hi Carsten and thanks for your comments.
> 
> About (application/yang-set+cbor)
> Do you propose to use it only for iPATCH /c request ?

That was my intention.

> Or also for GET /c response, PUT /c request and POST /c request ?

We could stick with application/yang+cbor for that, but that would meant that they all use the same structure.  I see that your table doesn’t.
(Or we could go for structural interoperability only.)

> If we move in that direction (structural interoperability), do we need to define a different Content-Format for each one used by CoMI?
> - value
> - CBOR array (instance-identifier)
> - CBOR array (value)
> - CBOR array (instance-identifier, value)

Oh, right, I wasn’t aware that we use all of them.

So this would be (all in application/___+cbor):

yang-value
yang-ids
yang-values
yang-set (or just yang)

This could be four media types, or one media type with four different values for a parameter.  Since, in both cases, we will have four different content-formats in the end, I’d go with four media types so we can minimize confusion.

Grüße, Carsten