Unveiling TCP: How Reliable Transport Works and Why It Matters

Network Layer Overview

Communication between two hosts begins at the physical layer, where hardware interfaces (e.g., cables, USB) are defined, and proceeds to the data link layer that uses MAC addresses for local network communication. Logical addressing is provided by IP addresses, allowing routing across multiple LANs via routers.

Data Link and Network Layers

The data link layer handles MAC‑based addressing within a LAN, while the network layer abstracts physical routes using IP addresses. Routers connect different LANs, forwarding packets based on destination IP.

Transport Layer: TCP vs UDP

TCP provides reliable, connection‑oriented communication with flow control, error recovery, and congestion control. UDP offers a lightweight, connection‑less service that only adds a minimal header for ports, length, and checksum.

TCP Header Structure

The TCP header is 20 bytes fixed plus optional fields. Key fields include source and destination ports, sequence and acknowledgment numbers, window size, and flags (SYN, ACK, FIN, etc.).

Reliable Transmission Mechanisms

TCP ensures reliability through several mechanisms:

Stop‑and‑wait (ARQ) : Send one segment, wait for acknowledgment before sending the next.

Sliding window : Allows multiple unacknowledged segments within a window size, improving throughput.

Timeout and retransmission : If an ACK is not received within a timeout, the segment is resent.

Cumulative and selective acknowledgments (SACK) : Reduce unnecessary retransmissions by acknowledging ranges of received data.

Flow Control and Congestion Control

Flow control prevents a fast sender from overwhelming a slow receiver by using the receiver’s advertised window size. Congestion control avoids network overload by adjusting the sender’s window based on packet loss and round‑trip time, employing algorithms such as slow start, congestion avoidance, fast retransmit, and fast recovery.

Connection Management

TCP establishes a connection using a three‑way handshake (SYN, SYN‑ACK, ACK) and terminates it with a four‑step handshake (FIN, ACK, FIN, ACK). These steps synchronize sequence numbers and ensure both sides agree on connection state.

UDP Characteristics

UDP’s 8‑byte header contains source port, destination port, length, and checksum. It offers low latency and low overhead, making it suitable for real‑time applications (e.g., video streaming, DNS) but provides no guarantees of delivery, ordering, or congestion control.

Advantages : Faster, lower overhead, supports broadcasting, and can handle high‑volume, loss‑tolerant traffic.

Disadvantages : No reliability, no congestion control, susceptible to packet loss.

Advanced Topics

Packet Fragmentation and Reassembly

Transport protocols split large data streams into smaller segments to fit the maximum transmission unit (MTU) of the underlying network. Over‑fragmentation increases header overhead, while under‑fragmentation can cause inefficiency.

Routing and Redundancy

Routers provide path redundancy; if one route fails, traffic can be rerouted through alternative paths, improving fault tolerance and load balancing.

Security Considerations

TCP’s connection‑oriented nature can be abused in SYN‑flood attacks, where an attacker sends many SYN packets with spoofed IPs, exhausting server resources. Mitigations include limiting half‑open connections, SYN cookies, and reducing timeout intervals.

Long‑Lived Connections

Keeping TCP connections open (persistent connections) reduces the overhead of repeated handshakes, improving performance for protocols like HTTP/1.1, but requires careful management to avoid resource exhaustion.

Practical Takeaways

Understanding the trade‑offs between TCP and UDP helps engineers choose the right protocol for a given application, balance reliability against latency, and implement appropriate flow and congestion control mechanisms.