Re: [netconf] [core] YANG encoding in CBOR

[Juergen Schoenwaelder <[e-mail]>]

On Fri, Mar 22, 2019 at 05:08:20PM +0100, Carsten Bormann wrote:
> 
> Anyway, I haven’t seen a piece of real-world YANG that actually has this problem, so I would be a bit reluctant to make CBOR-based implementations more complex (and less efficient) so solve this (non-?)problem.
>

I think we need to make sure that the interpretation of yang-defined
data is _always_ the same and does not depend on the encoding
negotiated between a client and a server. Efficiency is nice,
avoiding ambiguity is a must.

Avoiding ambiguity can be achieved in different ways, such as making
sure all encodings are designed to not allow different interpretations
(even if that means a loss of efficiency in some cases) or by changing
YANG (or YANG usage guidelines) such that constructs that may lead to
ambiguities are impossible or at least flagged and then avoided. I
guess this is why this topic pops up in the context of YANG next and
we need to figure out which road to take.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>