The OSI Model: 7 Layers of Network Communication

The International Letter Analogy

You want to send a letter to a friend in Japan. Here is what actually happens: you write the letter (create the content), fold it and seal it in an envelope (package it), write the address on the outside (add routing information), drop it at the post office (hand it to a transport system), it gets sorted and transported across countries (network routing), passes through customs (security and protocol checking), gets delivered to their local post office (local delivery), and finally your friend opens it and reads it (decapsulation and consumption).

Every step adds something. Every step has a defined job. No step needs to know the details of other steps — the postal worker does not read your letter, and you do not know which aircraft your letter flew on. This separation of concerns is the genius of the OSI model.

---

Why the OSI Model Was Created

In the 1970s, every computer manufacturer had its own proprietary networking protocols. IBM's network equipment only worked with IBM computers. DEC's only worked with DEC. This was a business advantage for vendors but a nightmare for customers who needed interoperability.

The International Organization for Standardization (ISO) developed the OSI (Open Systems Interconnection) model in 1984 as a conceptual framework that:

• Standardizes how different systems communicate
• Enables interoperability between equipment from different vendors
• Simplifies troubleshooting — if something breaks, you know which layer to inspect
• Allows independent development — improving one layer does not require rewriting all others

The OSI model does not describe actual protocols (TCP/IP does that). It describes what needs to happen at each conceptual stage of communication.

---

The 7 Layers — Top to Bottom

Mnemonic (Layer 7 to Layer 1): "All People Seem To Need Data Processing"

Mnemonic (Layer 1 to Layer 7): "Please Do Not Throw Sausage Pizza Away"

---

Layer 7 — Application Layer

What it does: Provides network services directly to user applications. This is where user-facing protocols live.

Not the application itself — it is the interface between your application and the network. When Chrome wants to load a web page, it uses HTTP at Layer 7.

Protocols: HTTP, HTTPS, FTP, SMTP, POP3, IMAP, DNS, SSH, Telnet

Devices: None specific — this is software/application level

Real analogy: You write the content of your letter in English

PDU (Protocol Data Unit): Data

---

Layer 6 — Presentation Layer

What it does: Translates, encrypts, and compresses data. Ensures data from the sender's application layer can be read by the receiver's application layer.

Handles: Character encoding (ASCII vs Unicode), encryption (SSL/TLS begins here), data compression (JPEG, MPEG compression formats)

Protocols: SSL/TLS (partially), JPEG, PNG, MPEG, ASCII, Unicode

Real analogy: You decide to write in a language both of you understand, and you seal the envelope for privacy

PDU: Data

---

Layer 5 — Session Layer

What it does: Establishes, manages, and terminates sessions (ongoing conversations) between applications. Handles session checkpoints for resuming interrupted transfers.

Responsible for: Session establishment, maintenance, and termination. When you log into a website, a session is created. When you log out, it is terminated.

Protocols: NetBIOS, RPC (Remote Procedure Call), PPTP

Real analogy: The formality of beginning a letter ("Dear Friend") and ending it ("Yours sincerely") — establishing and closing the communication context

PDU: Data

---

Layer 4 — Transport Layer

What it does: Provides reliable (or fast) end-to-end data delivery. Segments large data into smaller pieces, reassembles them at the destination, handles error recovery and flow control.

Two main protocols:

• TCP — reliable, ordered, connection-oriented (like certified mail)
• UDP — fast, connectionless, no guarantee (like a postcard)

Protocols: TCP, UDP

Devices: Firewalls (stateful), load balancers

Real analogy: The post office decides whether to use standard mail or registered mail with tracking

PDU: Segment (TCP) / Datagram (UDP)

---

Layer 3 — Network Layer

What it does: Handles logical addressing (IP addresses) and routing — finding the best path across multiple networks from source to destination.

Responsible for: IP addressing, routing between networks, fragmentation (breaking packets when they exceed path MTU)

Protocols: IP (IPv4, IPv6), ICMP, OSPF, BGP, ARP (debated — some say Layer 2.5)

Devices: Routers, Layer 3 switches

Real analogy: The address on your envelope — the city, country, and ZIP code that gets it routed to the right country and city

PDU: Packet

---

Layer 2 — Data Link Layer

What it does: Handles physical addressing (MAC addresses) and reliable node-to-node delivery on the same local network. Detects and sometimes corrects errors in Layer 1 transmission.

Two sublayers:

• LLC (Logical Link Control): flow control and error checking
• MAC (Media Access Control): hardware addressing and media access

Protocols: Ethernet, Wi-Fi (802.11), PPP, ARP, VLAN (802.1Q)

Devices: Switches, bridges, wireless access points

Real analogy: The specific street address on your envelope — which house on which street within the city to deliver to

PDU: Frame

---

Layer 1 — Physical Layer

What it does: Transmits raw bits (1s and 0s) over a physical medium. Defines voltages, cable types, connector types, pin layouts, radio frequencies.

Responsible for: Bit timing, signal encoding, transmission rate, physical connector specifications

Standards: Ethernet physical specs (Cat5e, Cat6, fiber), Wi-Fi radio specifications, Bluetooth

Devices: Hubs, repeaters, cables, connectors, NICs (physical component)

Real analogy: The actual truck, plane, or ship that physically carries your letter from one country to another

PDU: Bits

---

The Complete OSI Reference Table

---

Encapsulation and Decapsulation

When data travels down the OSI model (sender side), each layer adds its own header — this is called encapsulation:

When data travels up the OSI model (receiver side), each layer strips its own header — this is decapsulation. The receiver's Layer 2 reads and removes the Ethernet header. Layer 3 reads and removes the IP header. Layer 4 reads and removes the TCP header. Layer 7 receives the original data.

---

Common Protocol Placement Questions

The OSI model's real value is not memorizing layers — it is having a common vocabulary. When a network engineer says "the problem is at Layer 3," everyone knows to look at IP routing. That shared language saves enormous time during troubleshooting.