The TCP/IP Model

The TCP/IP model is the practical counterpart to OSI and a common interview compare-and-contrast: "difference between OSI and TCP/IP" is asked frequently. TCP/IP is what the real internet runs on, so know its layers and how they map to OSI.

The four layers

TCP/IP layer	Maps to OSI	Protocols
Application	App + Presentation + Session	HTTP, FTP, DNS, SMTP
Transport	Transport	TCP, UDP
Internet	Network	IP, ICMP, ARP
Network Access (Link)	Data Link + Physical	Ethernet, Wi-Fi

OSI vs TCP/IP

• Layers: OSI has 7, TCP/IP has 4 (some models say 5).
• Origin: TCP/IP's protocols came first, then the model (practical/descriptive); OSI is a reference/theoretical model designed before its protocols.
• Usage: TCP/IP is what the actual internet uses; OSI is mainly a teaching/reference framework.

Exam Tricks & Tips

• 🎯 TCP/IP has 4 layers (Application, Transport, Internet, Network Access) vs OSI's 7 — the headline difference.
• 🎯 TCP/IP's Application layer combines OSI's Application + Presentation + Session; its Network Access combines Data Link + Physical.
• 🎯 TCP/IP is protocol-first (practical); OSI is model-first (theoretical) — a favourite comparison point.
• 🎯 The Internet layer (TCP/IP) corresponds to OSI's Network layer — home of IP.
• 🎯 TCP/IP is the model the real internet actually runs on; OSI is a reference standard.
• 🎯 Both are layered with encapsulation — each layer adds its own header as data descends.
• ❌ Common mistake: mapping TCP/IP's Application layer to only OSI's Application — it also covers Presentation and Session.

Expected pattern

"OSI vs TCP/IP", "how many layers in TCP/IP?", "which OSI layers does the TCP/IP application layer cover?", "which model does the internet use?", and mapping a protocol to its TCP/IP layer.

Quick recap

TCP/IP has 4 layers: Application (=OSI app+presentation+session), Transport (TCP/UDP), Internet (IP/ICMP/ARP = OSI network), Network Access (=data link+physical). It's protocol-first and practical — what the internet runs on — versus OSI's 7-layer theoretical reference model.

Cover the answer, recall, then check. 11 cards on the TCP/IP model.

Q1. How many layers does the TCP/IP model have?
A1. Four: Application, Transport, Internet, and Network Access (Link). Some texts split it into five.

Q2. Which OSI layers does the TCP/IP Application layer cover?
A2. OSI's Application, Presentation, and Session layers combined.

Q3. Which OSI layers does the TCP/IP Network Access layer cover?
A3. OSI's Data Link and Physical layers.

Q4. Which TCP/IP layer corresponds to OSI's Network layer?
A4. The Internet layer — home of IP, ICMP, and ARP.

Q5. What protocols live at the TCP/IP Transport layer?
A5. TCP and UDP.

Q6. Key origin difference between OSI and TCP/IP?
A6. TCP/IP's protocols were built first and the model described them (practical); OSI is a model designed before its protocols (theoretical).

Q7. Which model does the real internet use?
A7. The TCP/IP model.

Q8. Name two Application-layer protocols in TCP/IP.
A8. HTTP, FTP, DNS, or SMTP (any two).

Q9. Which layer does IP belong to in TCP/IP?
A9. The Internet layer.

Q10. How many layers does OSI have compared to TCP/IP?
A10. OSI has 7; TCP/IP has 4 — OSI is more granular.

Q11. What do both models share structurally?
A11. Both are layered and use encapsulation, with each layer adding a header as data moves down the stack.

The internet doesn't actually run on OSI — it runs on TCP/IP, a leaner, practical model that predates OSI and became the real-world standard. Knowing how its layers map to OSI and which protocols live where is core networking knowledge.

Core idea: the TCP/IP model is the 4-layer (sometimes 5) architecture the internet is built on: Application, Transport, Internet, Network Access (Link). It's protocol-driven and practical — built around the actual TCP and IP protocols — rather than a purely conceptual reference like OSI.

How it works

Beginner — the four layers

4. Application — end-user protocols: HTTP, FTP, DNS, SMTP (combines OSI's Application + Presentation + Session).
5. Transport — end-to-end delivery: TCP (reliable) and UDP (fast). Same role as OSI L4.
6. Internet — logical addressing and routing: IP, ICMP, ARP. Same role as OSI L3 (Network).
7. Network Access / Link — physical transmission + MAC (combines OSI's Data Link + Physical).

Intermediate — mapping to OSI

TCP/IP layer	OSI layer(s)	Key protocols
Application	7 App + 6 Presentation + 5 Session	HTTP, DNS, SMTP, FTP
Transport	4 Transport	TCP, UDP
Internet	3 Network	IP, ICMP, ARP
Network Access	2 Data Link + 1 Physical	Ethernet, Wi-Fi

The Transport and Internet layers map one-to-one with OSI; the difference is at the top (TCP/IP merges three into one Application layer) and bottom (merges two into Network Access).

Advanced — the hourglass and why TCP/IP won

TCP/IP has an "hourglass" shape: many protocols at the top (apps) and bottom (link technologies), all funnelling through the narrow waist of IP at the Internet layer. This is the key design insight — "IP over everything, everything over IP": any application runs over any physical medium because they all agree on IP. TCP/IP beat OSI in practice because it was implemented and running (in Unix/ARPANET) while OSI was still being standardised — working code over committee design.

Worked example — placing protocols in the stack

Classify common protocols by TCP/IP layer:

• HTTP, DNS, SMTP, DHCP → Application.
• TCP, UDP → Transport (TCP for reliable web/email, UDP for DNS queries/streaming).
• IP, ICMP (ping), ARP → Internet.
• Ethernet, Wi-Fi (802.11) → Network Access.
  Note DNS is an application-layer protocol even though it supports other applications, and it typically runs over UDP at the transport layer — a favourite "which layer?" trap. Correctly slotting each protocol is the standard exam exercise.

Interview & exam relevance

Common asks: "TCP/IP vs OSI model" (4 vs 7 layers; which merge), "which TCP/IP layer does IP/TCP/HTTP belong to", "why did TCP/IP become the standard", and "what is the Internet layer's job" (routing via IP). The one-to-one mapping of Transport and Internet layers is worth stating explicitly.

Tricks & gotchas

• TCP/IP's Application layer = OSI layers 5+6+7; its Network Access = OSI layers 1+2.
• Transport and Internet map 1:1 with OSI's L4 and L3 — the clean part of the mapping.
• TCP/IP is protocol-centric and actually deployed; OSI is the conceptual teaching reference.
• Mnemonic: "Application, Transport, Internet, Link" — top to bottom.

Worked Example

Problem: Map each of these real protocols/actions to its TCP/IP model layer, and state how the 4-layer TCP/IP model corresponds to the 7-layer OSI model: (a) HTTP and DNS, (b) TCP and UDP, (c) IP and ICMP, (d) Ethernet and Wi-Fi.

Solution:
The TCP/IP (Internet) model has 4 layers: Application, Transport, Internet, Network Access (Link). It is the model the actual Internet runs on; OSI is the teaching reference.

Correspondence with OSI:

• TCP/IP Application layer = OSI layers 7 + 6 + 5 (Application + Presentation + Session) collapsed into one.
• TCP/IP Transport = OSI Transport (4).
• TCP/IP Internet = OSI Network (3).
• TCP/IP Network Access/Link = OSI layers 2 + 1 (Data Link + Physical) combined.

Placing the protocols:
(a) HTTP and DNS → Application layer. These are the programs' own protocols (web, name resolution). Encoding and session handling that OSI splits out are folded into this single layer here.
(b) TCP and UDP → Transport layer. They provide end-to-end delivery using ports: TCP reliable/connection-oriented, UDP fast/connectionless.
(c) IP and ICMP → Internet layer. IP does logical addressing and routing across networks; ICMP carries control/error messages (ping, "destination unreachable") and rides within IP.
(d) Ethernet and Wi-Fi → Network Access (Link) layer. These frame data with MAC addresses and transmit over the physical medium — combining what OSI calls Data Link + Physical.

Key difference to state: OSI is a 7-layer conceptual reference developed as a standard; TCP/IP is the 4-layer practical stack that the Internet actually implements. TCP/IP merges OSI's top three into Application and bottom two into Link, but the middle (Transport, Network/Internet) lines up one-to-one.

Answer: (a) HTTP, DNS → Application; (b) TCP, UDP → Transport; (c) IP, ICMP → Internet; (d) Ethernet, Wi-Fi → Network Access/Link. TCP/IP's 4 layers map to OSI's 7 by collapsing OSI's top 3 into Application and bottom 2 into Link, with Transport and Network aligning directly.