[Cbor] Re: List of all serialization variation (was Re: Working Group Last Call on Serialization draft)

[Joe Hildebrand <[e-mail]>]

I was thinking about Unicode normalization forms, but maybe there's something else?

— 
Joe Hildebrand

> On Sep 3, 2026, at 10:57 AM, Laurence Lundblade <[e-mail]> wrote:
> 
> Appreciate the thorough review!
> 
>> On Aug 18, 2026, at 12:05 PM, Joe Hildebrand <[e-mail]> wrote:
>> 
>> s2.1.1: I suggest "it may mandate deterministic serialization for all implementations in order to eliminate all serialization variability" -> "it may mandate deterministic serialization for all implementations in order to minimize serialization variability", since there are other sources of serialization variability.
> 
> 
> I can’t think of any other sources of serialization variability. Seems important to be sure we got themm all. They are listed in the description of [General Serialization]. Map sort ordering is missing, but I will add it [PR-unordered]. Am I missing something?
> 
>  - map sorting
>  - def/indef lengths
>  - CBOR argument length
>  - float length
> 
> 
> There is variability at the data model level that needs to be addressed for full determinism of a protocol, but that is not serialization variation.
> 
> LL
> 
> 
> [General Serialization]: https://www.ietf.org/archive/id/draft-ietf-cbor-serialization-08.html#name-general-serialization
> [PR-unordered: https://github.com/cbor-wg/draft-ietf-cbor-serialization/pull/84/changes
> _______________________________________________
> CBOR mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]