Primary Domain
Internet Governance
Within the Primary Domain facet, Internet Governance 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
Susan Estrada and the Network That Had to Account for Its Customers
An early Internet provider could prove that packets moved and still leave its customer unable to judge the service. Susan Estrada's work at CERFnet shows why commercial acceptance required another layer: reports, monitoring, support and a shared language for responsibility.

History
Laura Breeden and the Work Between a Connection and Adoption
An early federal evaluation found Internet projects that had acquired technology before asking what a community needed, leaving systems unused or badly underused. Laura Breeden's career explains why that failure belongs inside Internet history: a network becomes public…

History
The Checklist Was Retired. The Evidence Question Moved: RFC 1264
In 1991, a routing protocol did not advance merely because its specification looked complete. RFC 1264 asked for separate receipts: independently written code, tests for every feature, security demonstrations, operational history, and an account of where the design would break.…

ICANN
ICANN’s Priority Number Does Not Order String Evaluation. Which Five Checks Run Outside the Queue?
An applicant draws a low Priority Number and immediately gains a story to tell: its application is near the front of ICANN’s processing queue. That story is useful, but incomplete. The number does not place every part of the application near the front of every line. ICANN’s own…

SANOG
South Asia Asked for Invalid-Route Data and a Place to Test ROV
At the first South Asia APNIC Sub-Regional Forum, operators moved the routing-security conversation beyond awareness. They asked for the evidence and controlled environment needed to practise a change that can affect which routes a network accepts.

Story
At LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4
LACNIC’s rules ask a first-time operator to show that customers and equipment already justify an address block. Exhaustion then sends that approved need into a private market. The rule is neutral on paper; the sequence is not neutral between a network starting from zero and one…

Story
LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses
LACNIC’s IPv4 queue does not preserve a block for every approved applicant. It preserves an identity-bound place in a sequence whose supply, order, final approval and address quality remain unsettled until recovered space is actually released.

ICANN
A Proxy Clause Without a Private Enforcer: Balsam v Tucows
Daniel Balsam had a seven-figure judgment and a contract clause that seemed to point straight at the missing identity. What he did not have was the legal position from which to enforce that clause against the registrar.
