Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
RFC 2057: the 1996 argument over who controlled the audience
In 1996, sending an email to a mailing list could hand its onward distribution to another operator's program. Scott Bradner's RFC examined the distance between controlling that first transmission and establishing the identity and age of everyone it eventually reached.
History
Rob Blokzijl and the Chair That Could Coordinate but Not Command
The most revealing sentence in RIPE’s first terms of reference is not the one that declares a European ambition. It is the sentence that withholds power. RIPE was not a network provider, and the networks cooperating through it remained under the executive authority of their own…
CASE FILE
RFC 9746: the compatibility cost of choosing EVPN split horizon
A default-method entity can send an upgraded Ethernet segment back to its encapsulation baseline. The operational question is whether the network has kept the resources and evidence needed to make that return safely.
IETF
An Authenticated BGP Update Is Not an SD-WAN Tunnel Admission Record
When a protected control-plane session delivers a syntactically valid route, it is tempting to treat the event as one completed act of trust. In an SD-WAN, however, the update has only crossed the first of several institutional boundaries. The harder question is not whether BGP…
History
Qiheng Hu and the 64K Link That Needed Authority at Both Ends
By the end of 1993, the network was technically ready. Its domestic backbone joined three academic systems, its team had chosen TCP/IP, and the international circuit had been provisioned. Yet packets still did not cross. Qiheng Hu’s part in China’s full-function Internet…
IETF
A BMP Percentile Is Local Until Its Sampling Method Travels With It
A router can report a P95 that is correctly encoded, correctly attributed and still unsafe to compare with the P95 from the next router. The missing link is not another decimal place. It is the method that selected the observations from which the percentile was made.
Story
LACNIC Asked for a Technical-Committee Charter. Its First Committee Ran the Registry.
LACNIC’s Board has found a sensible reason to create a technical committee and an equally sensible reason to fear one. Directors need a place to understand technologies that may reshape the registry. They do not need a second operations room. The distinction sounds obvious until…
History
RFC 2056 and the Fork in a Z39.50 URL
In 1996, RFC 2056 gave two URL schemes to Z39.50 because one locator could conceal two very different kinds of work. One scheme entered a continuing, stateful inquiry; the other attempted a tightly bounded retrieval of a server-identified item. The distinction is a small piece of…
CASE FILE
RFC 9747: the neighbour returns a packet, not a health declaration
Unaffiliated BFD Echo removes the need for the far end to speak BFD. That useful simplification leaves the local operator owning both the test and the decision made from its result.
History
Jun Murai and the Address Space That Became a Trust
The number is oddly exact: 14,680,064 IPv4 addresses. They were neither a fresh registry allocation nor abandoned space waiting to be reclaimed. They were seven-eighths of an old Class A block, held through three decades of changing Internet institutions, and in 2020 Jun Murai…
IETF
IPv6-Only Is a Scoped Forwarding Claim, Not an IPv4 Decommission Certificate
The phrase “IPv6-only” sounds like a clean finish line. In an operating network it can describe something much narrower: one link natively forwards IPv6 while IPv4 still reaches users through translation, another plane remains dual-stack, and a management path still depends on…
History
Kilnam Chon and the Router Asia Could Not Buy
On 15 May 1982, two computers in South Korea began speaking across a 1,200 bps leased line. The connection was modest; the missing box beside it was more consequential. With no obtainable IP router, Kilnam Chon’s group treated published protocol documents as equipment they could…
IETF
A Valid CoSERV Result Is Not a Completeness Proof
A relying party asks for the reference material needed to judge attestation evidence. The query is deterministic, the response is signed, the contents are still valid and every cryptographic check succeeds. That is a strong result—but a bounded one. The exchange proves what was…
Story
ARIN Can Attach a Ticket to an Org ID. That Does Not Make It the Organization’s Decision.
ARIN fixed a mundane but costly support problem: staff no longer need to begin every ambiguous question by asking which organization it concerns. The resulting Org ID selector gives a ticket context and a durable home. That is good service design. It also makes one distinction…
History
The Zero Handle Opened a Door. It Did Not Grant Entry
In 1996, RFC 2054 tried to remove two conversations that stood between an NFS client and its first useful file reference. Its answer was not a new permission system. It was a disciplined gamble: try the port most servers already used, try the newer protocol first, and present a…
History
Kees Neggers and the Backbone Europe Built in Parallel
On 26 September 1992, one link between London and Montpellier completed Ebone’s initially defined backbone. The more revealing number was not its line rate but its age: 390 days since a small group had first met outside Amsterdam to ask whether Europe could operate a shared IP…
IETF
A Token Status Bit Is Not a Revocation Timeline
A relying party reads one compact value and declines a credential. The decision may be correct. Yet the bit alone cannot say when the underlying state changed, who authorised that change, when the list exposed it, which cached copy was consulted or why this application treated…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
History
The Configuration Row Vanished. RFC 2051 Kept the Session Alive
RFC 2051 turned an obscure APPC management model into a durable lesson about evidence: the record of what should exist can disappear while the record of what is already running remains true.
IETF
The Zone Was Still Answering. The Signing Key Was Already Gone
A correctly signed zone can outlive the private key that produced it. That interval is not recovery; it is a perishable option whose value depends on preserving old cryptographic state while proving, clock by clock, that a replacement chain has taken over.