# TCP/IP Model

Let's learn about the TCP/IP model. It's also a framework similar to the OSI model but does some things differently in terms of structure, protocols, and how layers are defined.

The **TCP/IP model** is a more simplified and practical approach to networking. It was developed by the Department of Defense in the 1970s for the ARPANET, the precursor to the modern internet. While OSI is a conceptual model used to understand networking and is often used in educational contexts, the TCP/IP model reflects the real-world implementation of networking protocols.

The TCP/IP model has **four layers**:

1. **Application Layer**: This is where high-level protocols like HTTP, FTP, and SMTP operate. It's the layer where user applications interact with the network.
2. **Transport Layer**: This layer is responsible for providing communication services between systems. The most important protocols in this layer are TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). TCP provides reliable communication, while UDP is used for low-latency applications that can tolerate some data loss.
3. **Internet Layer**: The primary protocol in this layer is IP (Internet Protocol). It's responsible for routing packets of data from the source to the destination across different networks. This is where IP addressing and routing protocols like ICMP (Internet Control Message Protocol) come into play.
4. **Network Access Layer (Link Layer)**: This layer corresponds to the physical network hardware and protocols, like Ethernet or Wi-Fi, and is responsible for moving data across the physical network. It handles framing and addressing within the local network.

#### Key Differences Between TCP/IP and OSI:

* **Layer Count**: The TCP/IP model has four layers, whereas the OSI model has seven layers. TCP/IP merges the OSI's Presentation and Session layers into its Application layer, making it more concise.
* **Protocol Focus**: The OSI model is abstract and doesn't specify particular protocols for each layer, while the TCP/IP model was built specifically around the protocols that were used in the early stages of networking, particularly TCP and IP.

## **Real-World Use**:

The TCP/IP model was created to solve practical networking problems and is the foundation of the internet. In contrast, OSI was designed as a theoretical framework, and while its concepts are still useful for understanding networking, the TCP/IP model is more commonly used in practice.

This diagram will help illustrate the structural and functional differences between them.

<figure><img src="/files/0ux85BLOqM9iemjp5hnr" alt=""><figcaption></figcaption></figure>

From the image shown above comparing the OSI and TCP/IP models, you can see how the **Application**, **Presentation**, and **Session** layers from the OSI model are merged into one single layer called the **Application layer** in the TCP/IP model. This simplification was made to streamline the structure while still covering all the necessary functions for network communication. Additionally, you will notice that the **Network layer** in OSI is renamed to the **Internet layer** in TCP/IP, reflecting the role of IP (Internet Protocol) and its focus on routing and addressing on the internet.

Moreover, the **Data Link layer** and **Physical layer** in the OSI model are combined into a single layer called the **Network Access layer** in the TCP/IP model. This change was made because the early design of ARPANET, the precursor to the internet, didn’t require the detailed separation of these layers. The focus was on providing a practical framework for network communication.

The reason for this restructuring is that when ARPANET, the first version of the internet, was developed, TCP/IP emerged as a more practical, accurate version of the layered network model. While the theoretical foundations of the OSI model continue to influence network design, the TCP/IP model was developed by the Department of Defense to be more practical, structured, and directly applicable to real-world networking.

The fundamental concept of layers—each providing distinct functions in the communication process—remains similar to what we learned from the OSI model, but the TCP/IP model represents a more efficient and streamlined approach to achieving these same goals in modern networking.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://handbook.ncateam.xyz/fundamentals/networking/networking-models/tcp-ip-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.