The OSI (Open Systems Interconnection) model divides network communication into seven abstracted layers, from physical transmission at Layer 1 to application-level services at Layer 7. Each layer provides services to the layer above and relies on services from the layer below, enabling modularity and independent protocol design. This abstraction is fundamental to understanding how diverse networking technologies coexist and interoperate.
Study each layer with concrete examples of protocols (e.g., Ethernet at Layer 2, IP at Layer 3, TCP at Layer 4). Map real protocols to their layers to build intuition.
Networking is enormously complex — signals travel over copper, fiber, and radio; data must be addressed, routed, error-checked, encrypted, and delivered to the right application. The OSI model tames this complexity by dividing the problem into seven layers, each responsible for one well-defined aspect of communication. The key insight is that each layer only interacts with the layers directly above and below it, so you can change how one layer works (say, switching from Ethernet to Wi-Fi at Layer 2) without rewriting everything above it.
The layers, from bottom to top, are: Physical (Layer 1) handles raw bit transmission over a medium — voltage levels, light pulses, radio frequencies. Data Link (Layer 2) frames those bits into structured units and handles hop-by-hop delivery between directly connected devices, using MAC addresses; Ethernet lives here. Network (Layer 3) introduces logical addressing (IP addresses) and routing across multiple hops. Transport (Layer 4) provides end-to-end communication — TCP gives reliable, ordered delivery while UDP gives fast, connectionless delivery. Session (Layer 5) manages dialog control between applications. Presentation (Layer 6) handles data format translation, encryption, and compression. Application (Layer 7) is where user-facing protocols like HTTP, DNS, and SMTP operate.
A useful way to internalize this is to trace what happens when you load a webpage. Your browser (Layer 7) constructs an HTTP request. That request gets encapsulated — each layer wraps it with its own header as it travels down the stack. The transport layer adds a TCP header with port numbers, the network layer adds an IP header with source and destination addresses, the data link layer adds an Ethernet frame with MAC addresses, and the physical layer converts it all to electrical signals on the wire. At the receiving end, each layer strips off its corresponding header and passes the payload up. This process of encapsulation and de-encapsulation is the mechanism that makes layered independence possible.
In practice, the OSI model is more of a teaching and troubleshooting framework than a literal implementation guide. The internet actually runs on the simpler TCP/IP model, which collapses Layers 5–7 into a single Application layer and merges Layers 1–2 into a Network Access layer. But the OSI model's vocabulary is universal: when a network engineer says "this is a Layer 3 problem," everyone immediately knows the issue involves IP addressing or routing, not cabling or application bugs. That shared language for isolating where in the stack a problem lives is the model's enduring practical value.
This is a foundational topic with no prerequisites.
No prerequisites — this is a starting point.