Closed fanpei91 closed 4 years ago
I believe this is correct. The reason is sequence numbers wrap around and TCP window size is capped at 1/2 the sequence space (i.e 2^32/2). Which means that 0 is in fact > 3744465773 and not less as otherwise the permitted window will be > 2 ^32/2 and that would break down the strict ordering logic of sequence numbers.
I see, thank you for your explanation. I understand now why the window scale factor is up to 14, not 255.
PAWS has been on my todo list forever. It required first implementing support for Timestamps which was done but then we had other things like SACK that took priority. PAWS is something we intend to implement in the future. Current uses of netstack ran little risk of wrap around as it's not used in situations where the sequence number could wrap around that fast for PAWS to be required.
-bhasker
On Thu, Dec 27, 2018 at 6:58 PM fanpei91 notifications@github.com wrote:
One question: Why there is no implementation of PAWS https://tools.ietf.org/html/rfc1323#page-17?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/google/netstack/issues/14#issuecomment-450278440, or mute the thread https://github.com/notifications/unsubscribe-auth/AAssNUOLyuxPWjJg7cAtJcRLoxiy48yIks5u9YjkgaJpZM4ZgOVV .
Thank you. I am forwarding SACK and PAWS.
Can this issue be closed?
seqnum.LessThan :
It will be false at this case:
This version works correctly.