Echoes

Echoes

The Network Was Built Not to Know

Three engineers argued in 1984 that only the two ends of a conversation can judge whether an exchange came out right. TCP/IP took the advice. What we got is a network that moves a purchase, a regulatory disclosure, and a video of somebody's dog through the same machinery, which is precisely why anyone could build anything on it without asking permission first. The paper also asked a question it declined to answer: where are the ends? Agents now sit there, checking outcomes against a standard held by a principal who never saw the choice being made.

The Network Was Built Not to Know
Three engineers argued in 1984 that only the two ends of a conversation can judge whether an exchange came out right. TCP/IP took the advice. What we got is a network that moves a purchase, a regulatory disclosure, and a video of somebody's dog through the same machinery, which is precisely why anyone could build anything on it without asking permission first. The paper also asked a question it declined to answer: where are the ends? Agents now sit there, checking outcomes against a standard held by a principal who never saw the choice being made.
The Road Refused

For most of a century the telephone network knew who was talking. A call reserved a physical path and held it: two identified endpoints, a start time, a route, an explicit hang-up. By the late 1970s the signaling layer underneath tracked all of that well enough to bill you by the second. The relationship between two people talking was something the network itself maintained.
Donald Davies, working on data communication in Britain in the mid-1960s, kept circling the waste in that arrangement. An hour on the line during which almost nothing is transmitted still occupies the circuit. Computers talk in bursts; reserving a lane for silence is expensive.
Data networks took the bits and left the rest. They got resilience, cheap components, and room for applications nobody had to clear in advance.
But the knowledge was useful, so it was rebuilt one layer up — cookies, tokens, session identifiers — by every application separately. It was also rebuilt outside the rules the phone network operated under. Common carriage, wiretap statutes, and audited billing records governed what a switch was allowed to know. Nothing comparable moved with it.

Gil Hopsworth on Routing Packets for Thirty Years Without Asking Why
CONTINUE READINGIntelligence Returns

The Middle of the Network Wanted to Know
Traffic does not declare what it is for. There is no field for that, and there never was — so when broadband operators bought equipment to read inside the packets they carried, the machinery had to guess: from sizes, from timing, from patterns of bytes recurring at line rate. A 2008 FCC case shows what a guessing engine can do once it is sitting on the rack. Encryption's reply had no way to tell the honest operators from the opportunistic ones, and made no attempt.

Your Browser Believes the Edge Is the Site
Distributed caching entered the world in 1997 as a load-balancing result: how to keep everyone wanting the same file at once from melting a single server. Encryption changed what that position means. To serve a site over HTTPS, the machine nearest you has to hold credentials in the site's own name, which means your browser treats it as the party it was talking to all along. The reading that encryption drove out of the middle of the network found somewhere it is welcome.
Further Signals




Past Articles

A signed agent request will tell you which key signed it, when, and when that signature stops counting. It will not tell...

A bill comes in from Hamburg. Nobody in the counting house has ever seen the hand that signed it, and the sealed power o...

In June 2000, Congress gave machine-formed contracts federal standing, with one condition attached: the agent's action h...

Visa and Cloudflare, solving different problems in different industries, independently arrived at the same structural mo...
