Core Network Protocols Explained

The Role of the Transport Layer: TCP vs. UDP

The Network Layer provides host-to-host delivery, but the Transport Layer provides process-to-process delivery. Think of the IP address as the mailing address of an apartment building, and the port number used by the Transport Layer as the specific apartment number. This allows multiple network applications (e.g., a web browser, an email client, a game) to run on the same computer simultaneously.

The two primary protocols at this layer offer a fundamental trade-off: reliability versus speed. The following animated video provides an excellent high-level comparison between them.

As you saw, TCP and UDP serve very different purposes. Let's formalize their differences, as this comparison is a classic GATE topic.

Deep Dive: TCP Connection Establishment (The 3-Way Handshake)

TCP's reliability begins with establishing a robust, virtual circuit between the client and server. This is achieved through a process known as the three-way handshake. Its purpose is to synchronize the sequence and acknowledgment numbers on both sides, ensuring that both client and server are ready to communicate.

The following video provides a detailed, step-by-step walkthrough of this process, including the specific flags and numbers exchanged.

Let's summarize this critical process. Assume the client chooses an Initial Sequence Number (ISN) of $X$ and the server chooses an ISN of $Y$.

Step 1: Client sends SYN
The client wants to establish a connection. It sends a TCP segment to the server with:

• SYN flag set to 1 (indicating a request to synchronize).
• Seq number set to a random initial value, $X$.
  • Client -> Server: SYN=1, Seq=X

Step 2: Server sends SYN-ACK
The server receives the request. If it's willing to connect, it responds with a segment that both acknowledges the client's request and sends its own synchronization request.

• SYN flag set to 1.
• ACK flag set to 1.
• Seq number set to its own random initial value, $Y$.
• Ack number set to $X+1$. This tells the client, "I have received all your bytes up to sequence number $X$. I am now expecting the byte with sequence number $X+1$."
  • Server -> Client: SYN=1, ACK=1, Seq=Y, Ack=X+1

Step 3: Client sends ACK
The client receives the server's response. The connection is now established from its perspective. It sends a final segment to acknowledge the server's SYN packet.

• ACK flag set to 1.
• Seq number set to $X+1$.
• Ack number set to $Y+1$. This tells the server, "I have received your synchronization request. I am now expecting the byte with sequence number $Y+1$."
  • Client -> Server: ACK=1, Seq=X+1, Ack=Y+1

At this point, the connection is fully established, and both sides can begin sending data. This handshake ensures that both parties have agreed to communicate and have synchronized their starting sequence numbers.

Supporting Protocols: ARP and ICMP

While TCP and UDP operate at the Transport Layer, there are other crucial protocols that support the internet's infrastructure, primarily at the Network and Data Link layers.

Address Resolution Protocol (ARP)

ARP solves a fundamental problem: how to bridge the gap between Layer 3 (logical IP addresses) and Layer 2 (physical MAC addresses).

Imagine your computer (Host A) wants to send a packet to your friend's computer (Host B) on the same local network (LAN).

• Your application knows Host B's IP address (e.g., 192.168.1.10).
• However, to send an Ethernet frame on the local network, your network card needs Host B's physical MAC address (e.g., 00:1A:2B:3C:4D:5E).

How do you find the MAC address corresponding to a known IP address? This is ARP's job.

The ARP Process:

1. Check Cache: Host A first checks its local ARP cache, a table that stores recent IP-to-MAC address mappings.
2. Broadcast Request: If the mapping is not in the cache, Host A broadcasts an ARP Request packet to every device on the LAN. The message is essentially, "Who has the IP address 192.168.1.10? Please send me your MAC address."
3. Unicast Reply: All devices on the LAN receive the request, but only Host B recognizes its own IP address. Host B sends an ARP Reply directly (unicast) to Host A. The message says, "I have IP 192.168.1.10, and my MAC address is 00:1A:2B:3C:4D:5E."
4. Update Cache and Send: Host A receives the reply, updates its ARP cache with the new mapping, and can now encapsulate the IP packet in an Ethernet frame addressed to Host B's MAC address and send it.

In short, ARP translates a Layer 3 IP address into a Layer 2 MAC address for communication within a local network.

Internet Control Message Protocol (ICMP)

ICMP is the diagnostic and error-reporting protocol for IP. When something goes wrong in the network—a router is down, a host is unreachable—IP itself has no way to report the error back to the source. ICMP fills this gap. It's a network-layer protocol used by network devices to send control messages.

You have likely used ICMP without realizing it. The two most famous uses are:

1. ping Utility: This tool checks if a host is reachable. It works by sending an ICMP Echo Request message to the destination IP. If the destination is reachable, it replies with an ICMP Echo Reply message. If you get a reply, you know the host is online and there is a path to it.

2. traceroute (or tracert on Windows) Utility: This tool maps the route (the sequence of routers) a packet takes to a destination. It cleverly uses ICMP Time Exceeded messages. traceroute sends packets with a Time-To-Live (TTL) value starting at 1. The first router decrements the TTL to 0, discards the packet, and sends back an ICMP Time Exceeded message. traceroute records this router's IP. It then sends a packet with TTL=2, which makes it to the second router, and so on, building a map of the path.

Other important ICMP messages include:

• Destination Unreachable: Sent by a router if it cannot find a path to the destination.
• Redirect: Sent by a router to inform a host of a better, more direct route to a destination.

In essence, ICMP provides feedback about network operations and is the foundation for network diagnostic tools.

Conclusion

In this lesson, we moved up to the Transport Layer and also explored key supporting protocols, bridging the gap between network-level routing and application-level communication.

Here are your key takeaways:

• TCP vs. UDP: TCP provides reliable, ordered, and connection-oriented communication, essential for applications like web and email. UDP offers a fast, low-overhead, but unreliable connectionless service, suitable for real-time applications like streaming and gaming.
• TCP 3-Way Handshake: This fundamental process (SYN, SYN-ACK, ACK) establishes a reliable connection by synchronizing sequence numbers between a client and a server before any data is transferred.
• ARP: The Address Resolution Protocol is the essential glue between Layer 3 and Layer 2 on a local network, translating known IP addresses into the physical MAC addresses needed for frame delivery.
• ICMP: The Internet Control Message Protocol acts as the network's feedback mechanism, reporting errors (like Destination Unreachable, Time Exceeded) and enabling diagnostic tools like ping and traceroute.

We have now seen how connections are established. In our next lesson, we will delve deeper into how TCP maintains reliability during data transfer, focusing on its mechanisms for flow control (sliding window) and congestion control (slow start, AIMD). We will also ascend to the final layer of the network stack, the Application Layer, and examine protocols like DNS, HTTP, and FTP that power the services we use daily.