Re: [core] YANG to CBOR mapping version 1

peter van der Stok <stokcons@xs4all.nl> Wed, 13 July 2016 06:34 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE9612B071 for <core@ietfa.amsl.com>; Tue, 12 Jul 2016 23:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5kfBEIxy-_y for <core@ietfa.amsl.com>; Tue, 12 Jul 2016 23:34:21 -0700 (PDT)
Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F35712B031 for <core@ietf.org>; Tue, 12 Jul 2016 23:34:21 -0700 (PDT)
Received: from webmail.xs4all.nl ([194.109.20.216]) by smtp-cloud6.xs4all.net with ESMTP id J6aK1t00K4fjQrE016aKgd; Wed, 13 Jul 2016 08:34:19 +0200
Received: from 2001:983:a264:1:64eb:91b1:57ea:8151 by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Wed, 13 Jul 2016 08:34:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Wed, 13 Jul 2016 08:34:19 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <BLUPR06MB17638EB4CCB4235B5101D540FE300@BLUPR06MB1763.namprd06.prod.outlook.com>
References: <1ed9a5d16aca7d13412259e94afc1aa2@xs4all.nl> <BLUPR06MB17639739570760661AEC32C3FE3C0@BLUPR06MB1763.namprd06.prod.outlook.com> <e18f0f45bfae89fc55df444fdd957550@xs4all.nl> <BLUPR06MB17638EB4CCB4235B5101D540FE300@BLUPR06MB1763.namprd06.prod.outlook.com>
Message-ID: <d58ca58bd8f89b9856a2e23290a18ba8@xs4all.nl>
X-Sender: stokcons@xs4all.nl (2o4EKVkKqtwZ3O+PjWIv4MELJ7yvPfNR)
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7CahSEcdjSYiKVubGya9_a9in7Q>
Cc: Core <core@ietf.org>
Subject: Re: [core] YANG to CBOR mapping version 1
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2016 06:34:23 -0000

Hi Michel,

When a specification changes it set of of keys, I don't think the SIDs 
will change.
It is for sure that the hashes are not affected by the attribution of a 
key.

Therefore, what happens when client and server use different keys in 
otherwise identical list specification?

Peter

Michel Veillette schreef op 2016-07-12 17:07:
> Hi Peter
> 
> The validations performed by the entity which de-serialize the CBOR
> payload is based on the YANG schema.
> This validation is based on all king of YANG statements such as:
> key, unique, range, pattern, length, min-elements, max-elements, must,
> when, if-feature
> 
> The identification of which data nodes are keys is considered
> unnecessary meta-data since available in the schema.
> Even more heavy weight representations such as xml and json don't
> include this meta-data in the encode payload.
> 
> Regards,
> Michel
> 
> -----Original Message-----
> From: peter van der Stok [mailto:stokcons@xs4all.nl]
> Sent: Tuesday, July 12, 2016 6:08 AM
> To: Michel Veillette <Michel.Veillette@trilliantinc.com>
> Cc: consultancy@vanderstok.org; Core <core@ietf.org>
> Subject: RE: [core] YANG to CBOR mapping version 1
> 
> Hi Michel,
> 
>> 
>> However, I am missing how to transport a given list instance with its
>> key values in the CBOR encoding. Section 4.4 describes the encoding of
>> a complete list not a subset of its instances.
>> 
>> [MV] A list instance is a collection which is described in section 
>> 4.2.
>> ______________________________________________________________________
>> _______________________
> 
> With the current text I don't see how you distinguish instances with
> the same key from instances with different keys.
> 
> Example:
> 
> list server {
>       key name;
> 
>       leaf name {
>         type string;
>       }
>       leaf iburst {
>         type boolean;
>         default false;
>     }
> 
> How to distinguish that in the list below that two instances are
> identical (should not occur)
>     [
>       {
>         1755 : "NRC TIC server",          # name (SID 1755)
>         1754 : false,                     # iburst (SID 1754)
>       },
>       {
>         1755 : "NRC TIC server",          # name (SID 1755)
>         1754 : true,                     # iburst (SID 1754)
>       }
>     ]
> 
> And the following two instances are different  (valid array)
> 
>     [
>       {
>         1755 : "NRC TAC server",          # name (SID 1755)
>         1754 : true,                      # iburst (SID 1754)
>       },
>       {
>         1755 : "NRC TIC server",          # name (SID 1755)
>         1754 : true,                     # iburst (SID 1754)
>       }
>     ]