TCP sequence number uses signed integers

[pchaseh]

While working with this library, I have noticed that in commit e13e406 the sequence numbers for TCP are reworked to use signed 32-bit integers. This seems rather unusual to me, given that every resource I can find describes this field as being in the range of 0 to 2^32 - 1. I am hoping that someone can provide clarification on why this decision was chosen

[Dirbaio]

In the end sequence numbers are integers modulo 2^32 where the only thing that matter is the position of one relative to another, not the absolute value.. The behavior is the same whether they're signed or unsigned. Have you found any actual misbehavior due to this?