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 Address You Needed DNS to Find: How Glue Broke the Delegation Loop
A DNS referral can name the server that knows the answer and still leave a resolver unable to reach it. Glue was the small, deliberately non-authoritative exception that let the resolver cross that gap without giving the parent zone control over the child's facts.
History
The Address That Asked the Wire: How ARP Made Local Reachability Revisable
Routing can choose the next IP address without knowing how to put a frame on the local cable. ARP filled that last gap with a public question, a private answer, and a memory designed to be corrected.
History
The Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake
A packet can arrive at the right address, carry a plausible number and still belong to a conversation that has already died. TCP's familiar opening exchange was designed around that ambiguity: before accepting a new connection, both endpoints must show that they have seen each…
Global National Telecom Trends
An IRU Buys the Strand, Not the Road Around It
A dark-fibre contract can name a strand, reserve it for twenty years and make it feel like an owned asset. The harder question begins one layer out: who controls the ducts, access, power, maintenance, relocation and remedies that keep that strand useful when the route changes or…
Asia-Pacific Cloud Services Trends
Mercury Buys Into Datagrid Before the 140MW Power Option Becomes Load
Mercury has paid NZ$53 million for a 12.7% stake and a board seat in Datagrid NZ after signing a 140MW power purchase option. The structure gives the generator an early position beside a possible anchor customer, but it does not turn consent, earthworks or an option into an…
History
The Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge
A packet may cross a path whose narrowest link is invisible to its sender. The Internet spent four decades changing who should discover that limit, who should report it and who should decide what size to send next.
History
Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA
An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop…
Africa Cloud Services Trends
Nigeria Bets Federal Cloud Buying Power Can Anchor an Open Provider Market
Nigeria’s new cloud policy puts aggregated federal demand at the centre of its market-building strategy: ministries, departments and agencies would buy through coordinated mechanisms from multiple registered providers, creating an anchor customer large enough to improve…
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…