Re: [netconf] YANG encoding in CBOR

[Carsten Bormann <[e-mail]>]

On Mar 27, 2019, at 07:16, Juergen Schoenwaelder <[e-mail]> wrote:
> 
> A robust fix to all these problems will be to tag the type members in
> order to discriminate the values in the encodings. This, however, will
> take some time to specify and we will need to preserve backwards
> compatibility with unions without a tag (but compilers can encourage
> people to add tags whenever modules are updated).


And that may be the way forward:

As XML and JSON already differ in handling “first-match wins” (as Andy has demonstrated), there is probably not a lot of damage in CBOR being different again in handling this arcane case, so we can mostly ship as is (but see below).

We then develop the YANG-wide fix together.  We’ll make sure that the CBOR union representation has the right placeholders to put that in.  For that, it would be nice to have a direction about where exactly that information would be in the instance tree.  And, more importantly, if something needs to be included in the SID files, it would be good to nail that down now.

Grüße, Carsten