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
Hugo Krawczyk and the Public Salt That Is Not Password Hardening
A value may be public, repeated and still do important cryptographic work. That is the apparent paradox at the centre of HKDF. Hugo Krawczyk’s extract-then-expand design makes the answer operational: salt, source entropy and application context are separate inputs with separate…
IETF
Suzanne Woolf and the Server Label That Is Not a Machine Identity
A DNS reply can carry a label for the server that produced it. That sounds like identity until anycast, operator-defined bytes and hop-by-hop scope are allowed back into the picture. Suzanne Woolf’s work on the requirements behind NSID offers a more useful interpretation: the…
IETF
Sara Dickinson and the Resolver Promise Encryption Cannot Prove
The padlock beside a DNS resolver name is reassuring because it proves something useful: the client has protected its conversation on the way to a particular service. It is also dangerously easy to ask that icon to prove the rest. Sara Dickinson’s co-authored RFC 8932 follows the…
Leaders
Nurani Nimpuno and the Accountability Layer Behind Number Governance
Internet number governance is often described through institutions and acronyms. Nurani Nimpuno’s public record reveals a more useful operating question: how can a community preserve technical discretion while making delegated authority reviewable?
IETF
Ole Trøan and the Three Decisions NAT Used to Hide
A laptop has two globally usable IPv6 addresses, two routers and two DNS resolvers. Nothing is missing, yet the first packet can still fail: the chosen source may belong to one provider, the chosen door to another, and the chosen name answer to a third context. Ole Trøan’s…
Leaders
Kanchana Kanchanasut and the Infrastructure Hidden Inside a First Connection
The celebrated moment in Kanchana Kanchanasut’s career is an early connection: an email link from the Asian Institute of Technology to colleagues outside Thailand. The more durable story is what had to come after that experiment—addressing, operating institutions, training and a…
IETF
Tim Chown and the Host List Hidden Inside an IPv6 Address Plan
IPv6 made blind enumeration uneconomic, but it did not abolish reconnaissance. Tim Chown’s work shows how addressing conventions and operational exhaust can turn an immense namespace into a succession of small, testable target lists—and why defenders face the same discovery…
IETF
Brian Haberman and the 40-Bit Global ID That Was Not an Allocation Receipt
A locally generated IPv6 prefix can be extraordinarily unlikely to collide with another one and still carry no guarantee. Brian Haberman’s work on RFC 4193 makes that distinction operational: probability reduces coordination cost, but only an inventory, a route decision and a…
ICANN
Allison Mankin and the Name-Collision Sample That Could Not Prove Its Cause
A root server can record a query for a private-looking name with great precision. The record still cannot say which application produced it, who owns the broken dependency, how many users rely on it or what a future delegation would harm. Allison Mankin’s work on RFC 8023 helps…
IETF
Radia Perlman and the Appointed Forwarder That Had to Stop Forwarding
A TRILL switch may still hold the appointment for a VLAN while its safest legal action is to drop the native frames it would normally handle. That is not a contradiction in the standard. It is the moment when recorded authority and permission to act must be read as separate…
Leaders
Hisham Ibrahim and the Measurement Problem Inside Community Building
When RIPE NCC reorganised its community work in 2021, Hisham Ibrahim inherited more than a collection of events and services. He inherited a harder management question: how can an institution tell whether community activity creates lasting value rather than merely producing a…
Leaders
Daniel Fett and the Issuer Field That Named the Server, Not the Token
An OAuth callback can contain the right state and a real authorization code and still be on its way to the wrong server. RFC 9207 adds one small comparison before that mistake becomes a disclosure: did the server named in the response match the issuer the client recorded when the…
History
The Address Was Supposed to Declare the Charging Rule Before Contact: RFC 1681
In 1994, one IPng paper imagined a Gopher server redirecting a caller to a paid destination before any useful warning could appear. Its answer was to make the destination address speak first: some bits would identify who paid, or point to a charging algorithm. RFC 1681 exposed a…
History
The Test Measured the Reserve by Spending It: RFC 1628
A UPS exists to preserve power when ordinary supply disappears. RFC 1628 defined a diagnostic that learned more about that reserve by deliberately drawing it down. The result could improve confidence in battery replacement and run time, but the test left the protected load with…
History
The Address That Had to Be Empty: How SMTP Stopped Errors from Mailing Errors
The most important address in SMTP is sometimes no address at all. A delivery failure has to travel back to the system responsible for the original message, yet a failure to deliver that failure must not produce another failure notice, and another after that. `MAIL FROM:<>`…
History
The Address That Recruited a Subnet: Why Routers Stopped Forwarding Directed Broadcasts
One IPv4 datagram could cross the Internet as an ordinary routed packet, reach the router responsible for a remote network and become a local broadcast there. With a victim's address forged as the source, that last-hop conversion could turn willing hosts on someone else's subnet…
History
The Link That Borrowed Its Address: How Relative URLs Made Documents Movable
A short hyperlink is not a small absolute address. It is an instruction to borrow missing components from a base. That dependency let authors omit repeated schemes, hosts and path prefixes, and it let a collection of pages move while preserving its internal edges. The economy…
IETF
A QUIC STREAM Frame Carries Byte Ranges, Not Application Messages
A packet trace can show a complete STREAM frame while telling you nothing conclusive about whether an application request was complete, parsed, accepted, or committed.
Global Cloud Services Trends
A CDN-Cache-Control Field Is Not a Chain-Wide Cache Policy
`CDN-Cache-Control` lets an origin address CDN caches separately from other HTTP caches. That is a useful control surface, but the field is not a declaration that every cache on the path will apply the same policy. Recognition, parsing, target-list order and forwarding still…
Leaders
Hans Petter Holen and the Chair That Needed a Selection Process
A trusted personal handover placed Hans Petter Holen in the RIPE Chair role in 2014. By 2020, the more consequential achievement was a community process designed to make the next transition less dependent on any one person.