1. Complete - No missing pieces

2. In order - Proper sequence

3. Uncorrupted - Exactly as sent

4. Without duplication - No repeats

Problems TCP Solves:

1. Packet Loss - Network congestion, router failures

2. Out-of-Order Delivery - Packets taking different routes

3. Data Corruption - Electrical interference, hardware errors

4. Network Congestion - Too much traffic slowing everything down

5. Connection Management - Knowing when to start and stop talking

Without TCP: Webpages would load with missing images, emails would arrive scrambled, file downloads would be unreliable.

With TCP: You get perfect webpages, complete emails, and intact files—even over unreliable networks.

The TCP 3-Way Handshake: Establishing a Connection

Before any data transfers, TCP establishes a reliable connection using a 3-way handshake. Think of it as a formal introduction:

Step 1: SYN (Synchronize)

Client → Server: "I want to talk. My starting sequence number is 100."

• Client picks a random starting sequence number (e.g., 100)

• Sets SYN flag = 1

• Meaning: "Can we establish a connection starting from sequence 100?"

Step 2: SYN-ACK (Synchronize-Acknowledgment)

Server → Client: "I acknowledge your 100. Let's start from my sequence 300."

• Server acknowledges client's SYN (Ack = 101, meaning "I expect sequence 101 next")

• Server sends its own SYN with starting sequence number (e.g., 300)

• Sets SYN flag = 1, ACK flag = 1

• Meaning: "Yes, let's connect. I start from 300, and I acknowledge your starting point."

Step 3: ACK (Acknowledgment)

Client → Server: "I acknowledge your 300. Let's begin!"

• Client acknowledges server's SYN (Ack = 301, meaning "I expect sequence 301 next")

• Sets ACK flag = 1

• Meaning: "Connection established. We can now exchange data."

How Data Transfer Works in TCP

How TCP Ensures Reliability, Order, and Correctness

Reliability: Handling Packet Loss

Problem: What if a packet gets lost?
Solution: Automatic Retransmission

How TCP knows when to retransmit:

1. Timeout: If no ACK received within expected time

Duplicate ACKs: If receiver gets packets out of order (gets packet 3 before 2, it sends duplicate ACK for packet 1)

Order: Handling Out-of-Order Delivery

Problem: Packets may arrive in wrong order due to different network paths.
Solution: Sequence numbers + buffering

Correctness: Handling Data Corruption

Problem: Bits might flip during transmission.
Solution: Checksums

• Each packet includes a mathematical checksum

• Receiver recalculates and compares

• If mismatch → packet is corrupt → discarded (will be retransmitted)

4. Congestion Control: Preventing Network Overload

TCP slows down when it detects congestion:

• Slow Start: Begin cautiously, increase speed gradually

• Congestion Avoidance: Grow window size slowly

• Fast Retransmit: On duplicate ACKs, retransmit immediately

• Fast Recovery: After recovery, don't start from scratch

How a TCP Connection is Closed

TCP closes connections gracefully using a 4-step termination (often called a 4-way handshake).

Why Graceful Closure?

To ensure all data is delivered before closing. Imagine hanging up while someone is still talking!

Step-by-Step Termination:

1. Client sends FIN (Finish): "I'm done sending data"

2. Server sends ACK: "I acknowledge your FIN"

   • At this point: Client → Server direction is closed

   • Server → Client direction may still be open

3. Server sends FIN: "I'm also done sending data"

4. Client sends ACK: "I acknowledge your FIN"

   • Connection fully closed after waiting period

Why both sides send FIN? Because TCP is full-duplex—data can flow in both directions independently. Each side needs to close its sending direction.