Four Layers, Not Seven
The TCP/IP model — also called the Internet model or the DoD model — emerged from the ARPANET research that became the internet. Unlike the OSI model, which was designed as an abstract framework by committee, TCP/IP was developed alongside real, working protocols. The result is a leaner four-layer model that reflects how internet protocols are actually structured and implemented.
The four layers from bottom to top are: Link, Internet, Transport, and Application. Each layer has a clear, focused responsibility. The model is defined across numerous IETF RFCs rather than a single document — TCP in RFC 793, IP in RFC 791, and so on. Every device connected to the internet implements this stack, making it the most widely deployed protocol architecture in history.
The TCP/IP model won over OSI for a pragmatic reason: it was already implemented and working when OSI was still being standardized. The internet ran on TCP/IP, and network effects made it the de facto standard. OSI remained influential as a conceptual framework and troubleshooting vocabulary, but TCP/IP protocols dominate every layer of real-world networks.
The Four Layers Explained
| Layer | Name | Key Protocols |
|---|---|---|
| 4 (top) | Application | HTTP, HTTPS, DNS, SMTP, FTP, SSH, DHCP, SNMP |
| 3 | Transport | TCP, UDP, SCTP |
| 2 | Internet | IPv4, IPv6, ICMP, ARP, IPsec |
| 1 (bottom) | Link | Ethernet (802.3), Wi-Fi (802.11), PPP, DSL, fiber optic |
The Link layer (sometimes called the Network Access or Network Interface layer) handles transmission on the specific physical medium — copper, fiber, or radio waves. It deals with MAC addresses, framing, and the hardware-level details that vary between Ethernet, Wi-Fi, and other technologies. This layer corresponds to OSI Layers 1 and 2 combined.
The Internet layer provides logical addressing and routing using IP addresses. It is responsible for getting packets from any source to any destination across multiple networks, regardless of what Link layer technologies are used along the way. IP is the universal glue — it works over any Link layer technology, which is why the same IP packet can travel over Ethernet, Wi-Fi, and fiber segments on its path across the internet.
The Transport layer provides end-to-end communication between applications. TCP provides reliable, ordered, connection-oriented delivery with flow control and congestion control. UDP provides fast, connectionless delivery without those guarantees. Port numbers at this layer identify which application should receive each packet, allowing a single host to run many services simultaneously.
The Application layer encompasses everything above Transport — all the protocols that applications use to communicate. HTTP for web, SMTP for email, DNS for name resolution, SSH for secure remote access. This layer combines what OSI splits into Session (Layer 5), Presentation (Layer 6), and Application (Layer 7). In practice, modern application protocols handle their own session management and encryption (TLS) without relying on separate protocol layers.
TCP/IP vs OSI: Layer Mapping
| OSI Layer | OSI Name | TCP/IP Layer | TCP/IP Name |
|---|---|---|---|
| 7 | Application | 4 | Application |
| 6 | Presentation | ||
| 5 | Session | ||
| 4 | Transport | 3 | Transport |
| 3 | Network | 2 | Internet |
| 2 | Data Link | 1 | Link |
| 1 | Physical |
Why the TCP/IP Model Won
OSI and TCP/IP were developed concurrently in the 1970s and 1980s, and for a time there was genuine competition between them. OSI had governmental and telecommunications industry backing in Europe; TCP/IP had ARPANET and the growing US academic internet. The decisive factor was timing: by the time OSI protocols were fully standardized in the late 1980s and early 1990s, TCP/IP was already widely deployed and battle-tested. Switching would have required replacing working infrastructure.
TCP/IP also had practical advantages: it was simpler, it ran on ordinary computers rather than requiring specialized hardware, its specifications were freely available as IETF RFCs, and it had a large community of implementations to work out bugs. OSI protocols were theoretically more complete but suffered from complexity and late arrival. The internet's explosive growth in the early 1990s cemented TCP/IP as the permanent winner.
Encapsulation: How Data Moves Down the Stack
When an application sends data, it moves down the TCP/IP stack before being transmitted, with each layer adding its own header (and in the case of the Link layer, a trailer). This process is called encapsulation.
Starting from the Application layer: your browser creates an HTTP request. The Transport layer wraps it in a TCP segment, adding a TCP header with source and destination port numbers, sequence numbers, and flags. The Internet layer wraps the TCP segment in an IP packet, adding an IP header with source and destination IP addresses and TTL. The Link layer wraps the IP packet in an Ethernet frame, adding a frame header with MAC addresses and a trailer with a CRC checksum.
At the receiving end, the process reverses — de-encapsulation. The Link layer strips the Ethernet frame, the Internet layer strips the IP header, the Transport layer strips the TCP header and reassembles segments in order, and the Application layer receives the original HTTP data. Each layer only reads and removes the header added at its own level; the layers above are opaque to it.
Frequently Asked Questions
What are the 4 layers of the TCP/IP model?
From top to bottom: Application (HTTP, DNS, SMTP, SSH), Transport (TCP, UDP), Internet (IP, ICMP), and Link (Ethernet, Wi-Fi). Each layer encapsulates the one above it when sending and strips its header when receiving.
How does TCP/IP differ from OSI?
TCP/IP has 4 layers; OSI has 7. TCP/IP's Link layer combines OSI's Physical and Data Link layers. TCP/IP's Application layer combines OSI's Session, Presentation, and Application layers. TCP/IP was built alongside real protocols; OSI was a theoretical framework.
What layer is IP at in TCP/IP?
IP operates at the Internet layer of the TCP/IP model — the second layer from the bottom, corresponding to OSI Layer 3. It handles logical addressing and packet routing between networks.
What is encapsulation in networking?
Encapsulation is wrapping data with headers as it moves down the protocol stack. Each layer adds its own header — TCP adds a transport header, IP adds a network header, Ethernet adds a frame header. The receiving side strips each header at the corresponding layer.
Which model do real networks use?
Real networks use the TCP/IP model. OSI is a conceptual reference framework used for education and troubleshooting, but all actual internet protocols are defined and implemented according to the TCP/IP architecture documented in IETF RFCs.
What is the link layer in TCP/IP?
The Link layer is the bottom layer of TCP/IP, handling physical transmission on a specific network medium. It combines OSI Layers 1 and 2, dealing with MAC addresses, framing, and the physical characteristics of Ethernet, Wi-Fi, fiber, and other transmission technologies.