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.
History
Elise Gerich and the Public Record Behind Private Routes
Routers could tell one network what another network could reach. They could not explain what the other network meant to announce, what it was prepared to accept, or whether the two intentions were compatible. Elise Gerich’s work around the Routing Arbiter belongs to the history…
Story
IRINN’s 13 Webinar Bars Sum to 3,567. The Same Slide Says 5,000+
IRINN’s APNIC 62 update offers an unusually useful test of capacity-building evidence: thirteen visible webinar counts reconcile exactly to 3,567, while a footer on the same page reports more than 5,000. Both may describe real activity, but the public record does not say whether…
Story
LACNIC's Election Recovery Defaults to ALL. One Email Search Reaches Vote, Nomination and Support Links
Convenience has a constitutional edge when the thing being recovered is not an account but a power. LACNIC’s newly published election code can use one email address to find three kinds of tokenised link. The missing record is not another log of clicks. It is a receipt showing why…
Story
AFRINIC’s Transfer Log Reaches 13 September. Its Last Event Is 18 June
AFRINIC’s cumulative transfer file carries a production time and coverage end from 13 September 2026, while its newest transfer event is dated 18 June. Both dates can be correct; the missing evidence is what advancing the first clock proves about the second.
Story
LACNIC's 12,609-Organisation Electoral Roll Has No Revision Clock
LACNIC has opened a month-long period for members to challenge its 2026 Board electoral roll. The roll is searchable and its totals reconcile, but the number on the page has no visible timestamp or version to tell a member which state they are challenging.
Story
ARIN's WhoWas Accepts an IPv6 Address. The History Still Needs a Capability Receipt
A request can be well formed, a report can have the right columns, and the archive behind both can still remain unproved. ARIN’s public record now makes all three propositions about IPv6 WhoWas look adjacent. What it does not provide is the small, dated receipt that would make…
Story
ARIN Approved Two Grants Below $50,000. The Exact Total Awaits the September Notice
ARIN’s Board has approved two 2026 Community Grants after ten applications, and has already disclosed that their combined value is below budget. The public record is clear enough to locate the uncommitted money, but not yet precise enough to count it.
Story
APNIC’s 53% Willingness-to-Pay Signal Has No Price Attached
APNIC found a majority willing to consider paying extra for premium support—but only inside a preselected group, and without naming the price or the service bought. That makes 53% a reason to ask the next question, not an answer to it.
Story
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
A Correct Registry Cannot Repair a Wrong ASN.1 Module
Two implementers can read official material, write conscientious code and still produce systems that refuse to speak to each other. That is what the authors of a new IETF draft say happened with RFC 6211: one implementation followed the entity identifier printed in the RFC…
Story
AFRINIC’s Draft Keeps the Community in the Fee Notice, Not the Fee Consultation
The same sixty days can protect two very different things. AFRINIC’s current Constitution gives Members and the community time to comment while a fee decision is still open. Its August draft keeps sixty days for the community after finalisation, but no longer names that community…
Story
RIPE’s NRTMv4 Source Gate Reads a Replica. Its Fallback Does Not Cover the Gate
A three-file code change gives RIPE NCC’s NRTMv4 service a sensible read path and leaves one unusually precise question behind: when a source is new, what proves the catalogue reached that path before the service begins treating it as authoritative?
IETF
VXLAN's Registry Opens 39 Bits While Its Wire Text Still Reserves 24
A protocol registry is a promise about future change. A packet diagram is a promise about what implementations do now. The latest VXLAN bis draft makes both promises about the same header, but they do not yet line up: its proposed IANA registry marks 39 unused bits as Unassigned…
Story
AFRINIC's 2026 Closure Data Spells Voluntary Two Ways
AFRINIC has done the useful thing by publishing reproducible statistics on closed memberships and returned number resources. But its current 2026 data place `VOLUNTARY` beside `VOLUNTART`, and the dashboard treats the two strings as different categories. That one-character split…
Story
LACNIC’s AI Client Resolves a Model, Then Chats Without a Resolution ID
LACNIC has published a cleaner way for Java applications to reach its PAI AI gateway. The new client says which model answered. What it cannot say, in its public typed contract, is whether that answer came from the exact model-resolution state the application inspected a moment…
Story
ARIN’s 2026 Candidate Q&A Is for the Board, Not the Advisory Council
ARIN members will elect trustees and policy advisers in the same October ballot. Yet the only live candidate-questioning event on the current official calendar is expressly for one of those two elected bodies.
Story
LACNIC Asked for a Technical-Committee Charter. Its First Committee Ran the Registry.
LACNIC’s Board has found a sensible reason to create a technical committee and an equally sensible reason to fear one. Directors need a place to understand technologies that may reshape the registry. They do not need a second operations room. The distinction sounds obvious until…
History
Jun Murai and the Address Space That Became a Trust
The number is oddly exact: 14,680,064 IPv4 addresses. They were neither a fresh registry allocation nor abandoned space waiting to be reclaimed. They were seven-eighths of an old Class A block, held through three decades of changing Internet institutions, and in 2020 Jun Murai…
Story
ARIN Can Attach a Ticket to an Org ID. That Does Not Make It the Organization’s Decision.
ARIN fixed a mundane but costly support problem: staff no longer need to begin every ambiguous question by asking which organization it concerns. The resulting Org ID selector gives a ticket context and a durable home. That is good service design. It also makes one distinction…
IETF
INTAREA Adopted a Registry Cleanup. IANA Has Not Applied It.
An Internet-Draft can acquire a working group without changing a single live registry. That is what happened on 11 September: INTAREA published its version of a proposal to close one legacy list, assign procedures to three others and remove a fifth. The institutional handoff is…