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.
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…
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…
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…
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.
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…
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.
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…
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…
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…
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.…
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…
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.
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.
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…
History
The Activity Could Travel. Execution Stayed with the URAgency: RFC 2016
RFC 2016 imagined an Internet task as a durable entity that another person could inspect, change and run again. Yet the entity did not execute itself. A URAgency still decided how its type became runnable code, which dependencies were trusted, where targets pointed and what a…
CASE FILE
The Flag Field Was Extended. No Prefix Property Had Been Defined: RFC 9792
RFC 9792 made room for future OSPF prefix facts without claiming that any such fact yet existed. That small act of restraint creates a useful test for every routing-control assertion: identify the container, the assigned bit, the sender's bytes, the receiver's rule and the…
Europe and Middle East Regional ISP
ROYA’s AS210837: The Missing Step Between Network Identity and Operating Control
ROYA’s AS210837: The Missing Step Between Network Identity and Operating 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…
History
Hawaii Internet Exchange: What Public Routing Records Cannot Yet Prove
Hawaii Internet Exchange: What Public Routing Records Cannot Yet Prove 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.…
History
The Third Duplicate ACK Opened a Temporary Window: RFC 2001’s Recovery Ledger
RFC 2001 did not turn three repeated acknowledgments into certainty. It turned them into a bounded permission: retransmit one apparently missing segment, keep the ACK clock moving through a temporary window adjustment, then remove that extra allowance when new data is…
IETF
Leslie Daigle and the URN Namespace That Needed a Steward, Not a Resolver
A persistent name is easy to mistake for a durable hyperlink. Leslie Daigle’s work on the rules for Uniform Resource Name namespaces made the harder bargain visible: the name survives only if an institution keeps assigning it consistently, never recycles it and preserves the…