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.
Leaders
Yasu Taniwaki’s Question: Who Can Seek a Remedy from an RIR?
At Japan IGF 2024, Taniwaki asked whether the RIR system had an appeal or dispute-resolution process. A later draft names more people who may enforce rights against an RIR, but the text is still awaiting approval and implementation.
Story
AFRINIC’s RPD Reply Drew a Boundary. The Scope Question Remains.
AFRINIC’s third Bylaws consultation closed on 30 August. A public exchange on the RPD list two weeks later separated formal article review from policy discussion, but did not spell out where entities should raise a bylaw’s effects on the policy process.
Story
AFRINIC Reports 62 Event Attendances, but No Cost by Event
AFRINIC’s unaudited first-half report presents two different ledgers: travel spending by department and governance group, and attendance counts by event. One assigns USD 114,232 to Board travel; the other records 15 Board attendance entries among 62 event appearances. Neither…
History
A Global Voice by Unanimity: The RIRs’ 2003 NRO Compact
Four regional registries created a way to act together without merging their operations. The 2003 NRO memorandum made shared representation depend on delegated authority and unanimous commitments; in 2004, a separate agreement placed the NRO inside ICANN’s address-policy process…
Story
RIPE’s first-ASN draft defers the route-policy record until use
RIPE’s first-ASN draft defers the route-policy record until use 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…
Story
AFRINIC’s Dashboard Draft Needs a Versioned Policy-to-Test Map
The 25 September revision treats automated checks as possible indicators and requires staff to verify what a test found. That boundary matters only if members and reviewers can trace each alert to the exact policy version, input record and test that produced it.
History
The Registry Could Draft a Filter; Operators Still Had to Apply It: RIPE, 1993–95
In 1993, RIPE proposed making routing policy legible to databases and tools. A tiny pilot could turn records into access lists; the records still did not show what a network had put into operation.
Story
The LACNIC Board ballot is set for November. Its English call says October.
LACNIC’s election index and dated timelines put the 2026 Board vote on 3–10 November. One English field in the detailed call instead says voting opens a month earlier; the Spanish call gives the November date.
Story
ARIN’s space-address draft still needs a global allocator
ARIN has a draft for allocating addresses to networks beyond Earth orbit, but the document leaves a prior question open: who would supply the address block, and who would be authorized to distribute it? The answer sits across IETF, IANA, the RIRs and ARIN’s own board, not in one…
History
The First .com Came Four Years Before the Web
The first .com entered the naming system in 1985, four years before Tim Berners-Lee’s first Web proposal. The dates mark separate layers: domain administration and hypertext.
Story
RIPE NCC’s service review has a route, not a budget veto
The RIPE NCC Services Working Group can examine existing services, new tools and the annual activity plan. Its charter leaves budgets and fee structures outside the group’s remit. A co-chair selection under way shows how the community chooses conveners for that review channel—and…
Story
APNIC’s review program may end before remediation does
APNIC’s Q3 timetable separates three events that can easily be collapsed into one: finishing data analysis, handing results to National Internet Registries for checking and remediation, and concluding the review program. The first two are targeted for the end of 2026; the program…
Story
ARIN Can Retire 6.4.1. It Still Has to Name the Rule That Replaces It
ARIN-2026-3 would remove the Number Resource Policy Manual’s “not property” subsection. Its rationale says the subject belongs in the Registration Services Agreement, but the proposal contains no replacement text, contract version map or transition. The difficult question is what…
History
One Registry, Three Desks: APNIC’s Distributed Operations, 1993–94
APNIC’s early regional service was built across national network centres. Contemporary records show its address, information and DNS work being divided among JPNIC, KRNIC and AUNIC while a wider group coordinated remotely.
Story
RIPE NCC’s new risk register starts with the whole organisation
A top-down view of high-impact risks changes where the discussion begins; the September Board minutes tie some treatments to the right budget.
Story
APNIC begins reviewing its own IPv4 data as NIR checks advance
APNIC’s Q3 update places its own registry analysis inside a review that is moving from initial data work toward checks with national registries. It gives a timetable, but no findings.
Leaders
Andrei Robachevsky and the RIPE Database Migration That Put Every User in Scope
On 14 May 2001, a RIPE Database user could no longer send RIPE-181 updates to the familiar `auto-dbm` address. RPSL was now required there; a separate `auto-181` path would translate legacy updates until 15 October. The change was not a single overnight conversion. It was a…
Story
APNIC makes no consensus call on an IP-abuse definition
Prop-172 would define technical abuse tied to Internet number resources, but APNIC 62 left it on the Policy SIG mailing list. The remaining question is who can assess a response when the resource holder and complainant disagree.
North America Institutional Trends
ARIN’s rewrite keeps IPv6 aggregation on top
ARIN’s proposed cleanup would give general number-resource principles one home while preserving a distinct IPv6 priority. The harder question is whether the draft’s own wording makes that hierarchy and its decision-maker clear enough to audit.
Story
RIPE NCC’s 2027 Budget Table Says €2,209 per LIR. Its Notice Says €2,056
The 2027 draft calculates €2,209 in expenses for each LIR, up 7% from the 2026 budget. RIPE NCC’s announcement repeats the €2,056 baseline instead.