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 MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742
A management model is also a map of responsibility. In 1991, the first AppleTalk MIB let an SNMP manager write route fields and zone mappings while reporting how port settings had been obtained. Four years later, its replacement moved several of those lines. The revision matters…
History
The Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242
A clean throughput trial is seductive because it ends in one number. RFC 1242 gave that number a strict meaning, then surrounded it with other terms that refused to disappear. Zero loss at one offered rate did not answer latency, burst tolerance, overload, restart, filtering or…
History
The Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304
A number labelled total looks like the end of an investigation. In RFC 1304, it was the beginning of one. The 1992 MIB could count SIP packets discarded for protocol or bit errors, list other address-related failures and remember the latest disagreement of each syntactic type.…
History
The Tunnel Carried the Packet. The Error Lost the Question: RFC 1241
A tunnel can look transparent in the forward direction and become opaque the moment something fails. RFC 1241 drew that asymmetry with unusual precision. Its outer packet could carry an untouched IP datagram through a separate routing space. But an ICMP error from inside that…
NPNOG
Broken Dates, Empty Lists and Missing Slides: Can npNOG Preserve Its Own Memory?
npNOG’s public websites preserve a useful record of programmes, teaching materials and event continuity, but they also contain date conflicts, unfinished download promises and pages whose headings outlive their visible data. Those gaps do not prove that an event failed, a…
History
The MIB Arc Changed. Vendors Still Had to Revise: RFC 1239
Nothing in a management console announces that a number has become architecture. RFC 1239 did. Five MIBs kept describing familiar interfaces, yet their entity identifiers moved from an experimental branch to standard branches. The standards record changed in two pages; every…
North America Institutional Trends
AtaiBeckley’s Lilly Deal Has Two September Gates and a Seven-Year CVR Tail
Two timestamps, 47 hours apart, now organize Eli Lilly’s proposed purchase of AtaiBeckley. Stockholders are due to vote on 8 September. Australia’s merger waiting period is scheduled to expire on 10 September. Neither event is the closing, and neither turns the headline “US$6.75…
History
The Master Said Accepted. The Applications Had Not Reported an Outcome: RFC 1301
Twelve small verdicts travelled inside every Multicast Transport Protocol packet. One could say accepted, another pending, a third rejected. They looked like receipts, but they were not votes from twelve receivers. RFC 1301 gave one master the right to set those values after…
History
The Agent Spoke with One Voice. The Subtree Had Another Owner: RFC 1227
To a management station, an SNMP agent looked like one speaker. RFC 1227 placed a switchboard behind that voice: local processes registered branches of the MIB, priorities chose which process answered, and a broader branch could hide a narrower one. The reply was real, but its…
North America Datacenter Trends
Fervo’s 396MW Google PPA Comes in Four Tranches—and the 600MW Option Has a Reimbursement Tail
The nearly-one-gigawatt headline hides four different contractual states. Fervo Energy has signed a 396MW power purchase agreement with Google, divided into four 99MW deliveries. It must also offer roughly 600MW more, but that capacity becomes contracted only if Google accepts…
History
The Trap Carried 0.0.0.0. The Envelope Named the Agent: RFC 1298
An SNMP trap crossed an IPX network with four zeroes where its agent address might have been expected. That was not missing data by accident. RFC 1298 deliberately emptied the Trap-PDU field and told the receiving manager to take the source from the transport layer instead. The…
History
The Radio Frame Entered IP. Its Physical Edges Did Not: RFC 1226
A packet can cross a boundary without carrying every trace of the medium it came from. RFC 1226 put an AX.25 frame inside one IP datagram, discarded the HDLC marks that had framed it on a serial link, and retained the checksum. That choice made a useful tunnel format—and a…
History
The Host Said Down Before the Controller Had Finished: RFC 1307
A transport provider asked to release an expensive switched link. Its local control layer answered that the link was down, yet the external controller had not necessarily finished—or even recognised—the teardown transaction. RFC 1307 made that apparent contradiction part of a…
History
The Alarm Flood Stopped Itself. The Silence Still Needed a Ledger: RFC 1224
A quiet management console can mean that nothing is wrong. It can also mean that the alarm path deliberately shut itself down. RFC 1224 made that second possibility explicit: cap an agent's alert rate with a sliding-window pin, then keep a separate numbered log so silence did not…
History
The Desktop Showed One Directory. No Server Held the Whole Thing: RFC 1309
The promise looked almost magical in 1992. A person at one workstation could search what appeared to be a single worldwide directory, even though no central machine owned the complete collection. RFC 1309 explained the machinery behind that appearance: user agents, system agents…
History
The Protocol Asked for Multicast. The Network Sent a List of Copies: RFC 1223
HYPERchannel could carry the routing protocols of an imagined broadcast LAN, but it could not broadcast. RFC 1223 bridged that mismatch with a more revealing mechanism: keep a list of intended listeners, make one copy for each, and space the transmissions so the imitation did not…
History
One Router Held Two Domains. It Still Needed Two Owners: RFC 1222
The cheaper router in RFC 1222 was not supposed to abolish a boundary. It was supposed to house both sides of it. One routing process would speak for a service subscriber, another for the NSFNET Backbone, and an exterior protocol would still cross between them—even if the…
History
The Setting Said One Thing. The Port Reported Another: RFC 1317
An early network-management console could present a serial port with the authority of a control panel: speed, parity, character width, error totals, signal states. When the value on screen differed from the value an operator remembered setting, the easiest story was that somebody…
North America Institutional Trends
Korn Ferry’s £850m AMS Price Closed in Three Ledgers
Korn Ferry announced one approximate purchase price for AMS. At closing, the filed receipt became two currencies, an exact share count and an accounting clock. Those figures describe different perimeters. Until the exchange-rate, completion-price and purchase-accounting bridges…
History
The Switch Accepted the Message. The Destination Still Had No Receipt: RFC 1221
In 1991, the Host Access Protocol could return an acceptance for a numbered message at the edge of the Terrestrial Wideband Network. The word sounded conclusive; the specification was not. Acceptance closed a local Host–Wideband Packet Switch question so buffers could move on. It…