Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Offset That Could Not Name the File: How FTP Restart Assumed an Unchanged Object
After a large transfer breaks, a saved number feels like proof of progress. FTP could use that number to avoid sending the beginning again. But the number named a position, not the file version occupying that position. Resume worked only because both endpoints supplied an…
Story
Six Minutes Are Published. LACNIC’s Summary Column Says Nothing
LACNIC’s 2026 Board page presents six meetings, six dates and six links to approved minutes. Beside them sit six empty `Summary of activities` cells. The records exist; the map into the records does not. That difference determines whether a reader can find a decision without…
CASE FILE
The First Endpoint Was Preferred. It Was Never Eligible.
An HTTPS record can put one endpoint first and still require a client to ignore it. SVCB makes DNS a publisher of bounded connection plans, not a substitute for compatibility, endpoint authentication or running evidence.
IETF
Job Snijders and the Checklist That Could Sign Bytes, Not Truth
A cryptographic signature can settle a narrow argument and still leave the important business question open. Job Snijders and his co-authors designed the RPKI Signed Checklist to prove that a resource-authorized key signed a list of exact file digests. Its usefulness begins with…
IETF
The IAB Wants Age Rules to Name Outcomes, Not Freeze a Gatekeeper
Moving an age check from a website or a network into a personal device does not make governance disappear. It changes who holds the lever. In a statement published on 24 August 2026, the Internet Architecture Board argued that device-based age signals look more promising than…
History
The Name the Message Had to Mint Itself: How Message-ID Worked Without a Registry
A relay can add a trace field and change a message’s bytes without changing the message. An author can revise one sentence and create a new message even while most bytes remain. `Message-ID` gave that distinction a durable name, then let replies and distributed news servers build…
History
A Return Label Was Not a Shared Instruction
A RADIUS proxy could carry another proxy's private state without knowing what it meant. The common agreement concerned preservation, relative order and return, not a universal interpretation of every value. That small distinction left room for independent implementations while…
Story
ARIN’s 75% Gate Depends on a Plan That Can Change
Sixty assigned prefix units are 75% of a plan containing 80 units. The same sixty are only 60% of a revised plan containing 100. No address has moved, yet the qualification result has. Draft Policy `ARIN-2026-2` makes that possible in principle because its proposed…
CASE FILE
The Network Named a Provisioning Domain. It Did Not Choose the Path.
A Provisioning Domain can keep one network's addresses, resolvers and routes from contaminating another. It names a coherent context; it does not convert a Router Advertisement into a command that chooses a connection.
CASE FILE
The bridge was gone. The topology still crossed it
Two BGP-LS producers can each retain one stale half of a failed link. A consumer that merges their disclosures may reconstruct a plausible connection that no longer exists, and a controller may compute straight across it. The failure is not simply “bad telemetry.” It exposes who…
Story
APNIC’s First IPv6 PI Request Has No Previous Assignment
APNIC’s `prop-175-v001` offers to remove a peculiar round trip: issue a `/48`, wait for deployment, invite the applicant back, receive much the same network plan and assess the larger need a second time. Reusing the later-stage test is economical. It is also a change of state…
IETF
A Proposed Charter Is Not a Working Group Mandate
A document browser usually rewards the highest revision number. A governance register cannot. On 27 August 2026, the IETF showed DAWN's first charter proposal and NETCONF's proposed recharter under review at the same time. The newer text would create authority in the first case…
History
A Reservation Could Survive Without Being Rechecked
RSVP learned to keep previously advertised state alive by naming it instead of repeating its description. That reduced routine work, but changed what the routine could discover. A missing record could ask for repair; a recognisable record with the wrong contents was a different…
History
The Reply SMTP Could Not Divide: How LMTP Made Local Delivery Per-Recipient
One message reaches the local-delivery boundary with two accepted recipients. One mailbox can take it; the other is temporarily over quota. SMTP has one final answer for that transaction, so the receiver must own what happens next. LMTP changed the shape of the answer: one…
Story
Two Numbers on One Proposal: APNIC Must Correct Identity Without Rewriting History
`prop-174: Align implementation of Prop-125 in APNIC Policy (APNIC-127)` `prop-173: Align implementation of Prop-125 in APNIC Policy (APNIC-127)`
History
The Knock That Brought the Client Back
A DHCP server could know that a setting should change while its client had no reason to ask again. FORCERENEW gave the server an opening in that quiet interval. It did not give the opening message the power to complete the change.
CASE FILE
The route existed. The subscription did not
A VPN route can be valid, selected and available at its source while a remote PE correctly receives nothing. RFC 4684 lets Route Target interest travel toward the route and matching reachability travel back. That inverse graph saves state, but it also makes an absent or stale…
CASE FILE
The Child Has Spoken. Who Makes the DS Record Real?
A child zone can publish a perfectly signed request for its next DNSSEC trust state and still be rightfully refused. CDS/CDNSKEY automation works only when signal, acceptance, parent publication and validator observation remain separate facts.
History
Philip F. Smith and the Routing Report That Could Observe, Not Command
A daily BGP report begun in 1999 made routing behaviour public at a moment when registry records and operator claims could not show what the network was actually announcing. Philip F. Smith’s long-running instrument matters because it also exposes its own limits: a selected path…
Story
One Portal, Four Unfinished Clocks
MyAFRINIC v2 has become more than a software project: AFRINIC's own records place four materially different policy paths behind the same portal milestone, making it necessary to prove each implementation separately rather than letting one launch announcement stand for all four.