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.
IETF
Lukasz Kondrad and the RTP Group That Was Not Yet a Reconstructed Scene
A session description can place an atlas, occupancy, geometry and colour stream inside one V3C group. That is a precise statement about membership—not evidence that a receiver rebuilt the same three-dimensional scene.
History
The Request Was Queued. The File Still Had to Move: RFC 1068 and BFTP's Completion Boundary
In 1988, an Internet file-transfer experiment made the instruction outlive the terminal session. A user could leave after submitting a job; a daemon would remember, retry and report later. That persistence solved a human waiting problem, but it also created a new fact that was…
Global Cloud Services Trends
Intuit Put US$6.755bn Into Loans. Its Retained Balance Rose Just US$65m
Intuit’s loan business moved far more capital than its year-end balance suggests. During fiscal 2026, the company used US$6.755 billion to originate or buy notes intended for investment, collected US$4.253 billion of principal and received US$2.210 billion from loan sales. The…
IETF
Panos Kampanakis and the SSH Session with Three Different Security Receipts
An SSH client can negotiate a hybrid ML-KEM key exchange, verify the server through a conventional host key, and admit a user through a still separate credential. The session is one connection; the evidence is not one claim.
History
The FDDI Frame Carried IP. It Did Not Carry Identity: RFC 1188’s Encapsulation Boundary
An FDDI interface could put an IP datagram onto a fast local ring only after several small facts agreed: which link grammar carried the payload, how large a packet could be, and which local hardware address represented an IP neighbour. RFC 1188 made those facts interoperable in…
History
The Low-Delay Packet Was Given Less Room to Wait: RFC 1046's Queuing Bargain
In one of the Internet's early experiments with differentiated service, the faster class did not receive an infinite fast lane. It received a smaller waiting room. RFC 1046 proposed that a node bound delay by limiting the low-delay queue, discarding overflow and capping the…
North America Cloud Services Trends
Dropbox’s Cloud Carries US$285.9m of Finance-Lease Obligations
Dropbox looks like a subscription business until the raised floor comes into view. Its June accounts carried US$285.9 million of finance-lease obligations, while its engineers were describing racks, airflow, cooling and power headroom inside co-location facilities. The important…
History
The Mailbox Was a Contact. It Was Not a Control Room: RFC 1173’s “Oral Tradition”
Before the Internet had a single operational mythology, it had a more modest arrangement: if a problem crossed a boundary, someone needed to be reachable on the other side. RFC 1173, published in 1990, made that arrangement visible. Its lasting lesson is not that a role mailbox…
IETF
Cullen Jennings and the Capability Document That Was Not a Live SIP Trunk
An enterprise edge device can discover the right URL, pass TLS and OAuth, receive HTTP 200 and parse a valid provider capability document while no production call can cross the trunk. RFC 10006 makes configuration exchange easier; it does not collapse retrieval, activation…
ICANN
ICANN Changed ‘Five-Year’ to ‘Periodic’—the Audit Clock Still Runs
One word disappeared from ICANN’s Board Risk Committee charter, but the obligation behind it did not necessarily disappear. The adopted text now promises external assessment “periodically” under professional standards. Those standards still contain a five-year outer limit. The…
History
A Policy Sentence Was Not a Network Control: RFC 1087 and the Limits of “Acceptable Use”
In 1989, the Internet Activities Board could identify conduct that threatened a shared research facility. It could say that intentional intrusion, disruption, waste, destruction and privacy compromise were unacceptable. What it could not do with a sentence was observe an act…
History
The Bit Preserved a Return Path. It Did Not Authenticate the Request: RFC 1044's HYPERchannel SRC
In a physical network, an address can do something concrete without saying who is entitled to act. RFC 1044 gave HYPERchannel messages a Source Address Correct bit that could survive only while the declared return address remained usable in reverse. That was valuable path…
History
The Speed Was a Display Hint. It Was Not the Link: RFC 1079’s Telnet Boundary
In 1988, a remote terminal program could know something useful about the terminal at the other end without pretending to know the network between them. RFC 1079 made that distinction unusually crisp. It let one Telnet peer request a pair of terminal speeds and let the other peer…
Global Institutional Trends
Yum Sold Pizza Hut China for US$1.2bn; KFC's 3% Royalty Now Has a 12-Year Rebate
Yum! Brands completed a US$1.2 billion sale that turned Yum China from Pizza Hut's local licensee into the owner of the brand rights in Mainland China. One 3% recurring fee ended with that transfer. Yet the relationship did not end: KFC and Taco Bell remain under a separate…
IETF
Tobias Fiebig and the Four DNS Reachability Receipts
A zone can display two A records, two AAAA records and a reassuring “dual stack” label while still withholding names from an IPv6-only resolver. RFC 10001 replaces that label with four bounded claims: two authoritative services must answer over IPv4 and two must answer over IPv6…
History
Before DHCP, Four Bytes Chose the Grammar: RFC 1048 and BOOTP's 64-Octet Limit
Before a diskless machine could fetch its operating system, it needed enough network knowledge to ask for one. BOOTP carried that knowledge in a field only 64 octets long. RFC 1048 made the field intelligible across vendors with four opening bytes and a compact option…
History
The Name Was the Address. It Was Not a Route: RFC 1088’s IP-over-NetBIOS Mapping
In February 1989, RFC 1088 made an unusually literal bargain between two naming systems. A host carrying IP over NetBIOS would derive a 16-byte NetBIOS name from its IP address: `IP.XX.XX.XX.XX`, with each `XX` written as ASCII hexadecimal. The name was meant to let a NetBIOS…
Global Datacenter Trends
Arm Dropped RPO From Its Scorecard; 53% Still Sits Beyond Two Years
Arm has stopped putting remaining performance obligations in the operating-metrics table of its quarterly shareholder letter. The number did not disappear from the accounts. At 30 June, the financial-statement note still carried US$2.1226 billion of contracted work, with…
History
The Token Found the Connection. It Did Not Admit the Subflow: MPTCP's MP_JOIN Boundary
One new TCP SYN can propose to become part of a connection that began somewhere else, on another address pair, minutes earlier. That is the useful oddity in Multipath TCP. It is also where a casual description—“the session moved”—loses the decisions that keep continuity from…
IETF
Weiqiang Cheng and the SRv6 Locator Lease That Still Needed a Route
The DHCPv6 log can show a valid Reply, a locator, an IAID and two working clocks while the route table still has nothing to say. RFC 10038 makes that gap explicit: assignment is one controlled event; reachability must be created, distributed and observed through separate systems.