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
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation 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…
CASE FILE
Cancel the Second Checklist
Closing a redundant register should end a redundant obligation. RFC 9751 offers a precise example of administrative subtraction—and a test for organisations whose paperwork can outlive the procedure it describes.
Story
APNIC's ASPA Lists Authorized Providers, Not Observed Transit
APNIC's ASPA Lists Authorized Providers, Not Observed Transit 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…
Story
APNIC Adopted a Foundation Liaison. The Public Record Stops Before the Protocol
APNIC has done the difficult part that institutions often avoid: it identified an old role with no settled scope, named the governance risks around it, and formally adopted a replacement. The next part was deliberately separated. Observer attendance, confidentiality and…
Story
APNIC Put 23 September and 17 August in One Payment Notice
A service notice should let a Member decide when to act. APNIC’s current online-payment notice instead presents one four-hour window in its identity and timetable, then names a different day in the description. The responsible conclusion is not to choose between them. It is to…
Leaders
Nurani Nimpuno and the Accountability Layer Behind Number Governance
Internet number governance is often described through institutions and acronyms. Nurani Nimpuno’s public record reveals a more useful operating question: how can a community preserve technical discretion while making delegated authority reviewable?
Story
LACNIC Whois created Dates the Registry Record, Not the Network's Launch
A timestamp precise to the second can look like a birth certificate. In LACNIC registration data, however, `created` dates the record for an address block. It does not reveal when the holder was founded, when engineers switched on a network, when the addresses were first used, or…
Story
AFRINIC’s 5% Early-Payment Discount Runs on Two Invoice Clocks
AFRINIC's renewal calendar begins with an invoice released in November and rewards payment received by the end of December. Its accompanying prose sets the reward against a different entity: the date of the invoice. Those statements can belong to a perfectly coherent billing…
Story
The final RIR governance draft needs an implementation register
The 1 September 2026 FINAL DRAFT strengthens oversight, but Section 1.3 leaves the operational bridge to future Implementation Procedures. A public register could show what has been adopted, what remains procedural work and what resource holders can actually verify.
Story
AFRINIC Whois org-type Classifies a Registry Relationship, Not Legal Corporate Form
AFRINIC’s `org-type` field looks deceptively familiar: a short label attached to an organisation record. Its proper use is narrower. It helps describe how that record sits inside the registry’s resource and membership system; it does not answer the legal, ownership or operational…
Story
The New RIR Draft Has Two Review Limits—and No Public Counter
Three requests can cite the same duty, concern the same registry and arrive in the same audit cycle. Under the recommended RIR Governance Document, whether the third may proceed depends on two clocks and on who counts as the same initiator. The draft supplies the limits. It does…
Leaders
Kanchana Kanchanasut and the Infrastructure Hidden Inside a First Connection
The celebrated moment in Kanchana Kanchanasut’s career is an early connection: an email link from the Asian Institute of Technology to colleagues outside Thailand. The more durable story is what had to come after that experiment—addressing, operating institutions, training and a…
Story
RIPE Database mnt-ref Authorises an Organisation Reference, Not Corporate Control
An accepted `org:` link in the RIPE Database has passed a meaningful authorisation test. That makes it evidence of an approved database reference—not a shortcut to proving ownership, group membership or control of the network behind the record.
Story
AFRINIC’s CEO handover needs a public transition ledger
AFRINIC announced Mike Silber as CEO Designate on 24 August 2026. Because he is due to assume office on 1 January 2027, the interval should be documented as a governed transition rather than treated as an already completed change of leadership.
Story
AFRINIC’s AS-SET restoration exception needs a decision receipt
A narrow continuity exception could preserve a deleted flat-name entity—but without a bounded evidentiary record, it may reopen the legacy namespace risk the proposal leaves in place.
Story
APNIC’s NIR RDAP Redirect Finds a More-Specific Record, Not a Network Operator
A redirect from APNIC to an NIR-specific RDAP host is an evidence trail about where registration data is served. It can lead to a narrower record without proving who currently routes, owns or operates the network.
Story
LACNIC Made Merger Transfer Fees Equal. It Did Not Make the Payment Rules Equal
A price list can make two transactions look alike long before their obligations are alike. LACNIC has put merger, acquisition and name-change transfers on the same published fee bands as ordinary IPv4 transfers and has attached both to an annual inflation clock. Yet the public…
Story
AFRINIC’s IPv4 waiver needs an evidence standard
AFPUB-2026-IPv4-002-DRAFT02 keeps the 90% utilisation rule but opens a difficult decision boundary: when is use below that threshold an unavoidable technical constraint rather than ordinary operational convenience?
Story
RIPE’s IPv6 PI Draft Makes Membership a Compliance Event
A router, a customer appliance and a `/56` can remain exactly where they were. Under RIPE’s current IPv6 PI draft, the moment the holder’s LIR account becomes active may nevertheless change whether that arrangement complies. A policy transition this quiet needs its own receipt.
Story
ARIN’s Whois Retirement Proposal Is a Protocol Transition, Not the End of Directory Data
Three dates in ARIN’s latest consultation can look like shutdown deadlines. They are not. The registry is asking how to retire three older access protocols in favour of RDAP, with separate dependencies and earliest dates for each path. The proposal changes how registration data…