The missing owner

There Is No Head Office, And That Is The Whole Design

The internet is not a thing that somebody built and now operates. It is an arrangement between many independent networks that each chose to connect, and it holds together for reasons that are worth understanding properly.

Ask who runs the internet and the honest answer is that nobody does, not in the way anybody runs a railway or an airline or a water utility. There is no head office, no chief executive of the network, no single organisation that can switch it off or decide what it carries. What exists instead is a very large number of separate networks, each owned and operated by somebody different, each making its own decisions about equipment and staffing and customers, and each choosing to exchange traffic with some of the others. The internet is the name we give to the result of all those choices. It is a pattern rather than a possession, and once that is understood, a great many otherwise puzzling things about it become clear.

This surprises people because almost every other system of comparable scale has an owner. Electricity grids have operators. Postal systems have national administrators. Aviation has authorities that license aircraft and control airspace. The instinct to look for the equivalent body here is entirely reasonable, and the fact that the search comes up empty is not an oversight or a gap waiting to be filled. It is the arrangement working as intended. The networks that make up the internet remain independent precisely because no central authority was ever placed above them, and they cooperate because cooperating serves each of them, not because anybody instructed them to.

A Network Of Agreements

The Internet Is An Agreement, Not A Machine

What people call the internet is better understood as a set of arrangements between separate operators than as a single constructed object.

Why Networks Connect When Nobody Makes Them

Interoperating is not a duty imposed on operators, it is generally the most attractive option available to them.

Nobody Built The Whole, Everybody Built A Part

The system has no original architect because it was assembled outward from many independent decisions rather than designed as a unit.

The Parts That Must Be Coordinated

Names Have To Be Unique, So Somebody Must Coordinate

The requirement that a name means the same thing everywhere is what forces a genuinely central function into an otherwise decentralised system.

Addresses Are Allocated, Not Chosen By Their Users

Numbering a global network requires handing out identifiers in an orderly way, which is a second genuinely coordinated function.

Centralise The Least, Leave The Rest Alone

A consistent principle runs through the coordinated functions: keep them as narrow as the problem allows and no narrower.

How Standards Get Made Here

Open Participation Instead Of Appointed Delegations

The technical conventions everyone follows are written in forums that anybody with the interest and effort can join.

Rough Consensus And Running Code As A Working Culture

Decisions are settled by broad agreement and by demonstrated implementation rather than by voting or by executive choice.

Documents Anyone Can Read, Rules Anyone Can Ignore

The specifications are public and free, and following them is a choice each operator makes for its own reasons.

The Pressures On It

Consolidation Puts Most Traffic Through Few Hands

A design that assumed many roughly comparable networks now operates with a small number of very large ones carrying much of the load.

National Rules Meet A System Without Borders

Societies legislate for territories, while the network was designed without any concept of where anything is.

Openness And Governance Pull In Different Directions

A network built to carry anything sits uneasily with the ordinary and reasonable wish of societies to shape what happens within them.

About Net Nard

Net Nard exists to explain how the internet is arranged, in plain language, for readers who use it constantly and have never had cause to ask how it holds together. The starting assumption is that curiosity deserves a proper answer rather than a slogan, and that most of what seems mysterious about the system becomes clear once its basic shape is described accurately. We take the view that a reader who understands the arrangement is better placed to judge arguments about it, whichever way those arguments run, and that supplying the understanding is more useful than supplying a conclusion.

This issue is about governance in the broadest sense: who decides things, on what authority, and what happens where nobody decides anything. It is not a technical guide and contains no operational detail. Nothing here explains how to configure, operate or interfere with any system, and that omission is deliberate. Our subject is the arrangement rather than the mechanism, and the two are separable. A reader wanting to know how a message physically crosses a network will need to look elsewhere, because that is a different question with a different answer.

On the contested questions, our position is to describe rather than to advocate. Debates about consolidation, about national regulation and about the balance between an open network and the wish of societies to govern themselves involve people arguing in good faith from incompatible starting points, and we do not think it is our place to pick a winner. Where a tension is real and unresolved, we say so and set out both sides as fairly as we can manage. Readers are entitled to reach their own conclusions, and are better equipped to do so when the disagreement has been laid out honestly rather than settled on their behalf.