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.
Story
AFRINIC Named Its Next CEO. He Takes Office on 1 January
The appointment is public. The decision date is not. And the authority of the office does not follow from the title “CEO Designate” before the announced start date.
Story
RIPE Rebuilt LatencyMON. A Chart Still Needs Its Own Interpretation Receipt.
RIPE NCC has rebuilt LatencyMON, the RIPE Atlas view used to compare latency trends across probes. The update makes a great deal more of the measurement surface visible: more test types, a choice of grouping logic, an option to reach beyond the aggregated time range and a…
Story
RIPE NCC Fixed a Cross-Service Vulnerability. The Remediation Needs a Chain Receipt.
“Fixed” is a useful word only when a reader can tell what changed its meaning. RIPE NCC’s June account of a multi-service vulnerability disclosure makes that distinction unusually visible. It describes several issue categories across more than one service, and it also says that…
IETF
Qin Wu and the Registry Rule That Had to Catch Up With Practice
The same YANG module name appears three times in IANA’s register, attached to three dates and one XML namespace. That is not a uniqueness failure. It is the evidence needed to distinguish a stable identity from the revisions that change inside it.
Story
LACNIC Ratified the Sub-Assignment Rule. An Operating Log Still Needs Its Own Receipt.
LACNIC records LAC-2025-5 as ratified on 24 March 2026. Its final text calls for a WHOIS link and a public start-and-end movement log for qualifying IPv4 sub-assignments. Those are consequential commitments, but a ratification history is not itself a record of an individual…
Story
LACNIC and the economics of rough consensus
Consensus is not the absence of conflict. In a regional Internet registry, it is the work of turning conflict about scarce, shared infrastructure into rules that operators can recognize as legitimate.
Story
ARIN-2025-1 Has Two Official Status Labels. Neither Is Adoption.
One ARIN page records a 25 August Recommended Draft action for ARIN-2025-1. Another places it in the Recommended Draft list while its own status cell says Draft Policy. That public difference is a reason to preserve the record, not a licence to guess which label wins.
ICANN
ICANN’s .TEXAS Consent Gate Is Exact. Texas’s Letter Adds “Any Derivative”
Six words enlarge a clear objection into an undefined perimeter. Texas told ICANN that it opposed `.texas` “and any derivative thereof.” The 2026 Applicant Guidebook gives the state a consequential voice over the exact ISO 3166-2 match, but it also says strings that include…
ICANN
ICANN Logged a Javanese LGR Correction—The Final XML Is Still Pending
One character name separates the rule ICANN put out for comment from the rule its Javanese contributor says was intended. The April draft lets U+A9B4 follow U+A9BA or U+A9BC; the correction substitutes U+A9BB for U+A9BC. ICANN’s 24 August summary records the change and promises…
Story
ARIN’s Caribbean IPv6 Ranking Needs a Source-Coverage Receipt
The new Caribbean table is useful precisely because it avoids pretending to be a verdict on every network. Its next improvement is equally modest: show which available measurement sources made each jurisdictional average.
Story
APNIC’s Orbit Email Queue Was Delayed for 32 Hours. Its Release Needs a Receipt.
APNIC has recorded the service window and the stuck email processor. That is a useful notice. It is not yet a public account of the transition from a delayed mailing-list queue to a reconciled delivery record.
ICANN
ICANN Changed ‘Five-Year’ to ‘Periodic’—the Audit Clock Still Runs
One word disappeared from ICANN’s Board Risk Committee charter, but the obligation behind it did not necessarily disappear. The adopted text now promises external assessment “periodically” under professional standards. Those standards still contain a five-year outer limit. The…
ICANN
ICANN’s Name Collision Assessment Is Not a Delegation Decision. What Does a High-Risk String Need to Prove Next?
An ICANN name-collision assessment is a risk-management step in the 2026 New gTLD Program, not a confirmation that a proposed label will—or will not—reach the DNS. Its practical importance is in the next gate: a string identified as high risk can require a mitigation plan that…
ICANN
ICANN Names a Safeguard Assessment Provider. When Does String Review Become a Registry Agreement Obligation?
ICANN has appointed Mirror Group LLC for 2026 Round Safeguard Assessments. The important boundary is between a string-risk assessment and a safeguard that becomes part of a Registry Agreement.
Story
LACNIC and the economics of transition architecture beyond RIRs
A transition test built around functions, records and authority—not around the fantasy that scarce network resources can govern themselves.
Story
APNIC’s Five-Year Audit Rule Needs a Public Exception Record
The interesting sentence on APNIC’s transparency page is not the comforting one about a financial audit. It is the operational one: the audit firm is rotated at least every five years. That is a rule a reader can hold in mind. The December 2025 Executive Council minutes then…
Story
RIPE’s RPKI Key Plan Is Not Yet a ROA Scope Receipt
RIPE NCC’s plan to move RPKI API keys toward OpenID Connect is a statement about a future access mechanism. It is not yet a public way to reconstruct which resource authority and which state-changing action stood behind an individual ROA change.
Story
AFRINIC’s DBWG Shows 46 Open Items. A Count Is Not a State Path
Forty-six is a number that asks to be over-read. Put it next to the word Open and it can be made to sound like a verdict on an institution, a team or a service. AFRINIC’s public Database Working Group overview does not warrant that verdict. On the frozen 31 August 2026 capture…
Story
LACNIC’s Bogon Guide Has Three Different Data Clocks.
A BGP filter can reject a route without saying why that route was rejected. Treating every rejected route as one security statistic may be convenient for capacity reporting, but it is too coarse to explain what the underlying evidence meant at the moment of the decision.
ICANN
ICANN’s Ombuds Workplan Is Public. Its Board Evaluation Map Is Not
ICANN has published what its Ombuds Office plans to do in FY27 and the six kinds of performance evidence it intends to track. The Board has also approved a separate set of specific objectives against which it will evaluate the Ombuds. What the public record does not provide is…