Re: [netmod] [Technical Errata Reported] RFC7950 (6855)

[Andy Bierman <[e-mail]>]

On Tue, Mar 1, 2022 at 8:15 AM Carsten Bormann <[e-mail]> wrote:

> (Removing RFC-editor from the list:)
>
> On 2022-03-01, at 16:42, SADOVNIKOV, ALEXEI <[e-mail]> wrote:
> >
> > I continue to doubt if this optimization continues to have value in
> presence of JSON processing, where such optimization is not possible.   I
> am expecting an implementation these days to implement both XML and JSON,
> and then it either implements something which can deal with unordered for
> both, or have two different implementations one of which is optimized.
>
> This is very interesting also for YANG-CBOR.  We modeled our
> representation after that used in YANG-JSON, but of course CBOR can be much
> more efficient (in particular in conjunction with YANG-SIDs).
> If there is a performance problem with the YANG-JSON approach that we
> could work around on the CBOR side, I would certainly like to hear about it!
>
>
IMO JSON is too stateful, making it fragile (e.g., missing or extra comma).
It is also unordered, making implementation of annotations defined in RFC
7952 much more difficult.

The issues with JSON are more pronounced for a streaming server, where
there is
no JSON document in memory, just a lot of internal API calls to get data.
The API calls are easier if "what came before" and "what comes next" are
irrelevant (like for XML).

I am very interested in the CBOR encoding of YANG annotations (still TBD in
the drafts).




> Grüße, Carsten
>

Andy


>
> _______________________________________________
> netmod mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netmod
>