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 Hash That Stayed While the Keys Changed: How SSH Bound Authentication to One Session
An SSH connection can replace the cryptographic machinery protecting it without making every shell, file transfer or forwarded channel begin again. The protocol made that continuity explicit: the first key exchange left behind a hash that later keys could not rename.
History
The Number That Grew at Every Cache: How HTTP Age Estimated a Response Without Dating the Object
A browser can receive `Age: 120` for a document written years ago. The apparent contradiction disappears once the field is read narrowly: HTTP did not ask caches to date content. It asked each cache to carry forward, correct and extend an estimate about one stored response.
History
The Bit That Ended the Record: How ONC RPC Put Message Boundaries Back on TCP
A TCP reader can receive half a header, three complete calls or the tail of one reply. None of those read sizes says where an RPC message ends. ONC RPC solved the problem with four bytes: 31 bits counted one fragment, while the remaining bit closed one record after that…
History
The Message That Arrived as Several Messages: How MIME Made Reassembly a Local Act
A large mail entity could cross the Internet as several ordinary messages, each accepted or delayed on its own, and still become one typed entity at the far end. MIME achieved that without pretending the wrappers were the entity: it supplied a narrow grouping grammar and left…
Global Cloud Services Trends
Box's RPO Rose 15%. Broader Content Use Could Still Lower Margins
Box sold more contracted revenue faster than it grew current revenue, while preserving a 79.1% GAAP gross margin. Yet its own filing identifies a second commercial clock: customers that place more of their content in Box can consume more infrastructure before the public accounts…
History
The Condition That Turned a Range into the Whole: How HTTP If-Range Kept Partial Bytes in One Version
A client had the first million bytes of a file and wanted the rest. The offset was easy to state; the dangerous question was whether “the rest” still belonged to the same version. HTTP answered with a condition that could turn a request for a fragment into delivery of the whole…
History
The Trail That Grew Backwards: How Usenet Path Stopped a Relay from Sending News Back
A news article arrived at one server carrying the name of the server that had just sent it. That small trace let the receiver avoid an absurd next move—offering the same article straight back—without mistaking a mutable journey record for a return address, a signature or the…
IETF
Ari Keränen and the Candidate Pair That Won Before Success Could Be Claimed
An ICE log can name the transport path a session selected with millisecond precision. It still cannot tell an operator whether anyone heard a word, whether an application admitted the session or whether permission to keep sending remained fresh. The useful record begins where the…
History
The Link That Never Left the Message: How MIME Content-ID Named Embedded Parts
An HTML message could point to a picture using something that looked like a URL, yet no browser had to leave the message to fetch it. MIME made that possible by giving each body part a label, letting another part spell the label as `cid:`, and leaving the receiving application to…
History
One Call-ID, Several Dialogs: How SIP Tags Named a Fork
An invitation sent to one address could ring at several endpoints and return several answers. SIP's durable solution was not to give each answer a new call number, but to let each peer complete a two-sided name for the state that would outlive the invitation.
Global Datacenter Trends
NVIDIA Has US$2.8bn of Customer Advances. Its RPO Uses a Different Perimeter
NVIDIA is receiving substantial customer cash before recognizing the associated revenue, yet its quarter-end advance balance, half-year cash-to-revenue flow and long-duration contract obligations are not one metric. The distinction matters because the same quarter also carried…
IETF
Erik Nordmark and the Neighbor That Became Stale Before It Became Unreachable
An IPv6 neighbor can become `STALE` while it is still carrying traffic, and it can enter `UNREACHABLE` while packets are still sent to its cached link-layer address. The apparent contradiction disappears once the cache is read as a record of expiring evidence rather than a…
History
The Connection Died. The Session Did Not: How RTSP Put State Beyond TCP
A media server could lose the socket that carried PLAY and still remember what the client had set up. RTSP made that possible by giving server state its own expiring identifier—then carefully refusing to treat the identifier as the resource, the media path or the user's…
History
The Flag That Made Ignorance a Validation Failure: How X.509 Critical Extensions Governed Change
A certificate could acquire a new signed rule long after old software had shipped. X.509 v3 made that growth possible with an extension identifier, a value and one Boolean. The Boolean did not announce importance. It decided whether a validator that could not understand the rule…
North America Cloud Services Trends
DigitalOcean's Top 25 Customers Reached 20% of Revenue. AI ARR Counts the Whole Account
Two expanding labels now carry much of DigitalOcean's growth story: its largest customers and its AI customers. Neither label is a product revenue line. Reading them together requires an account-level bridge that the company has not yet published.
IETF
Carsten Bormann and the Token That Matched a Reply, Not a Person
A field small enough to fit inside a constrained message can still be asked to carry too much institutional meaning. CoAP’s design offers a better discipline: give each compact identifier one narrow job, preserve the surrounding evidence, and refuse to turn correlation into…
History
The Number That Said Goodbye So the Stream Could Continue: How RTP Resolved SSRC Collisions
Two live sources could enter one RTP session carrying the same 32-bit number. The protocol did not ask a central registry to decide who owned it. The source that found its own number in conflict sent goodbye for that label, selected an unused replacement and kept the media…
History
One XID, Two Executions: Why RPC Needed Memory Beyond the Reply Number
A remote call can be repeated with exactly the same number and still perform its work twice. ONC RPC made replies attributable; the harder task was preserving enough server-side history to say whether a retry was new.
IETF
Fernando Gont and the First Fragment That Had to Name What Came Next
An IPv6 fragment can arrive first without explaining what the completed packet is for. The source address is visible, the destination is visible and the fragment offset says zero, yet the transport header a firewall needs may be hiding in a later piece. RFC 7112, co-authored by…
Global Cloud Services Trends
Veeva's Salesforce CRM Has a 150% Per-Customer Cap and 2030 Exit
The legacy platform is neither open for ordinary growth nor scheduled to disappear tomorrow. Veeva's agreement with Salesforce has turned the old CRM into a bounded migration corridor: existing customers can still operate and expand within a fixed ceiling, while new customers and…