You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Transfer-ID reuse in response transfers was a design mistake and it warrants a footnote #148
The transfer-ID is quite essential for multi-frame reassembly, deduplication, sequence monitoring, and redundant interface selection, but its usage for request/response matching was a mistake because it interferes with the primary use cases if the server responds to multiple requests not in the order of their arrival, which has been observed in the wild.
One mitigation is to use a transfer-ID timeout of zero for response transfers; see:
We already mention in Spec v1.0 that the transfer-ID timeout of response ports should be zero, but that is not enough because a delayed duplicated start-of-transfer arriving at the client RX port may cause the port to discard a valid incomplete multiframe transfer, causing transfer loss. Ideally, the transfer-ID timeout should never be zero to avoid this condition.
There is no way to fix this now without breaking compatibility, so this is going to stay as is in RPCs. In v1.1 named topics we should send the responded-to transfer-ID as part of the response payload header.
Clarification to the latest point: Cyphal v1.1 will not need RPC response transfers at all. It needs RPC only for sending response messages and for reliable ACKs, both can be delivered using RPC-request transfers.
We will still need a transfer-ID timeout of zero for ports where out-of-order delivery is acceptable.
Activity
pavel-kirienko commentedon Nov 18, 2025
Clarification to the latest point: Cyphal v1.1 will not need RPC response transfers at all. It needs RPC only for sending response messages and for reliable ACKs, both can be delivered using RPC-request transfers.
We will still need a transfer-ID timeout of zero for ports where out-of-order delivery is acceptable.
pavel-kirienko commentedon Apr 12, 2026
v1.1 proposes 64-bit tags for this which entirely resolve this issue.
The relevant part of v1.0 where we require zero transfer-ID timeout for response transfers is here: