What Happens Without Rules?

Imagine shouting your order at a drive-through without checking if anyone's listening. Maybe they hear you, maybe they don't. Maybe your order arrives scrambled.

That's the internet without TCP:

• Packets arrive out of order

• Some packets never arrive

• No way to know if the other side received anything

• Complete chaos

That's why we need TCP.

What is TCP?

TCP (Transmission Control Protocol) is like having a careful conversation. Before sending anything important, both sides confirm they're ready. Then they keep checking "did you get that?" after each message.

TCP = Registered mail with tracking
No TCP = Throwing messages in bottles into the ocean

The TCP 3-Way Handshake

Before sending any real data, TCP does a handshake. Think of it like a phone call:

You: "Hello?"
Friend: "Hey! I can hear you!"
You: "Great! Let's talk!"

That's literally what happens, but with SYN and ACK packets.

Step 1: SYN (Client to Server)

Client ──────── SYN ──────── ▶ Server
        "Can we talk? My starting number is 1000"

The client sends a SYN packet saying "I want to connect, and here's my sequence number."

Step 2: SYN-ACK (Server to Client)

Client ◀──────── SYN-ACK ──────── Server
       "Yes! My number is 5000, and I got your 1000"

The server responds: "I'm ready too! Here's MY sequence number, and yes, I got yours."

Step 3: ACK (Client to Server)

Client ──────── ACK ──────── ▶ Server
        "Got your 5000! Let's go!"

The client confirms: "Got it! Connection established!"

Connection is now open and data can flow.

Why Three Steps?

Both sides need to:

1. Announce their starting sequence number

2. Acknowledge the other side's number

Three steps is the minimum to sync both ways. That's why it's called the "3-way handshake."

How Data Transfer Works

Once connected, data flows with sequence numbers tracking everything.

Example:

Client sends: "Hello" (seq=1000, 5 bytes)
Server ACKs:  ack=1005 (got it, send 1005 next)

Client sends: "World" (seq=1005, 5 bytes)  
Server ACKs:  ack=1010 (got it, send 1010 next)

Every byte gets a number. The server acknowledges what it received and what it expects next.

How TCP Ensures Reliability

1. Acknowledgments (ACKs)

Every packet must be acknowledged. No ACK? Resend it.

Client ───── Packet ─────▶ Server
Client ◀──── ACK ───────── Server  ✓ Good!

Client ───── Packet ─────▶ ❌ Lost!
Client    ...timeout...no ACK
Client ───── Packet ─────▶ Server  (Resend!)
Client ◀──── ACK ───────── Server  ✓ Success!

2. Sequence Numbers Keep Order

Packets might arrive scrambled. TCP uses sequence numbers to reorder them.

Sent:     1 → 2 → 3 → 4
Arrived:  1 → 3 → 2 → 4
TCP puts: 1 → 2 → 3 → 4  ✓

3. Checksums Detect Corruption

Each packet has a checksum. If data gets corrupted, checksum fails, TCP requests a resend.

4. Flow Control

TCP makes sure the sender doesn't overwhelm the receiver. The receiver says "I can handle this much" and the sender adjusts.

How TCP Closes a Connection

When done, you can't just hang up. You need to close properly with FIN packets:

Client ───── FIN ─────▶ Server  ("I'm done")
Client ◀──── ACK ────── Server  ("OK")
Client ◀──── FIN ────── Server  ("I'm done too")
Client ───── ACK ─────▶ Server  ("Bye!")

Four steps (4-way handshake) to close cleanly.

The Complete TCP 3- Way handshake

Real-World Example

When you visit google.com:

1. Handshake: Your browser and Google's server do SYN → SYN-ACK → ACK

2. Request: Browser sends "GET / HTTP/1.1" with sequence numbers

3. Response: Google sends HTML back with ACKs

4. Close: Both sides send FIN and ACK to disconnect

All of this happens in milliseconds. You never see it, but it's happening constantly.

Why This Matters

Every time you:

• Load a website

• Send an email

• Use an API

• Download a file

TCP is:

• Handshaking before starting

• Numbering every byte

• Confirming delivery

• Retransmitting lost packets

• Keeping everything in order

• Closing cleanly when done

Summary

3-Way Handshake:

1. Client: "Can we talk?" (SYN)

2. Server: "Yes! You there?" (SYN-ACK)

3. Client: "Yep, let's go!" (ACK)

Reliable Transfer:

• Sequence numbers track order

• ACKs confirm delivery

• Lost packets get resent

• Checksums catch corruption

Clean Close:

• Both sides send FIN

• Both sides ACK

• Connection closed

That's TCP! It costs a bit more time (handshakes, ACKs), but you get guaranteed delivery.