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 Put Two Rules on an 11 November Clock. One Names the Players; One Draws the Border.
The Advisory Council sent an ISP/LIR rewrite and an IPv4 geography rule into Last Call together. Anyone who wants a different boundary has fourteen days to say where it belongs.
Story
RIPE NCC Gave Attendee Lists 12 Months. Old Rosters Are Still on the Web.
The board drew a line between keeping a record and displaying it to everyone. Three past meeting sites still cross that line in an ordinary browser.
Story
ENUM's cleanup clock is 60 days. RIPE NCC does not start it alone.
The September decision turns a broad closure scare into a letter to one country at a time. A silent nameserver can raise the case; it cannot sign the withdrawal.
History
The Internet's New Media Types Took a Number and Waited Two Weeks
In 1994, naming a new kind of Internet content involved a public mailing list, a two-week wait and a trip to IANA. The form looked modest: type, subtype, parameters, encoding, known risks and a contact. Yet the queue solved a large coordination problem. A common name could follow…
Story
APNIC Wants an Open Contest for Host Cities. The 2028 Meeting Skips the Opening.
The registry’s directors backed a six-month invitation for future conference hosts. Its first test will use the new scoring method while keeping the invitation closed.
Story
RIPE Atlas Wants Your Spare Raspberry Pi. It Still Has to Find the Missing Networks.
RIPE NCC is exploring a flashable image that would turn a volunteer's own device into an Atlas hardware probe. The box is easier to find than the network vantage point that makes it useful.
Story
Chile Put 1,954 URLs on a Blocklist. Where Is the Clock to Take Them Off?
A five-day deadline tells network operators when to add a target. LACNIC's new blocking study asks for the other half of the job: a way to correct and retire it.
Story
ARIN’s Survey Gap Shrunk. Its Performance Score Fell Eight Points.
ARIN’s 2026 customer survey offers a tidy headline and a less tidy ledger: the gap between performance and expectations narrowed, while both scores fell. The distinction matters to members deciding what the registry should fix—and what its next fee should buy.
Story
APNIC’s Board Asked How to Lift Its Energy Investment Ban. The Gate Is Still Locked.
The registry expects investment income to matter more next year. Its directors have asked for the paperwork that would let them reconsider a sector they currently exclude.
Story
ARIN Has $12.5 Million Above Its Reserve Target. Its 2027 Fees Still Rise.
ARIN's treasurer called the registry's finances healthy at its October meeting. He had the numbers to make that case. The Board had also already voted to raise next year's registration-plan fees by 5%. The question for members is how quickly the registry should spend its cushion…
Story
ARIN's /44 Draft Says Will. Its Staff Says May.
An eight-site network can qualify for a /44 under ARIN's IPv6 draft. At ARIN 58, someone asked the question the draft leaves on the desk: can that network take less? The written examples say it **will receive** the larger block. The registry's senior staff said there is a choice.…
Story
ARIN Put a Border on Its IPv6 Bridge. The Border Is on the Wrong Noun.
ARIN staff already turn down requests to use a special IPv4 transition pool outside the region. A policy now in Last Call would put that practice in the manual. Its one added phrase limits where IPv6 is deployed, while staff say the rule is meant to limit where the IPv4 addresses…
Story
RIPE NCC Contacted the Holders. 51.7% of Legacy Ranges Still Await a Reply.
The registry says it has contacted all roughly 1,500 legacy holders. Its new range-level tally shows how much verification work remains before anonymous records go public in 2027.
Story
RIPE NCC Wants Two Independent Data Centres. The Switch Between Them Is the Story.
The registry plans to replace a shared network stretched across two nearby facilities with autonomous sites in Western Europe. Inside each site, systems would run active-active. Between sites, one would stand by. That last handoff will decide whether the rebuild delivers…
Story
RIPE NCC Wants Two Data Centres That Can Survive Each Other
The registry is replacing a stretched network between nearby facilities with independent sites. Its October design finally says how; the survival test comes later.
IETF
IANA Has Listed the New SFrame Ciphers. The RFC Is Still at the Printer.
A public standards table can move faster than the document that explains it. IANA's SFrame registry already displays three new cipher-suite numbers, five extra parameter columns and a row of “Y” recommendations. The defining draft is still in the RFC Editor queue. Engineers can…
Story
LACNIC Can Shut the Service Window. The Draft Wants the Address Block Too.
A legacy holder who misses LACNIC's December paperwork deadline faces the loss of registration services under a Board call already in force. A new policy proposal would put recovery of the number resource itself on the table. The distance between those acts is where the argument…
IETF
Same VPN Number. No Right to Import the Route.
Ten routers can share a VPN and still have different reasons to receive a particular route. A draft at the IETF proposes a tag that carries a Route Target's identifying numbers without carrying its power to distribute and import routes. The wire format changes only at the…
IETF
A Protocol Number Has an Owner for Its Next Edit. The Registry Should Say Who.
A code point can survive its author, its working group and several generations of software. Its entry in an IANA registry may need a new contact, reference or description years later. Someone has to approve that edit. A new IETF draft wants the answer written into more registry…
Story
LACNIC Reached 9.39% of Legacy Holders. They Cover 24.67% of the IPv4.
The registry’s contact campaign is reaching a large slice of address space through a small slice of organizations. The December deadline still runs for everyone else.