Imagine sending a long WhatsApp message, but:

• Messages arrive out of order

• Some messages never arrive

• Some messages arrive twice

• You don’t know if the other person even received them

That’s what sending data without rules looks like on a network.

The internet breaks data into small packets, and those packets:

• Can take different paths

• Can get lost

• Can arrive out of order

👉 We need rules to make communication reliable.

What is TCP and why is it needed?

TCP (Transmission Control Protocol) is a communication rulebook that ensures:

• Data is delivered

• Data is delivered in order

• Data is delivered correctly

• Sender and receiver agree before talking

💡 TCP is used when accuracy matters more than speed.

Examples:

• Websites (HTTP/HTTPS)

• File downloads

• Emails

• Login systems

• APIs

Problems TCP is designed to solve

TCP exists to fix these real-world network problems:

What is the TCP 3-Way Handshake?

Before sending data, TCP establishes a connection.

Think of it like starting a phone call ☎️:

“Can you hear me?”
“Yes, I can hear you.”
“Great, let’s talk.”

This agreement is called the 3-Way Handshake.

Step-by-step: SYN, SYN-ACK, ACK

Step 1: SYN (Client → Server)

Client says:

“Hey Server, I want to talk. Are you available?”

• Client sends a SYN packet

• Includes a sequence number (starting point)

Step 2: SYN-ACK (Server → Client)

Server replies:

“Yes, I’m available. I hear you.”

• Server sends SYN + ACK

• ACK confirms client’s SYN

• SYN includes server’s own sequence number

🧩 Step 3: ACK (Client → Server)

Client responds:

“Great, I hear you too.”

• Client sends ACK

• Connection is now established

🎉 Both sides agree → data transfer can begin

How data transfer works in TCP

Once connected:

• Data is split into segments

• Each segment has:

  • Sequence number

  • Data

• Receiver sends back ACKs

Example:

• Sender sends data #1

• Receiver replies: “ACK 2” (means “I got #1, send next”)

This continues until all data is sent.

Sequence numbers & acknowledgements (high level)

Think of page numbers in a book 📖

• Sequence number = page number

• ACK = “I’ve read up to page X”

If page 5 is missing:

• Receiver keeps asking for page 5

• Sender resends page 5

How TCP ensures reliability, order & correctness

TCP guarantees:

Reliability

• Uses ACKs

• Retransmits missing data

Correct order

• Uses sequence numbers

• Reorders packets before delivering to app

Correctness

• Uses checksums

• Detects corrupted data

Flow & congestion control

• Adjusts speed based on network conditions

What if a packet is lost?

Example:

• Sender sends packets 1, 2, 3

• Packet 2 is lost ❌

• Receiver says: “I’m missing packet 2”

• Sender retransmits packet 2

No guessing. No confusion. Just rules.

How a TCP connection is closed (FIN & ACK)

Ending a TCP connection is also polite and structured.

Step-by-step:

1. Client sends FIN → “I’m done sending”

2. Server sends ACK

3. Server sends FIN → “I’m done too”

4. Client sends ACK

Connection is cleanly closed.

TCP Connection Lifecycle (big picture)

ESTABLISH
   ↓
3-Way Handshake
   ↓
DATA TRANSFER
   ↓
ACKs & Retransmissions
   ↓
CONNECTION CLOSE