What are the OSI and TCP/IP models?

Question

IT Interview Practice · Accepted Answer

Both are **layered models** that describe how network communication is organized: each layer handles one concern and talks only to the layers directly above and below it. The **OSI model** is a 7-layer conceptual reference; the **TCP/IP model** is the 4-layer model the real internet actually runs on. They map onto each other:

```text
   OSI (7 layers, conceptual)          TCP/IP (4 layers, practical)      Examples
 ┌──────────────────────────┐        ┌──────────────────────────┐
 │ 7 Application            │        │                          │
 │ 6 Presentation          ─┼──────▶ │ Application              │  HTTP, DNS, TLS
 │ 5 Session               ─┘        │                          │
 ├──────────────────────────┤        ├──────────────────────────┤
 │ 4 Transport              │──────▶ │ Transport                │  TCP, UDP
 ├──────────────────────────┤        ├──────────────────────────┤
 │ 3 Network                │──────▶ │ Internet                 │  IP, ICMP
 ├──────────────────────────┤        ├──────────────────────────┤
 │ 2 Data Link             ─┼──────▶ │ Link (Network Access)    │  Ethernet, Wi-Fi,
 │ 1 Physical              ─┘        │                          │  ARP, cables
 └──────────────────────────┘        └──────────────────────────┘
```

The key idea is **encapsulation**: as data goes down the stack on the sender, each layer wraps it with its own header (HTTP payload → TCP segment → IP packet → Ethernet frame); on the receiver it travels back up, each layer stripping its header. This is why you can swap Wi-Fi for Ethernet without changing your HTTP code — the layers are independent.

For developers, the layers you touch daily are **Application** (HTTP, DNS), **Transport** (TCP vs UDP — ports, reliability), and **Internet** (IP addresses, routing). The lower link/physical layers are handled by the OS and hardware.

## Why it matters

Interviewers use this question to check whether you think in terms of a **structured stack** rather than a vague blob of "the network." Knowing which layer a concept lives on — a port is Transport, an IP address is Internet, a certificate is Application — lets you reason about problems precisely and place any new technology on the map. It's also the shared vocabulary the rest of networking is built on: TCP, IP, TLS, and load balancers are all described by which layer they operate at.

Why it matters

Related questions