Return to Answer

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two 1.5 times the round-trip time (RTT).

(Each side sees a 1x RTT delay for the handshake to happen while the server is one transmission delay / .5 RTT behind the client - assuming equal transmission delay for both directions.)

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the client side, the sequence is

1. SYN sent
2. longer delay (RTT + remote stack overhead) - 0.020003
3. SYN/ACK received
4. very small delay (local stack overhead) - 0.000077
5. final ACK is sent, socket is open
6. very small delay (local stack & application overhead) - 0.000223
7. GET sent

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received
6. very small delay (remote stack & application overhead)
7. GET is received

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two 1.5 times the round-trip time (RTT).

(Each side sees a 1x RTT delay for the handshake to happen while the server is one transmission delay / .5 RTT behind the client - assuming equal transmission delay for both directions.)

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the client side, the sequence is

1. SYN sent
2. longer delay (RTT + remote stack overhead) - 0.020003
3. SYN/ACK received
4. very small delay (local stack overhead) - 0.000077
5. final ACK is sent, socket is open
6. very small delay (local stack & application overhead) - 0.000223
7. GET sent

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received, socket is open
6. very small delay (remote stack & application overhead)
7. GET is received

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two 1.5 times the round-trip time (RTT).

(Each side sees a 1x RTT delay for the handshake to happen while the server is one transmission delay / .5 RTT behind the client - assuming equal transmission delay for both directions.)

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received
6. very small delay (remote stack & application overhead)
7. GET is received

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two 1.5 times the round-trip time (RTT).

(Each side sees a 1x RTT delay for the handshake to happen while the server is one transmission delay / .5 RTT behind the client - assuming equal transmission delay for both directions.)

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the client side, the sequence is

1. SYN sent
2. longer delay (RTT + remote stack overhead) - 0.020003
3. SYN/ACK received
4. very small delay (local stack overhead) - 0.000077
5. final ACK is sent, socket is open
6. very small delay (local stack & application overhead) - 0.000223
7. GET sent

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received
6. very small delay (remote stack & application overhead)
7. GET is received

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two times the round-trip time (RTT).

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received
6. very small delay (remote stack & application overhead)
7. GET is received

It's called 3-way handshake, so it is transmitted three times: SYN -> SYN/ACK -> ACK. The minimum time required is two 1.5 times the round-trip time (RTT).

(Each side sees a 1x RTT delay for the handshake to happen while the server is one transmission delay / .5 RTT behind the client - assuming equal transmission delay for both directions.)

In your capture, the only transmission time is between SYN and SYN/ACK. The successive ACK is the reaction to the received SYN/ACK. The socket is established on this side and the local node fires away with GET.

On the listener (server) side, this would look like

1. SYN received
2. very small delay (local stack overhead)
3. SYN/ACK sent
4. longer delay (RTT + remote stack overhead)
5. final ACK is received
6. very small delay (remote stack & application overhead)
7. GET is received