Primary Domain
Internet Infrastructure Institution
Within the Primary Domain facet, Internet Infrastructure Institution intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Story
APNIC’s Honeynet Saw 2,621 IPs Leave an SSH Key Behind
During one week, 2,621 source IPs ran the same command after logging in to APNIC’s honeynet. It wiped the existing `.ssh` directory and installed a key that could keep working after the password was gone.
Leaders
Kevin Blumberg Brought an 84-Meeting Receipt to ARIN’s IPv6 Task Force
One enterprise took three years and 84 meetings. At ARIN 58, Blumberg asked who would pay for the next conversion campaign.
Leaders
Mike Burns Helped Write ARIN’s One-Year Lock. Now He Wants the Key Thrown Away.
At ARIN 58, the man who carried a twelve-month IPv4 transfer wait into the rulebook asked why the wait was still there.
Story
AFRINIC’s Policy Draft Has More Clocks Than a Station and No Wall Chart
Version 4 of AFRINIC’s PDP proposal puts deadlines on impact analysis, list discussion, chair decisions and appeals. The hard part is making those clocks run in one order.
Leaders
Lily Botsyoe Brought a /48 Fix. One Verb Took the Microphone.
ARIN’s proposed IPv6 rule sorts organizations by site count. At ARIN 58, the room wanted to know whether the rule also chooses the size on an applicant’s behalf.
Leaders
Leif Sawyer Renamed ARIN’s ISP Door. The Signpost Faces the Other Way.
The policy manual is moving its rules from ISP to LIR. At ARIN 58, a reader asked where the old word would send them. The answer exposed a one-way glossary.
Leaders
Alison Wood Found the Catch in a Space Registry: Someone Has to Build It
ARIN 58 could picture an address book for the Moon. Wood brought the less cinematic question: who would run it, and at what cost?
Leaders
E. Marie Brierley Put IPv6’s “Not Property” Sentence on the Chopping Block
A tiny deletion at ARIN 58 drew a much larger question: what, exactly, does a holder take home from the registry?
Leaders
Matthew Wilder Tried to Simplify IPv6. The Room Found Homework.
ARIN’s proposed escape from address-allocation formulas asked for a network plan instead. At ARIN 58, the room wanted to know how small a network could be before that plan became absurd.
Leaders
Kevin Blumberg Found a Proxy in ARIN’s “Simultaneous Use” Escape Hatch
At ARIN 58, one word meant to protect Anycast drew a warning from the microphone: a regional rule can become surprisingly global when its exception has no edges.
Leaders
Clara Wade Got the IPv6 Proposal Down to Six Pages. The Spaghetti Survived.
She removed a definition, trimmed a rule and made room for readers. The harder part was getting a community to agree on what the shorter draft would actually do.
Leaders
Matthias Wichtlhuber Sent the IPv4 Bill to Future Engineers
A smaller first address block could keep new internet exchanges coming. Growing out of it would mean asking every connected network to help move house.
Leaders
Edwin Verheul’s 127 Addresses Had a Routing Problem
The paperwork could prove an experiment needed addresses. The internet still needed to see them. A Dutch network engineer took that mismatch to RIPE.
Leaders
Hernán Arcidiácono Put Two Ledgers at IPv4’s Exit
An IPv4 block can leave a special reserve or start serving another network. Arcidiácono helped write a public log for each journey.
Leaders
Tomás Lynch Put a Clock on Zombie Proposals
At LACNIC, a proposal could lose consensus and keep occupying a chair for years. Lynch gave that chair a twelve-month reservation.
Leaders
Hernán Moguilevsky Sent the ROA Pen Downstairs
The network using an assigned IPv4 block had to ask the address holder to sign its routing permission. Moguilevsky put the pen closer to the engineer doing the work.
Leaders
Fernando Frediani Put a Keyhole in the Word “Exclusive”
An address block can be assigned exclusively and still travel through another network. Frediani helped write the sentence that says who gets to turn the key.
Leaders
Evandro Varonil Cut the ISP Entrance Ticket to 256 Addresses
An aspiring network operator used to need a 1,024-address first ticket in LACNIC's region. Evandro Varonil asked why a young ISP had to buy a four-seat table when it needed one chair.
Leaders
Edmundo Cázarez-López Put 131,072 IPv4 Addresses Behind Glass
The network can run out of addresses while a new critical facility still needs them. Cázarez-López wrote a special reserve for that awkward day, complete with a size limit, a return rule and a sharp penalty for changing its purpose.
Leaders
Nicolás Antoniello Asked Who Could Order a Router Around
An IPv6 dispute proposal told IPv4-only networks to upgrade to dual stack. Antoniello, an engineer and former LACNIC policy-forum moderator, challenged the verb. The next draft turned an order into advice.