Understanding the Internet Protocol Suite: A Five‑Layer Model Overview

We use the Internet every day, yet few realize that billions of computers worldwide communicate by sending signals between network cards without knowing each other's physical locations.

The core of this global system is the Internet Protocol Suite, a collection of protocols that define how computers connect, address each other, and exchange data; understanding these protocols reveals the principles behind the Internet.

This note presents a concise framework of the suite, heavily simplified for clarity, to give a high‑level view of how the Internet is structured.

1. Overview – Five‑Layer Model The Internet is divided into several layers, each with its own function, similar to floors in a building. Users only see the top (application) layer, so to truly understand the Internet one must start from the lowest layer and work upward.

The bottom layer is the Physical Layer , the top is the Application Layer , and in between are the Link , Network , and Transport layers. The exact names are less important than the fact that the Internet is layered.

1.2 Layers and Protocols Each layer provides a specific function and relies on a set of shared rules called protocols .

2. Physical Layer This layer deals with the actual media—copper cables, fiber optics, wireless signals—that physically connect computers and transmit raw bits (0s and 1s).

3. Link Layer The link layer groups bits into frames. Ethernet, the dominant link‑layer protocol, defines a frame consisting of an 18‑byte header and a data payload (46–1500 bytes). The header contains source and destination MAC addresses, which are 48‑bit identifiers unique to each network interface.

MAC addresses are used for local delivery. Because Ethernet uses broadcast, a frame is sent to all devices on the same subnet; each device checks the destination MAC and discards the frame if it does not match.

When a host needs to know another host's MAC address, it uses the ARP (Address Resolution Protocol) to broadcast an IP‑to‑MAC query and receive a reply.

4. Network Layer MAC alone cannot distinguish different sub‑networks, so the network layer introduces IP addresses. IPv4 uses 32‑bit addresses, typically written as four decimal octets (e.g., 172.16.254.1). A subnet mask (e.g., 255.255.255.0) indicates which bits belong to the network portion.

Two IP addresses belong to the same subnet if an AND operation with the subnet mask yields identical results.

4.4 ARP Protocol ARP resolves an IP address to a MAC address within the same subnet by broadcasting a request; the host owning the IP replies with its MAC.

5. Transport Layer To differentiate multiple applications on the same host, the transport layer adds a port number (0–65535). A combination of IP address and port is called a socket .

5.1 UDP The User Datagram Protocol adds source and destination ports to the payload. UDP frames are simple, 8‑byte headers, but provide no delivery guarantees.

5.2 TCP The Transmission Control Protocol builds on UDP by adding acknowledgments, retransmissions, and ordering, ensuring reliable delivery at the cost of greater complexity.

6. Application Layer The highest layer defines the format of data for specific applications such as email, web, and FTP. Application data is placed in the payload of TCP (or UDP) segments.

In summary, the Internet can be understood as a five‑layer stack—Physical, Link, Network, Transport, and Application—each building on the services of the layer below while providing abstractions for the layer above.

Original source: http://tinyurl.com/6sjbcnj