Table of Contents
Two Different Models for Understanding Networks
In networking, the OSI model and the TCP/IP model are two different ways to describe how data moves from one device to another. They do not change how the network actually works. Instead, they provide different lenses to think about and organize networking functions.
The OSI model uses seven layers. The TCP/IP model uses fewer layers and is based directly on the real protocols used on the Internet. In this chapter, the focus is on how these models relate, where they differ, and why the TCP/IP model is usually preferred in practical work.
Layer Counts and Structures
The OSI model has seven layers. From bottom to top, these are Physical, Data Link, Network, Transport, Session, Presentation, and Application. Each of these has its own chapter, so we will not describe them in detail here.
The TCP/IP model is usually shown with four layers, sometimes five depending on the textbook. The four layer view is most common in practice:
| TCP/IP Layer | Typical OSI Equivalent Layers |
|---|---|
| Application | Application, Presentation, Session |
| Transport | Transport |
| Internet | Network |
| Network Access | Data Link, Physical |
In the TCP/IP model, several OSI layers are combined. Everything that deals with applications, formatting, and sessions is grouped into the single Application layer. Everything that deals with physical media and local delivery is grouped into the Network Access layer.
Important: The TCP/IP Application layer includes the functions of OSI layers 5, 6, and 7. The TCP/IP Network Access layer includes the functions of OSI layers 1 and 2.
Historical Background
The OSI model was defined as part of a formal standardization effort. It was meant to be a clean, ideal reference model for all kinds of networks. It describes functions in a very structured way, even if there is no real protocol that exactly matches each boundary.
The TCP/IP model grew directly out of the protocols that built the Internet, such as IP, TCP, and early application protocols. It was based on what actually worked in real networks. Because of this, the TCP/IP model is less strict and more practical, and it maps directly to widely used protocol suites.
Over time, TCP/IP protocols took over most real networks. The OSI protocol stack that was once planned did not become dominant. The OSI model remained valuable as a teaching and conceptual tool, but operational networks use TCP/IP as their foundation.
Conceptual vs Practical Focus
The OSI model is primarily a conceptual reference. It is helpful for learning, troubleshooting, and separating responsibilities, but it does not correspond exactly to real protocol implementations. For example, many modern application protocols combine presentation and application functions, instead of having a clean separation as OSI suggests.
The TCP/IP model is more directly tied to implementation. When someone says "Internet layer" in TCP/IP, they usually mean IP and related protocols. When they say "Transport layer," they usually mean TCP or UDP. These are real, widely deployed protocols, not just hypothetical examples.
Because of this practical focus, network engineers usually speak in TCP/IP terms for real designs and configurations, and use the OSI model as a neutral language to explain where a problem might live conceptually.
Mapping Common Protocols to Each Model
Even though this course covers many protocols later, it is useful here to see how they roughly fit in the two models. The table below uses the four layer TCP/IP model and the seven layer OSI model side by side.
| Protocol / Example | TCP/IP Layer | OSI Layer(s) |
|---|---|---|
| HTTP, HTTPS | Application | Application |
| DNS | Application | Application |
| SMTP, POP3, IMAP | Application | Application |
| SSH, Telnet | Application | Application |
| TLS (encryption) | Application | Presentation |
| TCP | Transport | Transport |
| UDP | Transport | Transport |
| IP (IPv4, IPv6) | Internet | Network |
| ICMP | Internet | Network |
| ARP | Network Access | Data Link |
| Ethernet | Network Access | Data Link and Physical |
| Wi Fi (802.11) | Network Access | Data Link and Physical |
Some OSI layers do not have a single clear real world protocol that sits only there. For example, presentation and session functions are often baked into application protocols or libraries. This is one reason the TCP/IP model merges them into the Application layer.
Main Differences in Layer Responsibilities
The most obvious difference between the two models is how they cut up responsibilities.
In OSI, the layers are more fine grained. Each of the seven layers is supposed to have a clear, distinct purpose. The three top layers are meant to handle the way applications talk to each other, the format of data, and how sessions are started and ended. In practice, real applications do not always follow this clean separation.
In TCP/IP, the Application layer is broader. Any function that deals with application level data, including formatting and sessions, is grouped there. So in TCP/IP, when we talk about Application layer protocols, we cover almost everything that is above the transport protocols.
Similarly, at the lower part of the stack, OSI splits physical signaling and link level framing into two layers. TCP/IP collects these into one Network Access layer, because from the Internet perspective, the exact physical and data link details do not matter. IP expects that something below it can send frames across a local link, whatever the medium is.
Remember: In TCP/IP, anything below IP is simply "Network Access," and anything above TCP or UDP is "Application." The OSI model uses more layers to describe those same zones in more detail.
Encapsulation View in Each Model
Both models describe encapsulation, but with different numbers of steps. In OSI, data moves from Application at the top down through Presentation and Session before it reaches the Transport layer, and then continues down until it is bits on the wire at the Physical layer.
In TCP/IP, the conceptual picture is shorter. Data moves from the Application layer directly down to Transport, then Internet, then Network Access. The principles of headers being added at each step, and removed in reverse order at the receiving side, are the same. The difference is only how many conceptual stages you pass through.
Later chapters will explain encapsulation in depth. For this chapter, it is enough to see that both models tell the same story, but OSI uses more intermediate steps, and TCP/IP uses fewer.
Why TCP/IP is Dominant Today
Modern networks, especially the Internet, are designed around the TCP/IP stack. Key reasons include simplicity, early adoption, and flexibility. The TCP/IP model matched the protocols that were already working and spreading, so it became the practical standard.
Network devices, operating systems, and applications are all built to speak TCP/IP. When you configure an IP address, a default gateway, or a DNS server, you are directly interacting with TCP/IP concepts, not OSI protocols.
The OSI model is still taught, because it gives a more detailed mental map and helps separate concerns. However, when you design, implement, or troubleshoot real networks, you normally think in terms of the TCP/IP layers and protocols.
Using Both Models Together
Even though they are different, you do not have to pick one model and abandon the other. In practice, you often use them side by side.
For high level learning and explanation, the OSI model helps you say where in the path a problem might occur, such as "layer 2 issue" or "layer 7 issue." For configuration and protocol details, the TCP/IP model tells you which real protocols and headers are involved, such as "IP at the Internet layer," or "TCP at the Transport layer."
A useful way to think about it is that the OSI model is a detailed map, and the TCP/IP model is a simplified map that lines up exactly with the roads you actually drive on. Both can describe the same journey, but with different levels of abstraction.
Key idea: OSI is a detailed reference for functions. TCP/IP is a practical stack based on real Internet protocols. They describe the same general path of data, but with different cuts and different focus.
Later chapters on the Internet layer, Transport layer, and Application layer will use the TCP/IP model directly and show how real networks behave inside this structure.