Jump to content

Possibly a bug in the µTP specs


Recommended Posts

As it says here:

The number of bytes in-flight is cur_window.


Unlike TCP, sequence numbers and ACKs in uTP refers to packets, not bytes.


Each socket keeps a state of the next sequence number to use when sending a packet, seq_nr. It also keeps a state of the sequence number that was last received, ack_nr. The oldest unacked packet is seq_nr - cur_window.

If all three are true, this will be the end of the universe. seq_nr - cur_window mixes packets with bytes, and therefore means nothing.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...