Time Horizon
Structural
Within the Time Horizon facet, Structural time-horizon intelligence organises articles by the period over which a signal is expected to matter. The page helps readers distinguish immediate operational changes from longer-cycle governance, investment, standards, and infrastructure shifts that may unfold across quarters or years. It connects timing assumptions with public evidence, related actors, market context, customer exposure, policy pressure, and infrastructure planning so readers can judge whether a development is urgent, strategic, or still waiting on confirming evidence. The page also explains how time horizon changes the meaning of a signal, which organisations may be exposed, and which infrastructure decisions require short-term action or long-cycle monitoring.
History
Hyunje Park and the Broadband Launch That Outran a Financial Crisis
Capital fled Korea in 1997. The cable under its streets and apartment blocks did not. Hyunje Park’s place in Internet history rests on what his team did with that asymmetry: turn physical reach that already existed into a commercial broadband service before the financial shock…
History
Tarek Kamel and the Local Call That Repriced Internet Access
Egypt’s “Free Internet” began with a number on a telephone line, not with a free network. The user paid for a local call, the monthly ISP subscription disappeared, and revenue moved through a new settlement between the incumbent and private providers. Tarek Kamel’s career shows…
History
Kenneth J. Klingenstein and the Registry Between Two Login Domains
A login crossing from a university to an outside service looks like a short trip through a browser. Kenneth J. Klingenstein’s work helped expose the institution hidden in the middle: a trust fabric that must make one domain’s assertion usable in another without pretending that…
History
John S. Quarterman and the Map That Had to Define the Internet
A dot on a map looks like a fact. John S. Quarterman’s work showed that, on a network without a central census, the fact begins much earlier: someone must decide which service, machine, name, route or person the dot is allowed to represent.
History
Elise Gerich and the Public Record Behind Private Routes
Routers could tell one network what another network could reach. They could not explain what the other network meant to announce, what it was prepared to accept, or whether the two intentions were compatible. Elise Gerich’s work around the Routing Arbiter belongs to the history…
History
Stephen Wolff and the Boundary Between a Public Backbone and a Market
A packet could not explain whether it served scholarship or commerce. NSFNET nevertheless had to draw that distinction while it was becoming the principal American research backbone. Stephen Wolff’s most revealing contribution was to treat commercialization and privatization as…
History
Hans-Werner Braun and the Numbers That Made a Backbone Governable
Hans-Werner Braun helped operate NSFNET at the moment when a research network was becoming national infrastructure. His most durable lesson is not a router model or a speed record. It is that a backbone becomes governable when its operators can show, in public and with honest…
History
Pål Spilling and the Cable That Made Norway Both Reachable and Vulnerable
Norway’s first Internet connection was a door to a global research community—and, for a time, a single physical point at which that door could be shut. Pål Spilling’s career shows why a network’s topology is also a map of authority: it decides who can connect, who absorbs…
History
Louis Pouzin and the Network That Refused to Remember the Conversation
CYCLADES asked what a packet network should be trusted to know. Louis Pouzin's answer was deliberately austere: let the switching system move independent datagrams, and make the computers at the edges responsible for turning them into a reliable conversation. That division of…
History
George Sadowsky and the Workshops Designed to Outgrow Their Teachers
The Internet Society's network-training workshops were built around a demanding test of technical assistance: would the people in the classroom still need the visitors when the next router failed? George Sadowsky's contribution was to make the answer less dependent on equipment…
History
Peter Kirstein and the Transatlantic Node That Was More Than a Terminal
When ARPANET reached London in 1973, the scarce asset was not simply a line across the Atlantic. Peter Kirstein's achievement was to turn UCL from a distant customer of American machines into a place where British researchers could attach computers, implement protocols, operate…
History
Dai Davies and the Buyer Europe Did Not Yet Have
In 1993, Europe’s national research networks did not mainly lack ambition. They lacked a counterparty. Someone had to turn many countries’ requirements into one specification, take that specification to a guarded telecommunications market, award contracts, reject deficient…
History
Klaas Wierenga and the Credential That Stayed Home
A student from Delft opens a laptop in Cape Town. The local university can offer a network, but it cannot vouch for the visitor’s account. Delft can vouch for the account, but it does not control the Cape Town network. Klaas Wierenga’s decisive contribution to eduroam was to make…
History
Jan Gruntorád and the Link That Had to Become Two Networks
At the start of 1992, an international circuit from Prague to Linz was strengthened and divided. One channel continued to carry EARN traffic; the other was assigned to the Internet. In that physical line becoming two operational networks lies a more useful history of Jan…
History
Ben Segal and the TCP/IP Pilot That Could Not Leave CERN
By March 1988, TCP/IP served 355 machines at CERN, from an IBM mainframe and a Cray to VAX systems, workstations, PCs and Macintoshes. Yet none of those machines could use TCP/IP to cross the laboratory’s external boundary. Ben Segal’s pilot had solved heterogeneous connectivity…
History
Rob Blokzijl and the Chair That Could Coordinate but Not Command
The most revealing sentence in RIPE’s first terms of reference is not the one that declares a European ambition. It is the sentence that withholds power. RIPE was not a network provider, and the networks cooperating through it remained under the executive authority of their own…
History
Qiheng Hu and the 64K Link That Needed Authority at Both Ends
By the end of 1993, the network was technically ready. Its domestic backbone joined three academic systems, its team had chosen TCP/IP, and the international circuit had been provisioned. Yet packets still did not cross. Qiheng Hu’s part in China’s full-function Internet…
History
Jun Murai and the Address Space That Became a Trust
The number is oddly exact: 14,680,064 IPv4 addresses. They were neither a fresh registry allocation nor abandoned space waiting to be reclaimed. They were seven-eighths of an old Class A block, held through three decades of changing Internet institutions, and in 2020 Jun Murai…
History
Kilnam Chon and the Router Asia Could Not Buy
On 15 May 1982, two computers in South Korea began speaking across a 1,200 bps leased line. The connection was modest; the missing box beside it was more consequential. With no obtainable IP router, Kilnam Chon’s group treated published protocol documents as equipment they could…
History
Kees Neggers and the Backbone Europe Built in Parallel
On 26 September 1992, one link between London and Montpellier completed Ebone’s initially defined backbone. The more revealing number was not its line rate but its age: 390 days since a small group had first met outside Amsterdam to ask whether Europe could operate a shared IP…