Time Horizon
Multi-year
Within the Time Horizon facet, Multi-year 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
The Error That Learned to Expire: How DNS Cached What Did Not Exist
The expensive DNS question is not always the one with a large answer. It may be the miss that thousands of resolvers repeat because nothing can be stored. Negative caching gave absence a scope, evidence and an expiry time—then forced operators to accept that a newly created name…
History
The Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems
The early Internet did not decentralize by pretending that every network agreed. It learned to survive disagreement. The Exterior Gateway Protocol drew a boundary around what one routing administration could keep private and what it had to tell its neighbours. That boundary made…
History
The Mail Address That Outlived Its Server: How MX Records Separated Identity from Delivery
An email address looks like a destination. In the early Internet, it often was: a mailer could take the domain after `@`, open SMTP to the machine with that name and hope the mailbox lived there. In January 1986, RFC 974 described why that assumption had stopped scaling—and how…
CASE FILE
A Verified RFC Erratum Corrects the Record Without Rewriting It
An RFC erratum can identify a real defect, supply corrected wording and be verified by the responsible parties. It still does not silently replace the published specification. That separation lets implementers learn from mistakes while preserving the text the community actually…
History
The Clock Built from Disagreement: How NTP Made Internet Time Without Trusting One Server
In 1989, an Internet-wide experiment found clocks wrong by minutes, hours and, in a few cases, weeks. The problem was not a shortage of machines willing to state the time. It was deciding which statements deserved to move a local clock when packets, oscillators and operators…
History
The Web CERN Chose Not to Own: How a Laboratory Designed Its Own Exit
The World Wide Web did not become universal merely because it was invented at a famous laboratory. It became portable across institutions because its common machinery was kept small, its specifications were public, its clients escaped one workstation, and CERN eventually removed…
History
The Network That Let Institutions Join Unequally: CSNET and the Architecture of Partial Access
CSNET widened the networked research community without pretending that every institution could afford or operate the same connection. By combining ARPANET access, full Internet service over commercial X.25, and dial-up PhoneNet mail, it showed that interoperability could begin…
History
The Map Made from Expired Packets: How Traceroute Turned Failure into Internet Evidence
In December 1988, Van Jacobson was not trying to draw the Internet. He was trying to find out where his packets had gone. The tool he assembled at Lawrence Berkeley Laboratory made the network answer indirectly: send a packet designed to expire, listen for the complaint, then let…
CASE FILE
DNSSEC Can Prove Absence Without Deciding Entitlement
A signed negative DNS answer can establish that a name or record type was absent from a particular signed zone during a bounded validity period. It cannot establish why the entry is absent, who deserves the label, whether a registrar should create it, or whether an Opt-Out…
History
The Day the Old Protocol Lost Its Network: The 1983 TCP/IP Cutover and the Limits of Technical Authority
On 1 January 1983, an ARPANET host that still depended on NCP faced a new fact: the network beneath it could stop servicing the old protocol. The famous cutover mattered not because a memo became universal law, but because a disclosed rule reached an execution boundary whose…
History
Where the Network Stopped: The IMP, the Host, and the First Price of Shared Correctness
ARPANET’s Interface Message Processor made packet switching operational by putting substantial machinery into a dedicated subnet. It also made a harder problem visible: infrastructure can carry, check, meter and protect communication without possessing the knowledge required to…
History
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
When the First Network Became Replaceable: ARPANET’s Retirement and the Internet That Continued
ARPANET did not take the Internet with it when it was retired in 1990. That was not because the pioneering network had become unimportant. It was because its most important function—making unlike networks communicate—had already escaped the machinery and institution that first…
History
The Window That Learned Restraint: How TCP Stopped Congestion Collapse Without a Traffic Authority
The Internet's answer to its first congestion crisis was not a controller above the network. It was a new discipline inside every sender: learn the path from acknowledgements and loss, increase carefully, and retreat before retransmissions turn shared capacity into useless…
CASE FILE
Mozilla’s Hidden Security Boundary: How the Public Suffix List Becomes Running Code
Mozilla began the Public Suffix List, and Firefox still turns a version of it into browser behaviour. The DNS can tell software that `whatwg.github.io` exists beneath `github.io`, but not whether those names belong to one organisation or mutually untrusting tenants. This article…
History
The Worm That Needed a Switchboard: How the 1988 Internet Built CERT Without Giving It Command
When the Internet’s first great emergency arrived, its most effective institutional answer was neither a central operator nor a security sovereign. It was a small, trusted point of contact built to make independent operators faster and better informed while leaving their…
NANOG
The Corporation NANOG Built—and the Networks It Did Not Own
When NANOG left Merit’s institutional shelter, the decisive transfer concerned a trademark, a domain, archives, contracts and financial responsibility—not routers, address space or the authority to speak for North America’s autonomous networks.
Story
Resolution 201804.407 Renewed the CEO Contract Before Final KPIs and Performance Evaluation
AFRINIC’s Board approved a three-year renewal on the same employment terms at a special meeting on 19 April 2018, even as its own resolution deferred finalising the chief executive’s KPIs and performance evaluation until May. The surviving sequence supports a precise governance…
Story
AFRINIC’s Interim Management Committee Was Given Six Months. Who Renewed It?
AFRINIC gave three senior employees collective responsibility for day-to-day management during its CEO vacancy and said the arrangement would last six months or until a new chief executive arrived. The announcement was public; the full authority chain was not. Using the…
Story
Eight elected seats in one notice: what AFRINIC’s 12 September result proves
AFRINIC’s brief announcement did something institutionally significant: it named an occupant for every member-elected Board seat in a single exceptional reconstitution cycle. Yet the notice remains a declaration, not a complete result receipt. Its evidentiary value becomes clear…