3 ms·
This is a bogus explanation, one that has nothing to do with TCP. In TCP every segment has a SEQ number and an ACK number, regardless of it being a handshake s
by tsimionescu 2y ago
This is a bogus explanation, one that has nothing to do with TCP.
In TCP every segment has a SEQ number and an ACK number, regardless of it being a handshake segment or a data segment. This completely negates the described problem: the server's first response to a SYN includes "SEQ=Y, ACK=X". If the client which just sent "SYN seq=Z" receives the ACK for SEQ=X, it will drop this ACK and wait for a new one. Also, a server which receives a new SYN has no reason to drop it, it will send a new ACK instead.