Day 4: The Language of Transport – TCP vs. UDP

Welcome to Day 4 of your CCNA journey.

On Days 1-3, we built the physical and logical roads (Routers, Switches, Cables). Today, we look at the trucks that drive on those roads.

Layer 4 (The Transport Layer) is responsible for the end-to-end delivery of applications. When you load a webpage, your computer isn’t just sending “data.” It is engaging in a complex conversation with the server to ensure every single pixel arrives in the correct order. Unless, of course, you are watching a live stream, in which case speed matters more than perfection.

This guide covers CCNA Exam Topic 1.5: Compare TCP to UDP. These are the two languages of the internet. One is careful and meticulous; the other is fast and reckless. Mastering the difference is critical for understanding everything from HTTP to VoIP.

The Great Analogy: Phone Call vs. Postcard

To understand Transport protocols, we need to step away from computers for a second and look at human communication.

TCP is a Phone Call (Connection-Oriented)

Imagine you want to tell your friend a long story.

1. Connection Setup: You dial the number. You wait. They pick up and say “Hello?” You say “Hi, can you talk?” They say “Yes.” (This is the Handshake).
2. Reliability: You tell the story. If they say “Wait, I didn’t hear that last part,” you repeat it. You know for a fact they heard you.
3. Teardown: When you are done, you say “Goodbye,” they say “Goodbye,” and you hang up.

TCP (Transmission Control Protocol) works exactly like this. It is formal, reliable, and establishes a session before sending data.

UDP is a Postcard (Connectionless)

Now imagine you want to send a quick update to a friend. You write a postcard and drop it in the mailbox.

1. No Setup: You don’t call them first to warn them it’s coming. You just send it.
2. No Reliability: You have no idea if the mailman lost it. You don’t get a receipt. If it arrives, great. If not, oh well.
3. No Ordering: If you send 5 postcards, they might arrive out of order (Day 3 arrives before Day 1).

UDP (User Datagram Protocol) works like this. It is “Best Effort.” It sends data and hopes for the best.

TCP: The Reliable Heavyweight

TCP is the protocol of choice for applications where data integrity is more important than speed. Web browsing (HTTP/HTTPS), Email (SMTP/IMAP), and File Transfers (FTP) all use TCP. If you are downloading a .exe file, you cannot afford to lose a single bit, or the program won’t run.

The Key Features of TCP (Memorize These)

1. Reliable: It guarantees delivery. If a packet is lost, it is resent.
2. Sequenced: Packets are numbered. If they arrive out of order (1, 3, 2), TCP puts them back in order (1, 2, 3).
3. Flow Control (Windowing): If the sender is talking too fast, the receiver can say “Whoa, slow down!” preventing buffer overflows.

The Three-Way Handshake

Before any data is sent, TCP establishes a connection. This is a favorite exam topic.

1. SYN (Synchronize): The Client sends a packet with the SYN flag set. “I want to talk to you.”
2. SYN-ACK (Synchronize-Acknowledge): The Server replies. “I received your request (ACK), and I am ready to talk (SYN).”
3. ACK (Acknowledge): The Client replies. “I received your acceptance. Let’s begin.”

Only after step 3 does the actual data (like the webpage HTML) start flowing.

Flow Control: The Sliding Window

What if the Server is a supercomputer and the Client is an old phone? The Server could send data so fast the phone crashes. TCP uses Windowing to solve this.

• The Window Size: The amount of data the sender can transmit before it must stop and wait for an Acknowledgment.
• Dynamic: If the receiver is overwhelmed, it sends a smaller Window Size. If the network is clear, it increases the Window Size to send data faster.

UDP: The Fast Lightweight

UDP is the protocol of choice for Real-Time Applications. Think Voice over IP (VoIP), Video Streaming (Zoom/Teams), and Online Gaming.

Why use an “Unreliable” protocol?

Imagine you are on a Zoom call.

• Scenario A (TCP): A packet of audio gets lost. TCP stops everything. It asks the sender to re-send that millisecond of audio. By the time it arrives, 2 seconds have passed. The conversation pauses, then speeds up to catch up. This is “Lag” or “Jitter.” It makes the call unusable.
• Scenario B (UDP): A packet of audio gets lost. UDP doesn’t care. It just plays the next packet. You hear a tiny glitch in the voice, but the conversation continues flowing in real-time.

For live media, it is better to lose data than to be late.

The UDP Header

The UDP header is tiny (8 Bytes) compared to TCP (20 Bytes). It contains only:

1. Source Port
2. Destination Port
3. Length
4. Checksum

That’s it. No sequence numbers, no acknowledgments, no windowing. This low overhead makes it incredibly fast.

Head-to-Head Comparison (Topic 1.5 Summary)

For the CCNA 200-301, you will likely see a drag-and-drop question asking you to categorize these traits.

Feature	TCP (Transmission Control Protocol)	UDP (User Datagram Protocol)
Connection	Connection-Oriented (3-Way Handshake)	Connectionless (Fire and Forget)
Reliability	Reliable (Acknowledgments & Retransmissions)	Unreliable (Best Effort)
Ordering	Sequenced (Numbering reorders packets)	Unordered (App must handle ordering)
Flow Control	Yes (Windowing)	No
Speed	Slower (High Overhead)	Faster (Low Overhead)
Header Size	20 Bytes	8 Bytes
Common Uses	Web (HTTP/HTTPS), Email (SMTP), FTP, SSH	VoIP, DNS, TFTP, Video Streaming, Gaming

A Note on DNS and Headers

DNS (Domain Name System) is a unique beast.

• DNS primarily uses UDP Port 53 for standard queries (speed is key).
• However, if the DNS response is huge (Zone Transfer), it switches to TCP Port 53 to ensure the database is copied correctly.

This is a classic “Gotcha” question. Generally, think DNS = UDP, but know that it can use TCP.

To pass Topic 1.5, remember the “Why.”

• We use TCP when we can’t afford to lose data (Documents, Emails, Webpages).
• We use UDP when we can’t afford to be late (Voice, Video, Live Gaming).

Ready for Day 5? Now that we understand how data is transported reliably, we need to understand the addresses that guide it. Tomorrow, we tackle the biggest topic of them all: IPv4 Addressing and Subnetting.

Author’s Note: This guide is strictly aligned with Cisco CCNA 200-301 Exam Topic 1.5. Remember: SYN, SYN-ACK, ACK!