Re: [Yot] questions concerning sid value assignments

[peter van der Stok <[e-mail]>]

Hi Michel,

thanks for the rectifications; will work out the example better for the 
draft.
But it served its purpose.

> Example:
> {
>   1001001: {
>     +2 : "2016-10-07T19:31:42Z",  / SID = 1001003, created-on /
>     +4 : "2016-10-21T19:31:42Z",  / SID = 1001005, expires-on /
>     +1 : "verified",              / SID = 1001002, assertion /
>     +10 : "JADA123456789",        / SID = 1001011, serial-number /
>     +5 : h'0102030405060708090A0B0C0D0F',  / SID = 1001006, 
> idevid-issuer /
>     +8 : h'0102030405060708090A0B0C0D0F',  / SID = 1001009, 
> pinned-domain-cert /
>     +3 : true,                    / SID = 1001004,
> domain-cert-revocation-checks /
>     +6 : "2017-10-07T19:31:42Z"   / SID = 1001007, last-renewal-date /
>   }
> }
> 
> About "when using comi to return the value"
> 
> Currently, these YANG files don't define any data nodes which can be
> instantiated in a datastore.

This is an unexpected turn of events.
in ietf-voucher there is voucher container defined.
but the grouping makes sure that it is only a schema node and not a data 
node.

Nice to know.

> If you want to make the last voucher received accessible though CoMI,
> you will need to add in the AYNG file something like:
> 
> container last_voucher_received {
>    uses voucher-artifact-grouping;
> }
> 
> This definition creates a new set of SIDs for the different fields
> within the voucher.

what I would have expected;
> 

cheerio,

peter