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
ARIN’s 75% Gate Depends on a Plan That Can Change
Sixty assigned prefix units are 75% of a plan containing 80 units. The same sixty are only 60% of a revised plan containing 100. No address has moved, yet the qualification result has. Draft Policy `ARIN-2026-2` makes that possible in principle because its proposed…
Story
APNIC’s First IPv6 PI Request Has No Previous Assignment
APNIC’s `prop-175-v001` offers to remove a peculiar round trip: issue a `/48`, wait for deployment, invite the applicant back, receive much the same network plan and assess the larger need a second time. Reusing the later-stage test is economical. It is also a change of state…
Story
Two Numbers on One Proposal: APNIC Must Correct Identity Without Rewriting History
`prop-174: Align implementation of Prop-125 in APNIC Policy (APNIC-127)` `prop-173: Align implementation of Prop-125 in APNIC Policy (APNIC-127)`
Story
One Portal, Four Unfinished Clocks
MyAFRINIC v2 has become more than a software project: AFRINIC's own records place four materially different policy paths behind the same portal milestone, making it necessary to prove each implementation separately rather than letting one launch announcement stand for all four.
Story
The Prefix Must Keep Its History: AFRINIC’s Proposed Pool Decision
Under `AFPUB-2026-IPv4-003-DRAFT01`, one recovered IPv4 block would first enter the temporary `Recovered Pool`. AFRINIC staff would trace its original source-pool category, return it there, classify a partial block proportionally, or send an uncertain origin to the…
Story
The Commitment Must Keep Its Name: RIPE NCC’s Missing Annual Ledger
RIPE-862 offers a precise starting chain: **Internet Resilience, Scalability and Routing Security**; the service-level objective **Security**; and the key metric **Internet Number Resources covered by ROAs and ASPA**. The next links—a costed 2027 Activity Plan and Budget…
Story
Between Listening and the Map: LACNIC’s Missing Input Trace
LACNIC’s public account names a collective planning process and a route from listening to SWOT and a final strategic map. What the checked documents do not expose is the privacy-safe join that would let a reviewer follow one issue from source class and channel through synthesis…
ICANN
The Breach Notice Stayed Itself: Employ Media, ICANN and the .JOBS Settlement
The contract did not require Employ Media to win before the threatened termination stopped. It required the registry operator to file arbitration and request a stay at the same time. On 3 May 2011, that procedural act kept `.JOBS` in place while ICANN and its operator argued over…
Story
The Seller’s Last Login: Why a LACNIC Deal Can Close Before Its Addresses Move
A buyer can acquire the shares, the routers and the customer contracts at midnight and still wake up without a completed registry handover. In a LACNIC transaction, the costly interval is the registry gap between legal control of the company and verified control of the number…
Story
APNIC's corporate-group rule turns affiliation into an electoral boundary
Before an APNIC nominee reaches the ballot, an organizational chart may already decide whether that candidacy counts as an independent choice or as a second seat for one corporate interest.
Story
AFRINIC's quarantine-floor objection crossed the Last Call boundary
A predictable Last Call cutoff and operational flexibility can both protect registry continuity. But AFRINIC's public record leaves a narrower control question unresolved: who owns a late objection when proposed discretion can shorten recovered IPv4 quarantine without a binding…
Story
A Valid Abuse Mailbox Is Not Enough. APNIC Wants a Working Handoff
A mailbox can answer a validation message and still fail the incident report that matters. APNIC’s prop-171 would make the upstream holder responsible for a working path to the downstream party able to act, but the proposal has not yet said how that path will be proved.
ICANN
When a Registration-Data Request Becomes Urgent—and What the New Clock Still Does Not Authorize
ICANN’s new urgent-request timetable can make a registrar answer faster. It cannot turn urgency into an automatic right to private data. The policy times acknowledgement and decision; authentication, necessity, legal basis and the merits of disclosure remain separate questions.
Story
APNIC’s SIG rulebook is turning bottom-up governance into a due-process test
A rule written for quiet mailing lists now sits at the centre of a larger question: whether APNIC’s community institutions can renew leadership and close inactive forums without weakening the procedural legitimacy on which bottom-up governance depends.
Leaders
Aaron Wendel and What Two Failed ARIN Proposals Reveal About Operator Power
Fourteen years apart, two public tallies put Aaron Wendel on the losing side of consequential debates about Internet number resources. The defeats are more revealing than a conventional success story: they show how practical operating knowledge enters policy, how commercial…
Story
LACNIC Turns IPv4 Value Into a Chain of Proof
An IPv4 block may attract a price, but a board cannot rely on that value until authority, eligibility and the registry change can survive diligence.
ICANN
The 90-Day Emergency Policy That Kept Domain Registration Data Moving
Eight days before the GDPR became applicable, ICANN used a temporary contractual power to keep one registration-data regime from fragmenting into hundreds of private answers. The power was immediate, but deliberately self-expiring: permanent policy had to come from somewhere…
Story
At LACNIC, the Most Valuable IPv4 Option Is Waiting
At LACNIC, the Most Valuable IPv4 Option Is Waiting 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's 2026 by-law vote bundled five constitutional choices into one weighted resolution
APNIC members approved Resolution 1 by a large weighted majority. The result settles whether the package passed; it does not reveal whether members separately endorsed longer Executive Council terms, term limits, an express Election Chair, revised Director General wording and the…
ICANN
When a DNS-Abuse Report Becomes Actionable—and What the Contract Still Does Not Order
The decisive step in ICANN's DNS-abuse regime is not the arrival of an allegation. It is the moment when available evidence supports a reasonable finding, after which a registrar or registry must act promptly—but still choose a remedy that fits its role, the harm and the risk to…