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 ACK That Could Not Name the Copy: How Karn Stopped TCP Learning the Wrong RTT
A TCP acknowledgment can be completely true and still answer the wrong question. After a timeout, the same bytes may have crossed the network twice. The returning ACK proves that the receiver advanced, but not which copy made it advance. Karn's algorithm made that missing label…
Leaders
Bill Woodcock, PCH and the Two Layers of Internet Authority
Bill Woodcock’s public record puts two arguments about Internet institutions side by side: his 2015 case for contractual accountability in the IANA transition, and Packet Clearing House’s later report that it had become an intergovernmental treaty organization. The difference is…
Leaders
Aftab Siddiqui and a Routing-Security Survey That Could Not Order an API
At APNIC, Aftab Siddiqui appears in two different routes from operator concern to institutional action: a policy proposal with public decision milestones, and a routing-security survey meant to inform service design. The contrast shows what each record can—and cannot—prove.
Leaders
William B. Norton and the Metric That Could Not Price a Peer
A traffic ratio can show how packets crossed one boundary during one period. It cannot, by itself, tell two networks whether a direct connection is worth the cost, which routes matter more, or whose policy should decide.
IETF
Niels ten Oever and the review that followed a protocol off the page
RFC 9620's update to a human-rights review guide is notable for the evidence gap it admits: questions about design can surface risks, but understanding consequences also means listening to people, examining implementations and keeping the method open to revision.
History
John Day and the Seven-Layer Model That Could Not Order Deployment
Seven boxes can look like a build plan. John Day’s account of the OSI reference model offers a different reading: a framework for standards work, not an implementation order. His later RINA proposal made a recursive IPC design explicit; a small prototype showed that research code…
Europe and Middle East Datacenter Trends
VIRTUS closed £2.45bn of funding. £1.2bn is identified as green capex
VIRTUS Data Centres has secured a large committed financing framework for growth. Its value will be decided after the announcement: by what is drawn, which eligible projects receive the green-capex money, and how quickly permits, grid access and construction become live IT load…
Global Datacenter Trends
Delos Data’s $100m must buy an acceptance matrix, not a bigger network claim
Funding can pay engineers to turn an architecture into a product. It cannot make cluster software, a server sample and interface silicon arrive on the same clock—or make a bandwidth target equal a verified cost per token.
North America Datacenter Trends
USD.AI’s $128.9m GPU loan needs a collateral receipt, not a rack count
Thirty-two GB200 NVL72 systems describe a substantial fleet. They do not disclose who owns it, whether it has been installed, which customer receipts repay the debt or who can remove the machines after a default. Those joins—not the headline—turn compute into collateral.
Global Cloud Services Trends
Bird’s $450 million debt finances shareholder liquidity, not proof of agent demand
Bird has paired a dividend recapitalisation with an ambitious communications layer for AI agents. The first transaction can be completed by banks and shareholders; the second becomes valuable only when authorised machine actions survive consent, delivery, carrier charges, abuse…
Leaders
Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
An IPv4 default gateway normally looks like an address that a host can find with ARP. Remco van Mook's current IETF proposal turns that expectation inside out: `192.0.0.11` is not a neighbour to discover, but an instruction to reuse a neighbour that IPv6 has already discovered.…
North America Institutional Trends
EigenQ’s $45 million headline buys a conditional commercialisation clock
The quantum-security company has not received a $45 million operating cheque. Its filed financing is a two-stage, discounted and secured bridge in which cash, closing risk, dilution and collateral must be reconciled before the valuation story can be judged.
North America Datacenter Trends
Sunrun and SPAN still need to price the home as a data-centre lease
Their residential compute partnership adds financing and field service to SPAN’s XFRA concept. It still leaves the decisive market unit undisclosed: a contract that allocates energy, compute, grid-service, maintenance and exit rights around each home.
Leaders
John Ousterhout and the Fast Write That Became Cleaning Debt
The log-structured file system made a small write look almost effortless by turning it into part of a long sequential transfer. Its deeper lesson was not that the cost had vanished, but that systems must account for where the cost returns: in cleaning, spare capacity…
History
The Packet Contained Picture and Sound. It Did Not Prove a Programme Played: RFC 2343
RFC 2343 put MPEG-2 video slices and audio frames into one RTP payload so that a stored programme could travel as one coordinated stream. The packet carried useful timing and boundary evidence. It still could not testify for the network, decoder, renderer, loudspeaker, screen or…
History
One Clean Match Hid the Hard Questions: RFC 2345 and the Company-Name Lookup
A company name went in; a name and a URL came back. RFC 2345 made that exchange intentionally small enough for a 1998 browser add-in and a port-43 server. The economy was the point. Yet the response line carried no proof of who registered the domain, which legal entity the name…
History
The Map Was Not the Road: What RFC 2333 Let NHRP Resolve—and What It Could Never Prove
A clean NHRP cache row could look like the end of a problem. It joined an IP destination to an NBMA address, carried an authority class and retained a holding time. Yet RFC 2333 placed that row in a much longer chain. Routing had to choose a path first. NHRP could then resolve a…
Global Institutional Trends
Lightera’s Subsea Fiber Expansion Still Needs a Demand Bridge
Lightera plans to nearly triple submarine optical-fiber manufacturing capacity by 2029. The commercial test is whether early demand visibility becomes qualified programmes, contracted volume, plant utilisation and durable cash returns.
Global Datacenter Trends
Coherent’s PhotonLink Engagements Need a Revenue Trail
Treating PhotonLink’s launch pipeline as a revenue ledger would credit Coherent with sales before their scope, timing and accounting basis are established. The commercial question is how its integrated optics offer moves from customer discussions and agreements to attributable…
History
When a Successful ESRO Result Still Ends in Failure
In ESRO, a performer could finish an operation, send a successful result, and later receive a failure indication even though the invoker had already accepted that result. RFC 2188 made room for both observations to be true. Its most durable lesson is not about a forgotten 1990s…