Notes on future transport frame headers #143
Description
It is desirable to have the total transfer payload size in the header. Yes, every frame of a transfer will carry the size of that transfer's payload, because in non-CAN transports frames may arrive out of order and even interleave with neighboring transfers. Having the size allows us to allocate not just extent-sized payload buffers but min(extent,size), which saves memory if the extent is large.
Cyphal/UDP specific
Please refer to LibUDPard for the header definition.
Cyphal/serial specific
Derived from LibUDPard except that it must contain the explicit destination UID and should not contain the multi-frame reassembly states since Cyphal/serial only supports single-frame transfers with unlimited MTU.