OSI vs TCP/IP Model – Side-by-Side Comparison

1. Why Two Models Exist

Two conceptual frameworks dominate network education and professional practice: the OSI model (Open Systems Interconnection) and the TCP/IP model (also called the Internet model or DoD model). Both describe how data moves from one device to another across a network — but they were created with different goals, at different times, and for different audiences.

Understanding why two models exist — and what each is actually used for — prevents the common confusion of treating them as competing descriptions of the same thing. They are complementary: the OSI model provides a precise theoretical vocabulary for discussing network functions, while the TCP/IP model describes the actual protocol suite that runs the internet.

Related pages: OSI Layer Functions | Common Port Numbers | Layer Functions | Packet Flow / show ip route | Frame Forwarding / MAC Table

2. The OSI Model — Seven Layers

The OSI model divides network communication into seven distinct layers, each with a clearly defined responsibility. Each layer provides services to the layer above and relies on services from the layer below. This layered separation means a change at one layer (e.g., switching from copper to fibre at Layer 1) does not require changes at other layers — a principle called layer independence.

  OSI Model — 7 layers with mnemonics:

  Layer 7 │ Application  │ "All"
  Layer 6 │ Presentation │ "People"
  Layer 5 │ Session      │ "Seem"
  Layer 4 │ Transport    │ "To"
  Layer 3 │ Network      │ "Need"
  Layer 2 │ Data Link    │ "Data"
  Layer 1 │ Physical     │ "Processing"

  Top-down mnemonic (7→1): "All People Seem To Need Data Processing"
  Bottom-up mnemonic (1→7): "Please Do Not Throw Sausage Pizza Away"

3. The TCP/IP Model — Four Layers

The TCP/IP model (sometimes called the Internet model or DoD model) consolidates the OSI model's seven layers into four practical layers that directly correspond to how the TCP/IP protocol suite is implemented and used. It emerged from the ARPANET research that became the internet, and unlike the OSI model, it was defined alongside the actual protocols — not as a theoretical framework.

4. Layer Mapping — OSI to TCP/IP Side by Side

  OSI Model (7 layers)          TCP/IP Model (4 layers)
  ─────────────────────         ─────────────────────────
  7 │ Application  │ ─────┐
  6 │ Presentation │ ─────┤──► 4 │ Application     │
  5 │ Session      │ ─────┘
  4 │ Transport    │ ──────────► 3 │ Transport       │
  3 │ Network      │ ──────────► 2 │ Internet        │
  2 │ Data Link    │ ─────┐
  1 │ Physical     │ ─────┴────► 1 │ Network Access  │


  OSI Model (7 layers)          TCP/IP Model (5-layer variant)
  ─────────────────────         ───────────────────────────────
  7 │ Application  │ ─────┐
  6 │ Presentation │ ─────┤──► 5 │ Application     │
  5 │ Session      │ ─────┘
  4 │ Transport    │ ──────────► 4 │ Transport       │
  3 │ Network      │ ──────────► 3 │ Network (IP)    │
  2 │ Data Link    │ ──────────► 2 │ Data Link       │
  1 │ Physical     │ ──────────► 1 │ Physical        │

5. Why the OSI Model Is Still Taught

A natural question: if TCP/IP is what actually runs the internet, why is so much time spent studying the OSI model? The answer is that the OSI model provides something the TCP/IP model deliberately avoids — a precise, granular vocabulary for describing network functions that is independent of any specific protocol.

Five Reasons the OSI Model Remains Essential

OSI Layers in Troubleshooting

  Bottom-up troubleshooting approach (most efficient for physical problems):

  Layer 1 — Physical: Is the cable plugged in? Is the link LED lit?
  ↓ If Layer 1 OK...
  Layer 2 — Data Link: Is there a MAC address in the table? Is the VLAN correct?
  ↓ If Layer 2 OK...
  Layer 3 — Network: Is there an IP address? Can you ping the gateway?
  ↓ If Layer 3 OK...
  Layer 4 — Transport: Is the port open? Does telnet to port 80 connect?
  ↓ If Layer 4 OK...
  Layer 7 — Application: Is the service running? Are credentials correct?

  Top-down troubleshooting (useful when the application is the complaint):
  Start at Layer 7 (is the app responding?) and work down to Layer 1.

  Examples of layer-specific problems:
  Layer 1: broken cable, bad SFP, no link light, duplex mismatch
  Layer 2: incorrect VLAN, STP loop, duplicate MAC, missing ARP entry
  Layer 3: wrong IP subnet, missing route, wrong gateway, ACL blocking
  Layer 4: firewall blocking port, wrong port in config, SYN but no ACK
  Layer 7: wrong URL, expired certificate, misconfigured application

6. How Real Protocols Map to Both Models

Real protocols rarely respect model boundaries perfectly — many span multiple layers or are categorised differently depending on context. The table below shows exactly where the most important protocols sit in both models simultaneously.

7. Encapsulation and De-encapsulation — Both Models

Encapsulation is the process by which each layer adds its own header (and sometimes trailer) to the data passed down from the layer above, building up the complete PDU for transmission. De-encapsulation is the reverse — each layer at the receiver strips its header and passes the inner data upward.

This process is the same in both OSI and TCP/IP — the two models describe the same physical reality, just with different levels of granularity.

  Encapsulation at the sender (top to bottom):

  Application generates HTTP request: "GET /index.html HTTP/1.1"
       │
       │ Layer 7 (OSI App / TCP/IP App)
       ▼
  ┌─────────────────────────────────────────────────────────┐
  │  HTTP Data: "GET /index.html HTTP/1.1"                  │
  └─────────────────────────────────────────────────────────┘
       │ Layer 4 (Transport): TCP adds port numbers, seq#
       ▼
  ┌────────────────────────────────────────────────────────────────┐
  │  TCP Header │  HTTP Data                                       │
  │  Src:54321  │  "GET /index.html..."                            │
  │  Dst:80     │                        ← TCP Segment             │
  └────────────────────────────────────────────────────────────────┘
       │ Layer 3 (Network): IP adds source/destination IPs
       ▼
  ┌──────────────────────────────────────────────────────────────────────┐
  │  IP Header  │  TCP Header │  HTTP Data                               │
  │  Src:10.0.0.5│  Src:54321  │  "GET /index.html..."  ← IP Packet      │
  │  Dst:93.x.x.x│  Dst:80    │                                          │
  └──────────────────────────────────────────────────────────────────────┘
       │ Layer 2 (Data Link): Ethernet adds MAC addresses, FCS
       ▼
  ┌────────────────────────────────────────────────────────────────────────────┐
  │ Eth Header │  IP Header  │  TCP Header │  HTTP Data            │ FCS (CRC) │
  │ Src MAC    │  Src IP     │  Src Port   │  "GET /index.html..."  │           │
  │ Dst MAC    │  Dst IP     │  Dst Port   │           ← Ethernet Frame        │
  └────────────────────────────────────────────────────────────────────────────┘
       │ Layer 1 (Physical): Frame serialised to electrical/optical bits
       ▼
  10110001 01001100 10110010 ... (bits transmitted on the wire)

  De-encapsulation at the receiver: reverse process — each layer
  reads its header, processes it, and passes the inner data upward.

Encapsulation Summary Table

8. Network Devices and Their OSI Layers

Each type of network device operates at a specific OSI layer — the layer at which it reads, processes, and makes forwarding decisions. Understanding device-layer relationships is foundational to network design and is heavily tested on the CCNA.

9. OSI Upper Layers (5, 6, 7) — Are They Relevant Today?

One source of confusion in CCNA study is that OSI Layers 5 (Session), 6 (Presentation), and 7 (Application) are all collapsed into the single TCP/IP Application layer — and in practice, most modern protocols implement session, presentation, and application functions together in a single protocol stack. This has led some engineers to dismiss OSI upper layers as irrelevant. They are not — they remain analytically useful.

Layer 5 — Session

The Session layer manages the establishment, maintenance, and termination of communication sessions. In practice, session management is handled by:

• TLS/SSL — establishes and tears down secure sessions (handshake → data transfer → close_notify)
• SIP (Session Initiation Protocol) — explicitly manages VoIP call sessions (INVITE → 200 OK → BYE)
• RPC (Remote Procedure Call) — manages distributed application sessions
• SQL sessions — database connection establishment and teardown

Layer 6 — Presentation

The Presentation layer handles data translation between different formats and encryption. In modern networking:

• TLS encryption — encrypts data before handing to TCP (Presentation function)
• Data serialisation formats — JSON, XML, Protocol Buffers, ASN.1 (used in SNMP and certificates) — translate application data into a format for network transmission
• Compression — HTTP Content-Encoding (gzip, Brotli) compresses data before transmission
• Character encoding — ASCII, Unicode, UTF-8 translation

Layer 7 — Application

Layer 7 is the interface between the network and the application. It provides network services directly to user applications — HTTP gives a browser access to web content, DNS resolves names, SMTP transfers email. Unlike the lower layers, Layer 7 protocols are application-specific.

10. Summary — Key Differences and Practical Takeaways

  Practical summary for the CCNA exam:

  ✔ Use OSI layer numbers when:
    → Discussing what a device does ("Layer 3 switch", "Layer 2 loop")
    → Troubleshooting ("Layer 1 problem — check the cable")
    → Describing where a protocol operates ("BGP runs at Layer 3/4")
    → Security discussions ("Layer 7 firewall inspects HTTP content")
    → CCNA exam questions about layers, PDUs, and device behaviour

  ✔ Use TCP/IP model when:
    → Discussing actual protocol implementation
    → Describing how internet communication works in practice
    → Referring to the protocol stack (IP/TCP/HTTP)

  ✔ Both models agree on:
    → Transport layer = TCP / UDP
    → Network layer = IP (Layer 3)
    → These are the two layers that matter most for daily
      network engineering work

  ✔ Know the PDU names cold:
    Data → Segment/Datagram → Packet → Frame → Bits
    (Application/Presentation/Session → Transport → Network → Data Link → Physical)

See also: OSI Layer Functions | Common Port Numbers | Layer Functions | Packet Flow / show ip route | Frame Forwarding / MAC Table | Common Port Numbers

Test Your Knowledge — OSI vs TCP/IP Quiz