Re: [core] content-formats for cbor YANG

peter van der Stok <stokcons@xs4all.nl> Mon, 24 April 2017 07:15 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Mon, 24 Apr 2017 09:15:18 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
Cc: Carsten Bormann <cabo@tzi.org>, peter van der Stok <consultancy@vanderstok.org>, Core <core@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <MWHPR06MB23176EC227CEC5E03B482F14FE1A0@MWHPR06MB2317.namprd06.prod.outlook.com>
References: <c2b6fb6e92c6a5680e544963e88d5fa7@xs4all.nl> <09BD739F-89A1-4DA7-9006-E30AEAEE581E@tzi.org> <BN6PR06MB230807D8EF9B69A473254077FE1B0@BN6PR06MB2308.namprd06.prod.outlook.com> <063c4a22d221667a92b180e5dce7ea1f@xs4all.nl> <BN6PR06MB2308B088FCC1DE8AD1370C4FFE1B0@BN6PR06MB2308.namprd06.prod.outlook.com> <102478F5-703D-46C0-9A0B-A21454F940DB@tzi.org> <BN6PR06MB23088F3C7FB189B774466177FE1B0@BN6PR06MB2308.namprd06.prod.outlook.com> <091EF847-AD5E-40D8-B04C-CDBDA47023F1@tzi.org> <8ff54501447ab9e681ecfbee04652fb3@xs4all.nl> <F5C2B33D-56DF-49E6-9EE9-8B2E4A4BADD3@tzi.org> <MWHPR06MB23176EC227CEC5E03B482F14FE1A0@MWHPR06MB2317.namprd06.prod.outlook.com>
Message-ID: <cbd73b5438dbef92bc620f4f1937927c@xs4all.nl>
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/F-FyePYRaRc4w_7iUaq_U-KN8gs>
Subject: Re: [core] content-formats for cbor YANG
Precedence: list

Michel,

See your point. Will change the text accordingly.
I hope that yang-cbor content-format will be defined in yang-cbor draft.

Peter

Michel Veillette schreef op 2017-04-21 17:49:
> Hi Peter
> 
> About "payload of an array of one item can be optimized to just one 
> item"
> 
> I agree with Carsten, I most cases, this rule have the potential to
> create ambiguities.
> In the specific case of a notification, the payload can be either a
> CBOR map (single notification) or a CBOR array (multiple
> notifications).
> A single Content-Format (e.g. yang-value+cbor) will work but a
> solution with two Content-Format seem to be cleaner.
> 
> Regards,
> Michel
> 
> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Friday, April 21, 2017 5:01 AM
> To: peter van der Stok <consultancy@vanderstok.org>
> Cc: Michel Veillette <Michel.Veillette@trilliantinc.com>; Core 
> <core@ietf.org>
> Subject: Re: [core] content-formats for cbor YANG
> 
> On Apr 21, 2017, at 09:18, peter van der Stok <stokcons@xs4all.nl> 
> wrote:
>> 
>> Because the CoMI text now says that the payload of an array of one
>> item can be optimized to just one item, I like to suppress the
>> yang-value+cbor and only retain the yang-values+cbor
> 
> That would create an ambiguity if a value can ever be an array.
> 
> What is so bad about the media type being very specific about what the
> payload is?
> 
> Grüße, Carsten

Re: [core] content-formats for cbor YANG Carsten Bormann
[core] content-formats for cbor YANG peter van der Stok
Re: [core] content-formats for cbor YANG Michel Veillette
Re: [core] content-formats for cbor YANG Carsten Bormann
Re: [core] content-formats for cbor YANG Andy Bierman
Re: [core] content-formats for cbor YANG Michel Veillette
Re: [core] content-formats for cbor YANG peter van der Stok
Re: [core] content-formats for cbor YANG peter van der Stok
Re: [core] content-formats for cbor YANG Michel Veillette
Re: [core] content-formats for cbor YANG Carsten Bormann
Re: [core] content-formats for cbor YANG peter van der Stok
Re: [core] content-formats for cbor YANG Carsten Bormann
Re: [core] content-formats for cbor YANG Michel Veillette
Re: [core] content-formats for cbor YANG peter van der Stok