Intelligence

Latest Articles

Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.

Five glass requirement gates stand before separate open chambers for dependencies, classification, old clients, retired nodes and migration.

IETF

The Requirements Were Written. The Solution Was Not Proven

Revision 14 gives YANG versioning work a disciplined list of obligations: evolve modules without detonating dependency graphs, disclose compatibility, protect old clients, clarify retired nodes and explain migration. Its value is the questions it preserves. A requirements…

AI editorial portrait of Mary Ann Horton in an early-1980s computing room with dial-up equipment and a volunteer-maintained route map

History

Mary Ann Horton and the Dial-Up Network That Had to Publish Its Own Map

Before an email address became a name, it could look like a set of directions. Every exclamation mark told a queued message which machine to visit next — and every omitted or stale hop could leave it stranded.

A narrow cyan route leaves a massive dark address block while an amber path loops beside a broad default corridor and a dark sink.

History

One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test

Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an…

A blank support ticket passes through three brass verification gates into one unranked queue beside an unnumbered timer.

Story

AFRINIC Can Close a Support Ticket After About Ten Working Days. It Never Ranks the Risk.

A registry is right to ask who is touching its records. AFRINIC's public Contractual Obligations Check makes that defence concrete: the sender must be registered, the member must be in good standing and a signed agreement must be on file. The problem begins after a check fails.…

An anonymous device passes through a narrow cyan allowlisted provisioning corridor as an amber shutter closes behind it and a separate authenticated path begins beyond another gate.

IETF

The eap.arpa Lane Must Close After Provisioning

The dangerous moment in device onboarding is not always the first packet. It can be the quiet minute after a certificate has been delivered, the dashboard has marked provisioning successful and the temporary access rule is still alive. RFC 9965 gives an uncredentialed EAP peer a…

A cyan route carries an abstract address-and-person token through several translucent monitoring branches toward an authorization aperture, while an amber route carries an opaque geometric handle below.

Story

LACNIC's Open-Source Election Lookup Puts the Email Address in the Request Path

LACNIC's open-source election system authenticates a participation lookup before returning its answer. Yet the documented interface has already placed the entity identifier in the part of the request most likely to be copied by infrastructure. The distinction is not a disclosed…

AI editorial portrait of Jean Armour Polly at a 1992 public-library desk beside a period computer, modem, telephone and subtle network paths

History

Jean Armour Polly and the Internet Connection That Still Needed a Librarian

In 1992, “going online” at a public library did not begin with a browser. It began with a desk computer, communications software, a modem, a telephone line — and somebody who could turn that fragile stack into a public service.

Amber and cyan schema tracks coexist through an asymmetric gate before separated glass evidence chambers.

IETF

Two YANG Versions Can Coexist While the Effective Schema Still Diverges

An upgrade can look calm precisely when its most consequential uncertainty has moved downstream: `draft-ietf-netmod-yang2-00` lets an older importer and a YANG 2.0 dependency remain together, but that accommodation proves far less than a shared client view of the network.

A glowing local network-state chamber feeds a branching multicast path whose red broken branch ends at a dark receiver.

IETF

The Router Remembered a Listener. The Receiver Saw Nothing: RFC 9777

MLDv2 gives an IPv6 router a disciplined account of multicast interest on one attached link. The danger begins when that local, aging account is promoted into proof that an authorized application still wants the traffic—or that the traffic arrived.

Separate archival workstations for chairing, editing, records, publication, approval, architecture and parameter custody surround a thick central dossier and an open blank register.

History

The Org Chart Was Not the Decision Log: RFC 2028 and the Map of IETF Responsibility

In 1996, RFC 2028 put the people and institutions of the IETF standards process into seven public pages. The map made responsibility easier to locate. It did not prove that any named role had acted, that a record was complete, or that the same allocation of authority still…

A provisional YANG artifact passes through a validation chamber into two matching publication vaults while four downstream evidence chambers remain separate.

IETF

Two Published Copies Can Match Before Any Device Changes

Revision 03 of a NETMOD working-group draft proposes a careful handoff for normative YANG modules: keep them visibly provisional through IESG approval, finish the bytes under RFC Editor control, validate again, and only then let the RFC and IANA copies appear together. That…

A cyan point-to-multipoint tree reaches a bounded row of leaves while a separate gold evidence layer verifies the authorized audience and one amber leaf remains disconnected.

IETF

A P2MP Tree Is Not an Audience Mandate

The operations screen is green. A ping addressed to a particular point-to-multipoint tree instance has returned from every expected leaf. The controller has built the efficient branches, the labels agree, and the old instance is ready to be removed. None of those facts answers…

A small orbital craft moves above five identical sealed registry drawers while an empty brass selector ring points to none.

Story

A Space IPv6 Draft Gives Every Planet Up to Five RIR Prefixes. It Never Defines the Region.

The appealing part of a new space-address proposal is that it does not start a sixth registry from scratch. The harder part is hidden in two words. Applicants would use their “appropriate RIR”, but a moving spacecraft has no obvious place on a map built for terrestrial service…

Eight distinct credential wafers sit above blank metal labels while a cyan action trail returns through a glass audit lens to one exact wafer and layered purpose cards await attachment.

Story

ARIN Can Trace an API Key. Its Dashboard Still Cannot Say What the Key Is For

ARIN tells customers to separate credentials so that actions can be traced, but its public key-management guide says those credentials are identified only by prefix and creation date. The missing description field is a small interface omission with a large operational…

AI editorial portrait of Nancy Hafkin beside a dial-up node, queued messages, distributed African network points and organised development records

History

Nancy Hafkin and the Network Before the Connection

Long before an always-on Internet line became ordinary across Africa, Nancy Hafkin’s programmes had to solve a harder problem: how to make information, institutions and people form a network when the connection itself was intermittent.

A luminous registry source divides into a red blocked path, an amber uninspected path and a cyan path through an explicit analysis chamber.

IETF

A Standards Action Can Authorize a Field. It Cannot Certify the Firewall: RFC 9778

RFC 9778 gives new IGMP values a high-visibility approval path. It also exposes a harder operational truth: a legitimate Type, Code, or extension flag can still be unknown to the security device deciding whether the packet is declined, inspected, or forwarded.

Unlabeled issue cards split into four paths before an unfinished blueprint and an incomplete bridge to deployed systems.

IETF

Four Buckets Did Not Make a Standard

Revision 00 of YANG Next Agreement turns a crowded GitHub issue pool into four decision lanes. That is useful scope control. It is not, however, a vote, a language specification or evidence that any tool or network can safely run what the lanes contain.

One distributed server worker alone acquires a luminous saved path memory and sends a paced cyan probe toward a shared bottleneck, while an orange retreat revokes the state.

IETF

A Saved Congestion Window Is Not Reusable Capacity

A server remembers that yesterday’s connection moved quickly. A new connection arrives at the same address, so the server is tempted to start where the old one finished. The memory is useful, but the capacity is gone: another flow may occupy the bottleneck, anycast may have…

Two point-to-point endpoint instruments face a central mechanical negotiation gate with blue acceptance, amber alternative and red rejection paths; a lower admitted path fades before reaching any distant service.

History

The Tokens Diverged. The Endpoint Was Still Unproven: RFC 2023

RFC 2023 gave early IPv6-over-PPP links a precise local bargain: establish the data link, enter PPP’s network phase, negotiate different 32-bit tokens, and only then admit IPv6. Every receipt in that sequence stopped short of identity, ownership, reachability and delivery.

Editorial illustration separating the AS211513 registry record from independently observed BGP routing evidence.

Number Resource Society

AS211513: What the public record can—and cannot—establish about EBL

AS211513: What the public record can—and cannot—establish about EBL intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…