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
Permission Was Not Acceptance: Why HTTP Added 100 Continue
HTTP 100 Continue let a server reject from headers before a large body crossed the network, while keeping interim permission separate from final acceptance.
History
The Silence That Wasn't a Failure: Why TCP Keepalive Stayed Optional
An established TCP connection can say nothing for hours and still be correct. Keepalive was the attempt to question that silence without pretending to understand it: send a probe likely to provoke an ACK, collect bounded evidence, and leave the application responsible for…
History
Who Opened TCP's Window Too Soon? The Cost of Immediate Permission
An early TCP receiver could publish every byte of newly freed capacity, and a sender could consume each offer at once. That openness looked exact and cooperative. Repeated quickly, it made the connection spend most of its effort on tiny packets. The historical repair assigned…
History
The Window Update That Could Vanish: Why TCP Learned to Persist at Zero
A TCP receiver can say “send nothing” and remain healthy. The harder problem begins when it later says “continue” in an ACK that may disappear. TCP's persist mechanism turned that fragile permission into a recoverable conversation, while leaving the application—not a transport…
History
The Verdict UDP Withheld: Who Owned the Risk Behind Zero?
In UDP, zero was not a favourable checksum result. It was a notice that the sender had withheld the verdict. The history from IPv4 to IPv6 is therefore about more than arithmetic: it asks who may remove shared evidence, and when the party saving the work must also own the…
History
When Both Ends Called at Once: Why TCP Simultaneous Open Was Not a Collision
The familiar TCP handshake casts one endpoint as caller and the other as listener. TCP's original design was less hierarchical. If two processes called each other at once, their SYNs could cross, both stacks could change role without asking a coordinator, and one connection would…
History
The Price of Tolerance: How Receiver Leniency Turned Bugs into Protocol Law
The Internet's most famous rule for imperfect software began as a way to keep unlike implementations talking. Its receiver absorbed ambiguity so the network could start. Kept forever, the same bargain hid defects, made quirks contractual and charged every future implementation…
History
The Pointer That Was Never Out of Band: How TCP Urgent Split from Its Own Stream
TCP offered applications a way to interrupt ordinary processing without creating another connection. The wire carried one ordered stream and a pointer into it; decades of software turned that boundary into a mythical side channel, then made the myth too widespread simply to…
History
The Message the Internet Learned to Ignore: Why ICMP Source Quench Lost Its Authority
The early Internet allowed an overloaded gateway to send a separate command telling a distant source to slow down. Three decades of operational evidence reversed that bargain: congestion still required feedback, but a bare ICMP order no longer deserved the power to change a…
Global Regional ISP Trends
The Five Percent That Prices the Network
A 95th-percentile bandwidth bill looks like a statistic. In practice it is a contract: a rule for deciding which traffic peaks the buyer absorbs, which the provider ignores, how much capacity remains physically available, and whether the buyer can reproduce the number on the…
ICANN
ICANN’s CIP Is Underway. Its Accountability Test Comes Later
ICANN’s first annual progress table for its Continuous Improvement Program shows six of eight community structures at work and one already implementing improvements. That is useful evidence of mobilisation. It is not yet evidence that any structure has become more effective or…
North America National Telecom Trends
Cox's 33.6m Charter Units Were Valued at $11.9bn at Signing and $5bn at Close
Charter completed its acquisition of Cox with approximately the same 33.6 million exchangeable common units promised in 2025. What changed was their implied value: Charter called them US$11.9 billion at signing and approximately US$5 billion at closing, making the seller's…
History
The Sum That Had Two Zeros: How the Internet Checksum Bounded Error, Not Trust
The Internet checksum made damaged packets easier to reject by making a deliberately small claim. Its strangest corner case—two representations of zero—shows why even cheap evidence must preserve an exact boundary.
History
The Report the Sender Could Not Trust: Why TCP SACK Remained Advice
A TCP sender may keep a byte range in memory even after the receiver has explicitly reported it. That apparent distrust is the safeguard at the centre of selective acknowledgment: a precise observation can guide recovery without becoming a final receipt or a command.
Asia-Pacific Cloud Services Trends
Singapore Has Assigned 200MW of Data-Centre Capacity, Not 200MW of Live Compute
Singapore has provisionally divided 200MW of new data-centre capacity among Digital Realty, Equinix, Keppel Data Centres and ST Telemedia Global Data Centres. The award is a valuable entry in a constrained market, but land, low-carbon energy, construction, customers and…
Global Cloud Services Trends
Cloud Portability Has a Postcode
Cloud computing was sold as locationless infrastructure, but the economics of leaving it are becoming conspicuously geographic. Within the same hyperscaler, the rights and price attached to moving data can now turn on account country, billing address, source region, network path…
History
The Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible
TCP's original acknowledgment could certify an unbroken prefix of a byte stream, but it could not describe the islands waiting beyond the first gap. Selective acknowledgment added a small map of those islands while leaving the sender—not the receiver—in charge of repair.
History
The Router That Pointed Sideways: How ICMP Redirect Stayed Local
ICMP Redirect let a gateway reveal a better local next hop without becoming a routing authority. Its power ended at the host that had just used it.
History
The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.
History
The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness
DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.