Two Models to Rule Them All
Networking is complex — data passes through many layers of hardware and software before reaching its destination. To make this complexity manageable, we use reference models that break the process into logical layers. There are two main models: the OSI model and the TCP/IP model.
The OSI Model
The Open Systems Interconnection (OSI) model was developed by the International Organization for Standardization (ISO) in 1984. It divides networking into 7 layers, each with a specific job:
┌─────────────────────────────────────────┐
│ Layer 7: Application │ ← User interfaces (HTTP, FTP, DNS)
├─────────────────────────────────────────┤
│ Layer 6: Presentation │ ← Data format, encryption, compression
├─────────────────────────────────────────┤
│ Layer 5: Session │ ← Managing connections between apps
├─────────────────────────────────────────┤
│ Layer 4: Transport │ ← End-to-end delivery (TCP, UDP)
├─────────────────────────────────────────┤
│ Layer 3: Network │ ← Routing & IP addressing
├─────────────────────────────────────────┤
│ Layer 2: Data Link │ ← MAC addresses, frames, switching
├─────────────────────────────────────────┤
│ Layer 1: Physical │ ← Cables, signals, bits on the wire
└─────────────────────────────────────────┘
Mnemonic: "Please Do Not Throw Sausage Pizza Away" (Physical, Data Link, Network, Transport, Session, Presentation, Application) — from bottom to top.
How the Layers Work Together
When you send data, it flows down through the layers (encapsulation). Each layer adds its own header (and sometimes trailer) to the data. When the data arrives at the destination, it flows back up through the layers (de-encapsulation), with each layer stripping off its header.
SENDER RECEIVER
────── ───────
Application ──→ Data Data ──→ Application
Presentation ──→ [Header] + Data [Header] + Data ──→ Presentation
Session ──→ [Header] + ... [Header] + ... ──→ Session
Transport ──→ Segment Segment ──→ Transport
Network ──→ Packet Packet ──→ Network
Data Link ──→ Frame Frame ──→ Data Link
Physical ──→ Bits ──────────────→ Bits ──→ Physical
Think of it like putting a letter in an envelope, then in a package, then in a shipping box. Each layer adds its own packaging. The receiving side unpacks each layer in reverse order.
The TCP/IP Model
The TCP/IP model is the practical model used on the real internet. It simplifies the OSI model into 4 layers:
┌─────────────────────────────────────────┐
│ Application │ ← OSI Layers 5-7 combined
├─────────────────────────────────────────┤
│ Transport │ ← TCP, UDP
├─────────────────────────────────────────┤
│ Internet │ ← IP, routing
├─────────────────────────────────────────┤
│ Network Access (Link) │ ← OSI Layers 1-2 combined
└─────────────────────────────────────────┘
The TCP/IP model is what the internet actually uses. The OSI model is more of a teaching tool — it's great for understanding concepts, but real-world protocols don't map neatly to all 7 layers.
OSI vs TCP/IP
OSI Model TCP/IP Model Real Protocols
───────────────── ────────────────── ──────────────────
Application ┐
Presentation ├─→ Application HTTP, DNS, FTP, SMTP
Session ┘
Transport → Transport TCP, UDP
Network → Internet IP, ICMP, ARP
Data Link ┐
Physical ┘─→ Network Access Ethernet, Wi-Fi
Both models are important to understand. The OSI model helps you think about networking in structured layers. The TCP/IP model shows you how the internet actually works.