Skip to main content

Primary Domain

Internet Infrastructure

Within the Primary Domain facet, Internet Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.

IETF

The Interface Still Said Up While the Carrier Was Down

A quiet status light can be the most dangerous signal in a recovery room. Revision 19 of the IETF's common interface-extension draft deliberately permits an interface to remain reported as up while a short down timer is running beneath it. That is useful engineering, not…

Sep 11, 2026
A pale inner IPv4 packet with its own TTL dial travels inside a dark outer envelope marked 04 and DF, whose fragments reassemble at a tunnel exit before the inner packet continues toward an unreached service light.

History

Protocol 4 Is an Envelope Label, Not a Delivery Receipt: RFC 2003

A monitor sees an IPv4 packet from one router to another and reads `4` in the outer Protocol field. That observation is precise but small: it says another IPv4 datagram should follow. It does not name the original sender, validate the inner route or show that the letter inside…

Sep 11, 2026
Layered illustration of software stewardship, downstream operations, registry authorization and routing observation as distinct internet infrastructure control surfaces.

Global Institutional

Where ISC’s Control Ends—and the Evidence of Recovery Begins

Where ISC’s Control Ends—and the Evidence of Recovery Begins 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 Global…

Sep 11, 2026

IETF

The Preference Won the Election. It Did Not Prove the Forwarder Was Ready: RFC 9785

An operator can make one EVPN Provider Edge router the obvious administrative favourite. RFC 9785 gives that intention a precise place in the DF election. What it does not give is a shortcut from “preferred” to “safe to carry traffic”. The standard opens a control surface…

Sep 11, 2026

IETF

The XML Matched. The Network Did Not

Two configuration documents can be well formed, stable under XML canonicalization and accepted by a validator, yet still fail to describe the same effective YANG data—or any change that a device actually applied. The first NETMOD draft dedicated to YANG’s XML encoding makes the…

Sep 11, 2026
AI editorial portrait of Dave Täht beside two matching network test rigs and a separate invalid run limited by its processor

History

Dave Täht and the Result That Had to Be Reproducible

A failed run can be more valuable than a beautiful graph. Dave Täht’s work on network latency made that unsettling proposition practical: if the apparatus cannot expose why a result is invalid, the result is not yet evidence.

Sep 11, 2026
A paper envelope holds only an amber retrieval line that crosses a separate gate to a sealed external object, with an independent cyan integrity path.

History

The Message Had an Address, Not the Object: RFC 2017

In October 1996, RFC 2017 gave MIME mail a way to point at an external entity with a URL. Its economy was the point—and the trap. A locator could arrive intact while the content stayed elsewhere, retrieval still needed permission, and neither a declared type nor a matching digest…

Sep 11, 2026
Editorial illustration of an autonomous system surrounded by distinct evidence pathways for registry records, BGP observations, IRR policy and RPKI authorization, with unresolved gaps showing the limits of proving operational control.

Global Institutional

What AS210764 Can—and Cannot—Prove About ISC’s Operational Control

What AS210764 Can—and Cannot—Prove About ISC’s Operational Control 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…

Sep 11, 2026
Abstract network diagram showing AS210833 connected to registry records, BGP routes, RPKI validation and interconnection links, with unresolved connections fading into darkness.

Number Resource Society

Florian Bauer and AS210833: What the Public Record Can Test About Network Stewardship

Florian Bauer and AS210833: What the Public Record Can Test About Network Stewardship intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…

Sep 11, 2026
An archival network ledger with a fixed brass plate linked to a translucent temporary tag and an expiry timer, while packet paths diverge into an indistinct endpoint.

History

The Binding Was Accepted; the Location Was Not Proven: RFC 2002

Mobile IP’s first standards-track design separated a durable network identity from a temporary delivery instruction. The home agent could authenticate and accept that instruction, yet neither act proved where the device physically was—or that a packet completed its journey.

Sep 11, 2026

Global Regional ISP

AS210833 and the evidence gap between registration and stewardship

AS210833 and the evidence gap between registration and stewardship 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…

Sep 11, 2026
AI editorial portrait of David Clark beside separate file-transfer checks whose local confirmations do not prove the final stored copy

History

David Clark and the Reliability the Network Could Not Finish

A subsystem can be flawlessly honest about the work it completed and still be unable to answer the question its user actually asked. David Clark’s end-to-end reasoning begins in that gap.

Sep 11, 2026

Global Institutional

DFINFRA and AS210860: The Evidence Stops Before Operational Control

DFINFRA and AS210860: The Evidence Stops Before Operational Control 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…

Sep 11, 2026
A systems illustration showing the operational control chain from upstream DNS and DHCP software stewardship through distribution, deployment, monitoring and tested recovery.

Global Institutional

ISC’s operational control ends where deployment evidence begins

ISC’s BIND and Kea projects are widely documented and publicly maintained. The harder accountability question is narrower: which parts of continuity can ISC demonstrate, which parts belong to distributors and operators, and what evidence would show that a repair survived contact…

Sep 11, 2026

Europe and Middle East Cloud Services

AS210775 Is a Registry Endpoint, Not Yet a Running Network

AS210775 Is a Registry Endpoint, Not Yet a Running Network 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 Europe…

Sep 11, 2026

Story

Xiamen Tashan Network Technology and the Evidence Gap Around AS151194

Xiamen Tashan Network Technology and the Evidence Gap Around AS151194 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.…

Sep 11, 2026

IETF

A Newer Date Can Belong to the Wrong Branch

Revision 17 of the YANG module-versioning draft makes revision history honest about forks, marks potentially incompatible steps and lets servers describe their treatment of retired nodes. Its metadata can expose risk early. It cannot tell an operator that the selected dependency…

Sep 11, 2026
AI editorial portrait of Lixia Zhang beside separate downstream and upstream RSVP signals, with one refresh-dependent state module fading after updates stop

IETF

Lixia Zhang and the Reservation That Expired Without a Refresh

A reservation sounds like something placed and possessed. In RSVP, it was something more disciplined: distributed state that had to keep earning the present tense.

Sep 11, 2026

Global Institutional

DFINFRA and AS210860: The Missing Continuity Loop

A registry association can identify where to investigate, but continuity is demonstrated only when routing, reachability, recovery authority and customer consequence align in time.

Sep 11, 2026

Global Institutional

What AS33169 Can Prove About Utherverse Network Operations — and Where Continuity Still Disappears

What AS33169 Can Prove About Utherverse Network Operations — and Where Continuity Still Disappears intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Sep 11, 2026