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
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…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
Story
AFRINIC-38 Has a Named Safety Concern. A Hybrid Format Is Not a Risk Assessment.
A public message from an experienced Malawian operator does not prove that Cape Town is unsafe. It does something more precise: it puts a concrete delegate concern into AFRINIC-38’s record. AFRINIC’s own meeting guide already treats security as a location-selection input. The…
Story
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
Story
RIPE NCC’s Four Stale IPv6 Glue Records Are Now Three. Root Repair Was Never a Batch.
One of four old IPv6 glue mappings identified after RIPE NCC’s AuthDNS renumbering has aligned with the nameserver’s current address. The other three have not. That split result reveals the real unit of root-zone maintenance: one delegation, one authorised decision and one…
Story
AFRINIC Calls 122 New Members a 4% Increase. The Baseline Is Missing.
AFRINIC’s statistics portal compresses five year-to-date counts into five whole-number growth labels. The figures look self-explanatory until one asks the ordinary questions behind any percentage: compared with what, at what time, under which inclusion rules, and rounded how? The…
Story
LACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million Updates
Two sums on LACNIC’s noisy-BGP study close perfectly. A third opens a 1.37-billion-count question. That does not make the research wrong; “messages” and “updates” may describe different stages. It does make the missing bridge between raw RIS files and the published tables the…
Story
LACNIC Signs 150 Reverse-DNS Files. The Batch Has No Manifest.
LACNIC’s public directory gives every reverse-DNS data file its own signature and checksum. What it does not give a whole-directory consumer is one signed statement saying which 150 filenames belong to the same completed publication.
Story
ARIN Waited for a Geofeed Standard. Its RDAP Help Still Does Not Claim It.
Two years ago ARIN tied a community request to a visible trigger: once the common RDAP geofeed standard was accepted, three named product surfaces would change. The standard is now RFC 9877. The useful question is no longer whether the IETF will finish the vocabulary, but how an…
Story
BCAP’s Prize Entry Preceded Training. Its Outcome Receipt Has Not.
The WSIS Prize submission window closed two days before BCAP’s published professional-development start window opened. The project won in July and is still listed as ongoing through 2027. The award may be sound; the public record still needs to say which finished phase and which…
Story
AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.
AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s…