Currently, the "bpcat" test program employs only raw/barebones BP, and receiver delivers data to stdout in the order it was received.
Thus, if bundle delivery disruptions between the sender and receiver do occur, then it is likely that the data will be delivered to the application out of order. This is in accordance with RFC9171 in that BP does not concern itself with delivery order; the protocol will deliver payloads in the order they came through the network. Any higher level data ordering is to be provided by higher levels.
However in the spirit of the "netcat" and similar programs that operate on a file/stream, the ordering is important. It therefore may be necessary to include some sort of stream position at the sender and reordering feature at the receiver, to ensure bundles are delivered in the order they were intended.
Currently, the "bpcat" test program employs only raw/barebones BP, and receiver delivers data to stdout in the order it was received.
Thus, if bundle delivery disruptions between the sender and receiver do occur, then it is likely that the data will be delivered to the application out of order. This is in accordance with RFC9171 in that BP does not concern itself with delivery order; the protocol will deliver payloads in the order they came through the network. Any higher level data ordering is to be provided by higher levels.
However in the spirit of the "netcat" and similar programs that operate on a file/stream, the ordering is important. It therefore may be necessary to include some sort of stream position at the sender and reordering feature at the receiver, to ensure bundles are delivered in the order they were intended.