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
Sander Steffann Asked for a Complaint Counter. The Room Went Quiet.
A registry can count addresses down to the last digit. In 2013, Steffann wanted it to count the complaints about those addresses, too.
Leaders
Paul Wilson Asked DNS to Stop Bothering the Root About Ghost Names
APNIC had helped install at least 29 root-server instances across 21 economies. Wilson’s next question was sharper: what if resolvers learned when an answer was already “no”?
Leaders
Mark Kosters Moved ARIN’s Front Door After the Power Failed
A registry can debate resilience for years. A failed office UPS has a shorter speaking slot. In 2014, Kosters’s engineering team moved ARIN’s critical customer-facing systems from Chantilly to Ashburn.
Leaders
Carlos Martínez Kept a Key for 15 Years. Then He Left the Chair.
At the DNS root, trust arrives with a script, a witness and someone willing to give up the seat.
Leaders
Alain Aina Built the Registry. Then He Helped People Fill in the Form.
The distance from a rulebook to a working research network can be one stubborn application.
Leaders
Andrew Alston Brought a /13 to a Soft Landing Fight. He Left Without His Draft.
A plan for Africa's remaining IPv4 became a test of who could restart a policy argument.
Leaders
Preston Louis Ursini Knocked Twice. ARIN Sent Him to Two Different Desks.
One proposal asked who may hold numbers; the next asked how a new network requests them. The answers mapped the boundary between policy and service design.
Leaders
Lily Botsyoe Found ARIN’s Front Door. Then She Asked Who Was Still Outside.
A fellowship took her from the audience to the Advisory Council. Her next question was why a good policy idea still needed a veteran to get through the email thread.
Leaders
Alicia Trotman Offered ARIN Seven Extra Days. The Clock Won.
The proposal tidied a tired registry rule and gave providers two weeks to publish reassignment records. The additional week became the argument that swallowed the cleanup.
Leaders
Gerry George Had a Cure for ARIN’s IPv4 Queue. The Queue Fought Back.
Cut each newcomer’s slice of scarce IPv4 space and the line should move faster. George’s proposal reached the harder question: who gets to keep the place they already hold?
Leaders
Brian Jones Counted Three ASNs. The Room Asked for Three Organizations.
An Internet exchange definition seemed to need a number and a switch. At ARIN 54, Jones found that neither was quite so simple—and moved to abandon the draft the next day.
Leaders
Alison Wood Closed ARIN’s Community Network VIP Lane. The Regular Lane Was Faster.
A special IPv6 route meant to help small community networks acquired more paperwork than the ordinary one. Wood brought the obsolete detour to the policy room, then kept the audience entertained while it voted.
Leaders
Kaitlyn Pellak’s Answer to an IPv4 Objection: Write Your Own Rule
An address broker turned ARIN policy shepherd tells critics of a regional IPv4 restriction to bring a counterproposal. The exchange exposes who has to do the work when practice gets promoted into policy.
Leaders
William Herrin Brought a Logarithm to ARIN. The Room Wanted an Eraser.
The IPv6 allocation formula had the wrong math. Herrin offered a correction. At ARIN 57, the sharper question became why a formula nobody used still occupied the policy manual.
Story
RIPE NCC’s sanctions queue has 39 alerts waiting to be investigated
The latest quarterly report counts 2,339 alerts across several different states. The sharpest change is a line that was empty in July: 39 cases are now marked “not yet started”.
Story
ARIN’s Election Is a 675-Member Roll Call. Blank Ballots Count.
A ballot is doing membership work this year. For leaders, the practical question is whether the person authorized to submit it has an organizational decision to carry out.
Leaders
John Curran Had the RPKI Switch. He Left the Policy Switch to the Room.
An operator asked ARIN to make routing security compulsory. Curran, the registry’s CEO, answered with a line between running a service and writing a rule for everyone who uses it.
Leaders
Bill Manning Refused to Bury IPv4 With the Last Scoop of Rice
At an APNIC meeting in 2007, the room reached for kitchen metaphors to explain an emptying address pool. Manning asked them to check which cupboard was actually empty.
Leaders
Mark Elkins Had Four Addresses to Use. AFRINIC's Rule Wanted a Full Network.
An anycast service can run on a handful of addresses and still need a prefix that the world can route. Elkins brought that awkward arithmetic into AFRINIC's policy room.
Leaders
Bill Darte Gave a Two-Provider Network One /24. The Host Count Had to Move Aside.
In ARIN's 2001 policy fight, a small customer could need two upstream connections long before it could fill a spreadsheet with hosts. Bill Darte carried that mismatch to a vote.