Internet Protocol Suite

The Internet Protocol Suite — commonly known as TCP/IP — is not merely a set of communication protocols but a governing architecture that determines how information flows, fails, and is recovered across the planetary network. It defines addressable nodes, routing paths, error handling, and congestion control, but its meaning is inseparable from the material infrastructure — fiber, routers, data centers, institutional agreements — that enacts it. The protocol suite is a code-as-infrastructure system: it prescribes what the network should be, and when the prescription is ignored, the network becomes a different network with different possibilities and different foreclosures.

The suite is organized in layers, but the layers are not merely technical abstractions. They are governance boundaries. The link layer determines who can connect. The internet layer determines who can be found. The transport layer determines who can communicate reliably. The application layer determines who can do what with the communication. Each layer embeds assumptions about trust, authority, and access that were designed for a research community in the 1970s and now govern a global civilization. The mismatch between the protocol's assumptions and its actual use is not a bug; it is the source of most contemporary network governance problems.\n\n

The governance of the protocol suite is contested territory, raising questions about protocol governance and digital sovereignty that its original designers did not anticipate.