Re: [core] content-formats for cbor YANG

Hi,

On Thu, Apr 20, 2017 at 1:46 AM, peter van der Stok <stokcons@xs4all.nl>
wrote:

> Hi Core,
>
> Following the discussion on CoMI content-formats during ietf98, I want to
> propose the following;
>
> Draft-ietf-core-yang-cbor deines the content-format application/yang+cbor
> which defines CBOR documents which contain the results of the mapping of a
> YANG document to CBOR as specified in the draft.
>
> Draft-ietf-core-comi defines two additional content-formats:
> 1) application/yang-fetch+cbor that specifies the contents and semantics
> of a FETCH CoMI request payload
> 2) application/yang-patch+cbor that specifies the contents and semantics
> of a PATCH CoMI request payload
>
>
I think the name application/yang-patch+cbor is very confusing, because
application/yang-patch+xml and
application/yang-patch+json are already defined in RFC 8072, and they work
completely differently
than the media types in CoMI.

I suggest application/coap-patch+cbor.

The reason this media-type is needed in RESTCONF is to distinguish a "plain
patch"
from a "structured patch". The payload for an RFC 5789 PATCH method is a
representation
of the target resource. A structured patch cannot use the same media-types
because the payload
is a predefined data structure. The resource content for the patch is
embedded inside.

Seems like the new media-types are needed instead of overloading
application/cbor.

Looking forward to alternative proposals or noises of approval.
>
> Greetings,
>
> Peter

Andy

>
>
> --
> Peter van der Stok
> vanderstok consultancy
> mailto: consultancy@vanderstok.org
> www: www.vanderstok.org
> tel NL: +31(0)492474673     F: +33(0)966015248
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>