Table of Contents
Overview
The TCP/IP model is the practical foundation of how the internet works. While the OSI model is mostly used for learning and discussion, TCP/IP describes how real-world protocols are organized and how devices actually communicate.
In this chapter you will see the big picture of TCP/IP as a model. Later chapters in this section will focus on each of its layers in detail, so here we keep to the overall structure and ideas.
Historical Context
TCP/IP was created as part of ARPANET, a research network funded by the United States government, which later evolved into the modern internet. Its main design goal was to allow different kinds of networks and computers to communicate reliably with one another.
Instead of describing a theoretical seven layer structure, the creators grouped related functions into fewer, more practical layers. Over time, TCP/IP and its protocols became the standard that all internet connected devices follow today.
Layer Structure of the TCP/IP Model
The TCP/IP model is usually shown with four layers. Each layer groups a set of protocols that perform related functions and that rely on the services of the layer below.
A common four layer view looks like this:
| TCP/IP Layer | Typical OSI Layers (rough mapping) | Main Role |
|---|---|---|
| Application | Application, Presentation, Session | Network services used by applications |
| Transport | Transport | End to end communication between hosts |
| Internet | Network | Addressing and routing of packets |
| Network Access | Data Link, Physical | Access to physical network media |
This table is only a comparison aid. The TCP/IP model stands on its own. It is not just a compressed OSI model, it is defined by the actual protocols that use it.
Important: The TCP/IP model is usually represented with 4 layers. Some sources show a 5 layer variation that splits the Network Access layer into separate Data Link and Physical layers, but the 4 layer view is the classic TCP/IP description.
Relationship Between TCP/IP and Protocols
The name TCP/IP comes from two key protocols:
- Transmission Control Protocol (TCP)
- Internet Protocol (IP)
These are not the only protocols in the model, but they are historically central. In the TCP/IP model:
- The Internet layer includes IP as its core protocol.
- The Transport layer includes TCP and also UDP.
- The Application layer includes many protocols, such as HTTP, DNS, and others.
- The Network Access layer includes technologies like Ethernet and Wi Fi, which will be mapped to other chapters.
Each protocol is designed to operate at a specific layer, use services from the layer below, and offer services to the layer above. For example, HTTP uses TCP, TCP uses IP, and IP uses a link technology such as Ethernet.
Encapsulation in the TCP/IP Model
When data moves from an application on one host to an application on another host, it is wrapped step by step as it passes down the TCP/IP layers. Each layer adds its own header information. This process is encapsulation in the context of TCP/IP.
Conceptually:
- An application creates some data.
- The Transport layer adds a transport header.
- The Internet layer adds an IP header.
- The Network Access layer adds link specific information and sends bits over the medium.
On the receiving host, the reverse process happens. Each layer reads and removes its own header and passes the remaining data up to the next layer.
You will study encapsulation mechanics and detailed headers in other chapters, so here it is enough to understand that the TCP/IP model provides the structure that defines which layer adds which information and why.
TCP/IP as an Implementation Model
One key difference from OSI is that TCP/IP is tied directly to real implementations. Operating systems, routers, and network devices are built to support TCP/IP protocols. When you configure an IP address, a default gateway, or a DNS server on your computer, you are directly working with the TCP/IP model.
TCP/IP also defines how devices should behave when they:
- Forward packets across networks.
- Handle congestion.
- Fragment and reassemble packets.
- Recover from errors.
Many of these behaviors are documented in technical documents called RFCs, which are the formal specifications for internet protocols. The TCP/IP model gives a layered framework in which these RFC defined protocols fit together.
Variations of the Model
Different textbooks and vendors sometimes draw the TCP/IP model with slight differences. The most common variations are:
- 4 layer model, which you will use in this course.
- 5 layer model, which explicitly shows a Physical layer below the Data Link part of Network Access.
- Some diagrams use different names such as Link layer instead of Network Access, or Internet Protocol layer instead of Internet layer.
The important thing is not the label but the idea of grouping protocols by function:
- Local network access and framing at the bottom.
- Logical addressing and routing above that.
- Reliable or unreliable end to end delivery above that.
- Application services at the top.
Whenever you see a picture of TCP/IP with slightly different names or an extra split at the bottom, look at the functions that are included rather than focusing only on the number of layers.
How TCP/IP and OSI Work Together Conceptually
Although TCP/IP and OSI are two different models, networking professionals often use both ideas at the same time. They might say that an issue is at the "Layer 3" level according to OSI, but they will be troubleshooting an IP problem in the Internet layer of TCP/IP.
In practice:
- The OSI model is used as a teaching and troubleshooting language.
- The TCP/IP model represents how protocols and software are actually structured and implemented.
Later chapters will compare the two models explicitly, and map specific protocols to layers. For now, it is enough to understand that TCP/IP is the practical standard that drives the internet, and that its four layer structure is the backbone of modern networking.