Re: [core] YANG to CBOR mapping version 1

[Michel Veillette <[e-mail]>]

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:[e-mail]] 
Sent: Tuesday, July 12, 2016 6:08 AM
To: Michel Veillette <[e-mail]>
Cc: [e-mail]; Core <[e-mail]>
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)
      }
    ]