The Four TCP/IP Layers
The TCP/IP model (also called the Internet model) consists of four layers: Network Access (or Link), Internet, Transport, and Application. The Network Access layer corresponds to OSI Layers 1 and 2 (Physical and Data Link). It handles physical transmission and MAC-level framing. Ethernet, Wi-Fi (802.11), and ARP operate here.
The Internet layer maps to OSI Layer 3 (Network). It is responsible for logical addressing, routing, and packet delivery across networks. IP (IPv4 and IPv6), ICMP, and IGMP operate at this layer. Routers make decisions at the Internet layer.
The Transport layer maps directly to OSI Layer 4. TCP (Transmission Control Protocol) provides reliable, connection-oriented, ordered delivery with error recovery. UDP (User Datagram Protocol) provides fast, connectionless, best-effort delivery without guarantees. Both use port numbers to identify application services.
The Application layer maps to OSI Layers 5, 6, and 7 combined. It encompasses all application protocols: HTTP/HTTPS, FTP/SFTP, DNS, DHCP, SMTP, IMAP, POP3, SNMP, SSH, Telnet, and many others. The Application layer is where end-user services interact with the network.
OSI vs TCP/IP Comparison
Network+ exam questions frequently ask you to match OSI layers to TCP/IP layers. The key mapping: TCP/IP Application layer = OSI Layers 5+6+7. TCP/IP Transport = OSI Layer 4. TCP/IP Internet = OSI Layer 3. TCP/IP Network Access = OSI Layers 1+2.
A common question asks: 'DHCP operates at which TCP/IP layer?' Answer: Application (even though DHCP assigns IP addresses, the protocol itself is an application-layer service). Similarly, DNS is an Application layer protocol despite being infrastructure. IP is Internet layer; Ethernet is Network Access layer.
Encapsulation in TCP/IP
When data is sent, it passes down through the TCP/IP layers with each layer adding its header (encapsulation). Application data → Transport adds TCP/UDP header (segment/datagram) → Internet adds IP header (packet) → Network Access adds Ethernet header+trailer (frame) → Physical transmission (bits).
De-encapsulation reverses this process at the receiver. Understanding encapsulation explains why a packet capture at Layer 3 shows IP headers but not Ethernet headers — each layer strips its own header as data moves up the stack.