Protocol stack

A protocol stack is the layered architecture of communication protocols that enables networked systems to exchange information across heterogeneous hardware and software. Each layer provides services to the layer above and consumes services from the layer below, creating a modular structure where changes at one level need not propagate to others. The internet's TCP/IP stack — linking, internetworking, transport, and application layers — is the most widely deployed protocol stack in history, yet it is only one possible layering among many.

The genius of the stack is not technical but conceptual: it separates concerns. The transport layer worries about reliable delivery; the network layer worries about addressing; the application layer worries about meaning. This separation allows innovation at one layer without requiring redesign at others. But it also creates blind spots: security, which cuts across all layers, has no natural home in the stack architecture, which is why the internet's original design treated trust as an afterthought.

The Stack as Power Architecture

The protocol stack is not merely an engineering abstraction. It is a governance structure. Each layer boundary is a jurisdictional boundary — a place where control can be exercised, contested, or concealed. The network layer determines who can reach whom; the transport layer determines whether the connection is reliable; the application layer determines what the connection means. Together, these layers constitute a hierarchy of control that is as political as any constitutional order.

This political dimension was not apparent in the stack's original design, which assumed that each layer would be operated by a different actor: hardware vendors at the link layer, telephone companies at the network layer, software companies at the application layer. The internet was supposed to be a modular marketplace in which no single actor controlled more than one layer. What emerged was something different. Platform companies like Google, Amazon, and Microsoft now operate at every layer simultaneously — from submarine cables (link layer) to cloud infrastructure (network layer) to applications (search, email, video). The vertical integration that the Bell System achieved through regulatory capture, these platforms achieve through technical architecture.

The stack model also obscures power by making it invisible. A user who searches the web sees only the application layer; the layers below are hidden by design. This abstraction is a convenience, but it is also a form of disenfranchisement. Users cannot contest what they cannot see. The stack architecture teaches us to think of the internet as a set of transparent layers, when in fact it is a set of opaque power relationships. The network neutrality debate was, at its core, a debate about whether the network layer should be allowed to discriminate against the application layer — a debate about whether one layer of the stack could be weaponized against another.

The lesson is not that the stack model is wrong. It is that the stack model is incomplete. Any useful description of networked systems must include not only the technical layers but the actors who control them, the interests they serve, and the mechanisms by which control is exercised and contested. The stack is architecture, and architecture is never neutral.