[Cbor] draft-cbor-cde issues

[Laurence Lundblade <[e-mail]>]

Stepping back from my request to put cbor-cde on the standard track, I realized what I’m really after is clarity on CBOR serialization for the sake of the CBOR ecosystem. CBOR is an important IETF standard and I want protocol authors and implementors to be able to understand serialization concepts and choices.

I don’t think we have this clarity in the draft yet. For example, no one but Carsten seemed to understand ALDR until recently. No one else stepped up and to explain or support it. The text in the draft didn’t do it for me and maybe no one else. There are areas beyond ALDR that I would like made more clear.

Much of this comes from my work to build thorough serialization support into my encoder/decoder (that work is substantially complete and in alpha release).

I plan to file issues in GitHub, contribute text and maybe raise topics here.

LL