Topic
Registry Governance
Within the Topic facet, Registry Governance topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
ICANN
Administrative Check Is a Filing Gate, Not a Merits Decision
ICANN’s Administrative Check verifies filing facts and prepares identical-string sets; it does not approve an application on its merits.
Story
AFRINIC's IPv4 Pool Plan Needs Two Ledgers
An AFRINIC draft sets out exact rules for recovered addresses and a post-exhaustion queue. Its procedural history shows why operators also need an exact record of when those rules acquire authority.
Leaders
Mirjam Kühne and the Forum That Had to Become a Journal
A post-Christmas spam problem revealed the editorial work required to keep an open technical publication useful: selection, moderation, format and a named hand-off.
Story
ARIN’s Incoming-Reassignment Switch Makes Registry Association Consent-Bound
An organization identifier used to be available for an upstream provider’s reassignment workflow unless another requirement failed. Since ARIN’s January 2026 release, the recipient can refuse that association before it is created. The new switch changes registry accountability in…
ICANN
One RSP Evaluation Can Cover Many gTLDs—Only for Qualified Services
One evaluation may be reused across gTLDs, but ICANN qualification remains tied to specific registry services.
Story
AFRINIC's PDP Continuity Plan Needs an Authority Map
AFRINIC's latest working-group proposal tries to keep policy development alive when corporate governance stalls. Its strongest ideas are procedural; its hardest question is who may lawfully act when the Board cannot.
ICANN
RSP Coverage Is a Function Map, Not a Provider Count
An applicant can name several Registry Service Providers and still leave a critical registry function uncovered. ICANN’s 2026 Round framework is role-specific: Main, DNS, DNSSEC and optional Proxy RSPs carry different functions and different limits on how many may serve a gTLD.
ICANN
Naming an RSP Is Not Contracting Confirmation
An applicant can identify a Registry Service Provider in its application, while ICANN separately seeks confirmation from that provider during contracting. The applicant’s selection, ICANN’s request and any actual RSP response are distinct evidence events.
Story
AFRINIC's Compliance Dashboard Needs an Appeal Path Before a Sanctions Path
AFRINIC is considering a member-facing compliance dashboard that could make policy obligations easier to see. Its own impact assessment shows why visibility must be separated from enforcement before a coloured status becomes a route to withholding services, revoking resources or…
ICANN
RSP Selection Can Wait Until Evaluation, Not Indefinitely
ICANN’s 2026 rules allow an applicant to submit without naming Registry Service Providers, but that flexibility narrows at evaluation: minimum critical registry functions must be covered, or Extended Evaluation may provide more time.
ICANN
Variant-String Sets Enter Contention Together, Not String by String
ICANN’s 2026 rules treat a primary string and its applied-for allocatable variants as one contention unit when different applicants seek strings from the same variant-string-set. That changes how applicants should map competitive exposure.
Story
LACNIC’s PAI Client Documents Java 8. Its Latest JAR Requires Java 17
The public instructions offer a familiar promise: Java 8 or later. The latest downloadable library makes a different, equally precise statement in its own bytes. Every class in the observed 1.5.1 JAR is version 61—the class-file level for Java 17. The code and the documentation…
Story
APNIC’s API Outage Notice Did Not Name the Registry API
One hyphen separates `api.apnic.net` from `registry-api.apnic.net`. APNIC’s 5 August incident notice named the first host and five affected member-facing or public services. Its published Registry API specification names the second host for authenticated changes to…
CASE FILE
The Registry Said 200. The Domain Command Failed
The newest EPP-over-HTTPS draft makes a deceptively simple distinction operationally unavoidable: `200 (OK)` can mean the command reached the registry application, not that the registry accepted it. Once registration traffic passes through load balancers, retries and distributed…
Story
ARIN Plans ROA Impact Warnings for the Web, Not the API
ARIN is building a warning for the moment before a Route Origin Authorization changes what observed routes look like. The warning belongs to its web interface. The registry’s programmatic writer is still expected to assemble the same evidence elsewhere. That is not a difference…
Story
ARIN’s Off-Earth Address Draft Has Four Locks Before the First Allocation
A proposal can describe addresses beyond GEO, but a registry service cannot begin until four separate institutions settle four separate questions. BTW recommends making that chain publicly reviewable before operational clauses are treated as ready.
Story
The IANA Review Called Outreach Sufficient. AFRINIC Had No Voting Community Member
The 2025 IANA Numbering Services review reached a supportable technical result and met its global quorum. Its own records nevertheless show a narrower institutional fact: a committee designed for ten community voters listed only eight, because AFRINIC’s two community places were…
ICANN
Existing gTLD Variant Applications Receive Processing Priority, Not Approval
ICANN gives one class of applications an earlier place in the processing order: allocatable-variant applications for existing gTLDs from the 2012 Round. That priority changes sequencing, not the substantive outcome.
Leaders
Razvan C. Oprea and the Discipline of Naming Operational Limits
The most revealing moments in Razvan C. Oprea’s public work are not declarations of success. They are the moments when a measurement fails to show what it was expected to show, when a research project draws a line around what its data can establish, or when a technical strategy…
Story
ARIN’s Harmonization Draft Needs a Semantic-Diff Ledger
ARIN-2026-4 presents itself as clarification, but two nearly parallel clauses differ in actor and modal force: the current text says registration “guarantees” uniqueness, while the proposal says a public registry is “necessary” to ensure uniqueness of allocated resources. Those…