The TCP/IP Model

TCP/IP follows the end-to-end principle: keep the network core simple (just forward packets) and push complexity to the endpoints. The network doesn't need to understand what's inside your packets — it just delivers them. This is the opposite of the telephone network (circuit-switched), where the network manages the entire call state.

Naming: "TCP/IP" refers to the two most important protocols in the suite (TCP at the transport layer, IP at the internet layer), but the model encompasses hundreds of protocols. The more precise name is the "Internet Protocol Suite."

Combines OSI Layers 1 and 2 into a single layer that handles everything required to send a frame across a single physical link. The TCP/IP model deliberately treats this as opaque — the upper layers don't care whether you're running on Ethernet, Wi-Fi, cellular, or carrier pigeon.

• Frames packets for the specific physical medium
• Handles hardware (MAC) addressing for local delivery
• Manages media access, error detection, and physical signaling
• Provides ARP (IPv4) or NDP (IPv6) for address resolution

The heart of the model. Responsible for addressing, routing, and forwarding packets across network boundaries. IP is the single protocol at this layer, and everything above and below must interface with it. This is the "narrow waist" of the hourglass.

• Logical addressing: IP addresses provide globally unique, hierarchical identifiers
• Routing: Each router independently makes a forwarding decision based on the destination IP
• Best-effort delivery: IP makes no guarantees — packets can be dropped, duplicated, or reordered
• Fragmentation: Breaks oversized packets (though Path MTU Discovery avoids this in practice)

Best-effort: IP intentionally provides no reliability, no ordering, and no delivery guarantees. This is a feature, not a bug. It keeps the network layer simple and pushes reliability to the endpoints (TCP) — exactly per the end-to-end principle.

Provides end-to-end communication between processes. Uses port numbers (16-bit, 0-65535) to demultiplex traffic to the correct application on a host. The two dominant protocols offer very different trade-offs.

QUIC (used by HTTP/3) is a transport protocol built on top of UDP that provides TCP-like reliability with significant improvements:

• Encrypted by default (TLS 1.3 integrated into the transport)
• 0-RTT connection establishment (vs TCP's 1-RTT + TLS 1-2 RTT)
• Multiplexed streams without head-of-line blocking
• Connection migration (change IPs without dropping the connection — useful for mobile)
• Implemented in userspace, not the kernel — faster iteration

Absorbs OSI Layers 5, 6, and 7 into a single layer. Any protocol that sits on top of TCP or UDP lives here. This layer handles session management, data encoding, encryption, and application semantics — all combined.

Note: In TCP/IP, there's no distinction between "application protocol" and "presentation/session protocol." TLS, which OSI would split across L5-L6, is just another application-layer protocol in TCP/IP that sits between the transport and the higher application protocols (HTTPS = HTTP + TLS).

• Universal interoperability: Any application that speaks IP can run over any link technology. HTTP doesn't care if you're on Ethernet, Wi-Fi, or 5G.
• Innovation at the edges: New application protocols (HTTP/3, gRPC) and new link technologies (5G, Starlink) can be added without changing IP.
• The cost: Changing IP itself is extraordinarily hard — IPv6 adoption has taken decades precisely because IP is the narrow waist everything depends on.

Historical irony: The U.S. government initially mandated OSI protocol adoption (GOSIP — Government OSI Profile, 1990). By 1995 they dropped the mandate because TCP/IP had already won the market. The internet's explosive growth in the early 1990s sealed OSI's fate as a protocol suite.

OSI survives as a teaching tool and shared vocabulary. TCP/IP survives as the actual implementation. In practice, you'll use OSI layer numbers (L2, L3, L4, L7) to talk about TCP/IP concepts. Nobody says "TCP/IP Layer 2" — they say "Layer 3" (meaning OSI Layer 3 = IP = TCP/IP Internet layer).