TCP (Transmission Control Protocol) is a set of rules that makes sure:

• Data reaches the right destination

• Data arrives completely

• Data arrives in the correct order

• Lost data is sent again

• Both sides agree when communication starts and ends

💡 TCP is used when accuracy matters:

• Websites (HTTP/HTTPS)

• Emails

• File downloads

• Login systems

If data loss is okay (like live video), TCP is usually not used.

Problems TCP is designed to solve

Without TCP, these problems happen:

1. Data may be lost

2. Data may arrive out of order

3. Receiver may get duplicate data

4. Sender doesn’t know if data was received

5. No clear start or end of communication

TCP fixes all of these.

Before TCP sends data: the 3-Way Handshake

TCP never sends data blindly.

First, it checks:

“Are you ready to talk?”
“Yes, I’m ready.”
“Cool, let’s talk.”

This process is called the TCP 3-Way Handshake.

TCP 3-Way Handshake (Conversation Analogy)

Step 1: SYN — “Can we talk?”

Client → Server

Client says:

“Hey Server, I want to start a connection.”

This message is called SYN (Synchronize).

Step 2: SYN-ACK — “Yes, I’m listening”

Server → Client

Server replies:

“Yes, I got your request, and I’m ready too.”

This message is SYN + ACK
(Synchronize + Acknowledge)

Step 3: ACK — “Great, let’s start”

Client → Server

Client confirms:

“Got it. Let’s begin communication.”

This is ACK (Acknowledge).

✅ Connection established
Now data transfer can begin.

Why 3 steps? Why not just 1?

Because both sides must confirm:

• They are alive

• They can send

• They can receive

Skipping this can cause:

• Fake connections

• Half-open connections

• Wasted resources

How data transfer works in TCP (simple version)

Once the connection is open:

• Data is broken into small chunks

• Each chunk is given a sequence number

• Receiver sends back ACKs saying what it received

Think of sequence numbers like page numbers in a book.

Sequence Numbers & ACKs (High-level)

Let’s say you send data:

• Packet 1 → Sequence 1

• Packet 2 → Sequence 2

• Packet 3 → Sequence 3

Receiver replies:

“I got up to Sequence 3.”

That reply is an ACK.

If Packet 2 is missing:

• Receiver says:

  “I’m still waiting for Sequence 2.”

How TCP ensures reliability

TCP uses four main techniques:

1. Sequence Numbers

• Keeps data in order

• Helps detect missing data

2. Acknowledgements (ACKs)

• Receiver confirms what it received

• Sender knows what was successful

3. Retransmission

If a packet is lost:

• ACK doesn’t arrive

• Sender waits for a timeout

• Sender resends the missing packet

4. Error Checking

• Each packet has a checksum

• If data is corrupted, it’s discarded

• Sender resends it

What if a packet is lost? (Real example)

1. Sender sends packets 1, 2, 3

2. Packet 2 gets lost

3. Receiver gets 1 and 3

4. Receiver says:

   “I got 1, still waiting for 2”

5. Sender resends packet 2

6. Communication continues normally

No panic. No confusion.
That’s TCP doing its job.

How TCP connection is closed

TCP also closes connections politely, not suddenly.

Connection termination uses:

• FIN (Finish)

• ACK (Acknowledge)

Simple flow:

1. Client → Server: FIN

   “I’m done sending data.”

2. Server → Client: ACK

   “Okay, I got that.”

3. Server → Client: FIN

   “I’m done too.”

4. Client → Server: ACK

   “Confirmed. Bye.”

🔚 Connection closed safely.

Why proper closing matters

If connections aren’t closed properly:

• Memory leaks

• Too many open connections

• Server crashes over time

TCP avoids this.

TCP Connection Lifecycle (big picture)

1. Establish connection
   → 3-Way Handshake

2. Data transfer
   → Sequence numbers, ACKs, retransmissions

3. Close connection
   → FIN & ACK