Ensure that byte counts in tag CNs are consistent #18

Open
opened 2025-09-08 09:10:04 -06:00 by sashakoshka · 0 comments
Owner

We offset the byte count in integer tag CNs by -1 so that the format can squeeze in very large numbers up to 256 bits. This needs to be done for OTA and KTV and wherever else byte counts are stored in the CN (I think that's all). I'm not sure this is done consistently even with integers. The correct behavior needs to be written down in the protocol specification, and tested for in generated code and dynamic code.

We offset the byte count in integer tag CNs by -1 so that the format can squeeze in very large numbers up to 256 bits. This needs to be done for OTA and KTV and wherever else byte counts are stored in the CN (I think that's all). I'm not sure this is done consistently even with integers. The correct behavior needs to be written down in the protocol specification, and tested for in generated code and dynamic code.
sashakoshka added a new dependency 2025-09-10 07:47:28 -06:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Blocks
Reference: sashakoshka/hopp#18
No description provided.