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
K-root Says It Meets Every Expectation. The Evidence Is Uneven
RIPE NCC has answered the root-server community's operating expectations one by one. That makes K-root easier to question than a service hidden behind a general assurance of competence. Yet RIPE-859 also reveals a governance gap: a public metric, a control description and the…
Story
RIPE's NRTMv3 Stream Can Skip an Invalid Object. A Moving Serial Is Not a Completeness Receipt
RIPE Database release 1.124 made a small change with a large evidentiary consequence: the NRTMv3 server should skip invalid objects. Keeping a replication stream alive may be the right operational choice, but continuity alone can no longer answer the mirror operator's most…
Story
APNIC Prop-173 Would Put Copyright in Every Query. It Still Needs a Rights Ledger
An RDAP answer can carry a copyright notice in the same envelope as an address range, a registration date and a holder-supplied contact. That does not make every element the same kind of legal entity. APNIC’s prop-173 correctly identifies that ordinary directory queries lack the…
Story
LACNIC’s 70% Pass Mark Is Not a Candidacy Receipt
LACNIC’s Board-election rules contain a consequential distinction: a person can pass the mandatory competency assessment and still not become a validated candidate. The Electoral Commission receives the score and remote-proctoring incident evidence, but the public process does…
Story
ARIN Put the Reg-RWS Key in a Header. That Does Not Make It Uncapturable
ARIN now accepts a Reg-RWS API key in the `Authorization` header while continuing to accept the same credential in a URL query string. The new channel removes a dangerous source of routine propagation, but the public record still needs to distinguish a safer request shape, client…
ICANN
ICANN Can Group Two Strings Without Finding Them Similar. What Does the Middle String Control?
Consider three applications for new top-level domains. ICANN’s String Similarity Evaluation Panel finds string A visually confusable with string B. It also finds B visually confusable with C. But it does not find A and C confusable with each other. All three applications can…
ICANN
ICANN Completes String Similarity Before Priority Batches. What Does the All-Strings Rule Protect?
A late Priority Number does not place a proposed string outside the comparison universe. ICANN's 2026 Round rules require the similarity review to cover every applied-for string before evaluation batches are formed.
Story
AFRINIC’s IPv6 Condition Names Three Percentages but Not the Meter
The proposal’s benign ambition is understandable: turn passive IPv6 holdings into actual, gradual deployment while using traffic information operators may already collect. The unresolved question is whether the proposed percentages can be reproduced, checked and fairly reviewed.
Story
AFRINIC Extended Its Bylaws Consultation. Its Only Named Form Went Down Four Days Before the Deadline
A deadline is a promise about access, not merely a date printed on a page. AFRINIC gave contributors until 17 May to use a designated constitutional-comment form; on 13 May it announced that the form host was unavailable, leaving the public record without the timestamps and…
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…
History
The Route That Moved Backward at Every Relay
ONE received a forward-path that already contained its own name: `@ONE,@TWO:JOE@THREE`. It removed `@ONE`, then prepended to the reverse-path the name by which the next mail environment knew it. The route still waiting to be followed became one step shorter. The route available…
Story
The 27 August Redline: Reading APNIC’s prop-165 Through Its Assessment Delta
APNIC’s canonical `prop-165` record now points to `prop-165-v004`, published on 27 August 2026, while the Secretariat analysis displayed on that record is expressly introduced as applying to version 3. With the APNIC 62 Open Policy Meeting scheduled for 10 September 2026, the…
Story
RIPE-861 Recommends Off-List Nominations. The Candidate List Needs a Receipt
RIPE's new guide gives a quiet volunteer a private way to approach a continuing working-group chair. That can widen participation. It also moves the first step outside the public archive, making the later conversion from interest to a complete candidate list the part that needs…
ICANN
ICANN’s Prioritization Draw Sets the Queue. What Can a Low Number Actually Guarantee?
A physical ticket costing USD 100 will help determine when a 2026 new gTLD application is processed. The mechanism sounds almost ceremonial beside an application system built around technical evaluations, objections and contracts. Its effect is not ceremonial.
Story
LACNIC and the economics of legitimacy after scandal
A balance-sheet test for how a regional Internet registry could restore trust after a verified governance failure without risking continuity.
Story
LACNIC's FORT Can Validate ASPA. Its Router Feed Defaults to Version 0
LACNIC announced a validator that can carry ASPA data towards routers. The release also keeps that route behind a configuration value whose default is zero. That is not a contradiction or a defect. It is the difference between shipping a capability and establishing that the…
Story
A Date Is Not a Review Window: AFRINIC’s Missing Assessment-to-Agenda Record
AFRINIC’s staff impact assessment for `AFPUB-2026-GEN-002-DRAFT01` is dated 23 June 2026. AFRINIC-37 met on 24 June, with the Policy Compliance Dashboard scheduled for 15:15–16:05 local meeting time. The minutes preserve the PDWG Chair’s concern that providing an assessment only…
Story
AFRINIC Invited Members to Test MyAFRINIC v2. The Beta Needs a Defect-to-Release Ledger
AFRINIC used its AfPIF 2026 page to invite members into the next stage of MyAFRINIC v2: workflow interviews, user acceptance testing and a live beta. That is a sensible way to test a member portal against real registry work. It also creates an evidence duty. Every finding should…
Story
ARIN Calls Its Space Policy Joint. IETF Has Not Adopted the Address Model
ARIN-2026-1 says the proposal is joint with an IETF working group. The linked IETF record says the address model has no formal standing, and the working-group chairs found no clear consensus to adopt it as-is. Both statements can be faithfully recorded only if institutional…
Story
Where Member Notice Stops: RIPE-865 and the Burden of a Public Record
RIPE-865 preserves the general position that RIPE NCC members are informed when authorities seek their data or registry action, unless notice is expressly prohibited. Its eEvidence section creates a different notification state: confidentiality applies, and the RIPE NCC cannot…