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
Ray Plzak Froze Three IPv6 Fee Waivers. ARIN Gave Away Two Years, Kept the Old Bill.
ARIN set a new IPv6 price list in October 2004, then spent two board meetings deciding who would actually pay it. Ray Plzak stopped three separate waiver motions and returned with one broad exemption. The invoice already sent in 2004 survived.
Leaders
Nicolás Antoniello Wanted a Sixth Registry. IANA's IPv4 Drawer Was Empty.
Global networks crossed five registry regions with one address plan. Antoniello proposed a virtual desk to serve them. LACNIC's own impact analysis found that the desk needed five operators, a new system and an IPv4 pool IANA no longer had.
Leaders
Malcolm Hutty Put Fairness Back Into RIPE’s “No Need” IPv4 Fight
The form asking how many IPv4 addresses an applicant needed had outlived the free pool. Malcolm Hutty feared that tearing up the form under the banner “No Need” would also sound like tearing up the registry’s promise to distribute addresses fairly.
Leaders
Haitham El-Nakhal Asked for Two Last /8s. Five Regions Settled on One.
Africa's IPv4 claim had a number attached: two final blocks for every regional registry. Haitham El-Nakhal carried it into an international policy room. The number that survived was one.
Leaders
Bill Woodcock Asked Who Could Afford ARIN’s $500 Experiment
ARIN put a price on temporary address space in 2004. Woodcock saw the student researcher on the wrong side of the invoice. Four years later, a different researcher had trouble getting even a company to pay it.
Leaders
Erik Bais Put a 24-Month Clock on Acquired IPv4. The Merger Door Stayed Open.
RIPE's transfer rules once lived in four documents. Bais pulled them into one and made a newly acquired scarce resource wait before a policy transfer. A company could still be acquired again while the clock ran.
Leaders
Adiel Akplogan Could Sign the Big Contract. AfriNIC’s Board Held the Key.
AfriNIC needed a CEO who could do business while its new registry took shape. Its board gave Adiel Akplogan that authority in writing, then drew a money line around it. Five years later, the line and its wording had changed.
Story
RIPE’s First-ASN Review Starts 336 Days After It Ends, Says RIPE’s Own Calendar
The policy officer opened the review in October 2026. The public proposal index sends its start into October 2027 while keeping the November 2026 deadline. Anyone following that page gets a time machine instead of a timetable.
Leaders
APNIC Voted for Katsuyasu Toyama’s IPv6 IRR. April Came and Went.
The room endorsed an IPv6 routing registry in September 2004. It left the hard questions to a quiet mailing list. APNIC then aimed for April 2005, ran into software work, invited operators to a test service, and recorded implementation in May 2006. Toyama got the vote; a usable…
Leaders
Masasi Eto Found a Registry That Could Spell the Route but Could Not Agree on It
Two networks could file perfectly legible routing policies and still describe opposite versions of their exchange. Masasi Eto tested that gap in 2003. His finding put a number on the registry's awkward question: if its records disagree with each other, who will trust them enough…
Leaders
Bill Darte Offered ARIN a /22 Now and a /24 After the Evidence. Only the First Door Opened.
The 2002 room could not agree on smaller IPv4 blocks. Darte returned with a narrower first step and a route-table test for going further. ARIN adopted the first step; the test stayed outside the rule.
Leaders
Thomas Narten Let ISPs Pick the IPv6 Block. ARIN Kept a /56 Ruler.
A household could receive an IPv6 block chosen by its provider, while ARIN would still judge the provider's utilization against a standard /56 unit. Narten and Lea Roberts put those two decisions in different hands in 2005. The split survived the policy room.
Story
Two Providers Can Announce the Route. ARIN's Easy /24 Comes From One.
ARIN says a downstream customer's need to use more than one upstream can, by itself, justify a /24 IPv4 block from an ISP. The customer must identify every upstream and run a border routing protocol with the provider supplying the block. Yet the policy gives that shortcut for a…
Story
One University /21, Two RIR Transfer Clocks, Six Hours Apart
ARIN and APNIC both record St Mary’s 140.184.16.0/21 moving to a Salesforce-named recipient. Their public timestamps disagree by 6 hours, 5 minutes and 15 seconds.
Story
City of Ruston to Rightfiber: Three Resources Moved in One Second. The Cutover Has No Public Clock.
City of Ruston to Rightfiber: Three Resources Moved in One Second. The Cutover Has No Public Clock. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
APNIC Put a 2013 ASN, IPv4 /24 and IPv6 /48 in the Same Reserved Drawer
Three Australian resource records changed status together overnight. The registry kept them reserved, outside the available pool.
Story
ARIN Accepts a Customer as Free Text. Give It Control and the Contact Gate Closes.
An upstream provider can put a customer's name into a simple ARIN reassignment without linking it to a vetted organization or contact record. The provider keeps control. If the customer needs a detailed reassignment or reallocation with its own management capability, ARIN…
Story
RIPE Renewed Its Open Source Co-Chair to RIPE 99. The Roster Still Says RIPE 93.
Sasha Romijn was the only candidate and received support. RIPE NCC’s public working-group table has not caught up with its own result.
Story
LACNIC Logged a Transfer with No Address. The Blank Is 297 Days Old.
A university-to-DIGY transfer has names, date and no IPv4 range in LACNIC’s public file. The only such row in 1,922 has survived since January.
Story
ARIN Can Review Your Addresses Without Cause. The 24-Month Brake Has Other Entrances.
ARIN's current policy lets it examine how an organization uses any number resources in its database and ask for reasonable supporting documents. One route needs no stated cause, unless a full review has finished in the preceding twenty-four months. Three other routes remain: a…