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
A Contact Test Is Not an Abuse Trial: AFRINIC Draft 3 and the Boundary It Exposed
When AFRINIC published the third draft of its Abuse Contact Policy Update in June 2019, it made a distinction with consequences far beyond mailbox administration: proving that an operator can be reached is not the same thing as deciding whether that operator handled an abuse…
Story
Draft 7 offered six months, but did not clearly offer a cure
On 6 April 2019, AFRINIC published Version 7.0 of its Internet Number Resources Review proposal, AFPUB-2016-GEN-001-DRAFT07. Its one stated change from Draft 6 sounded protective: an organisation would have at least six months, and perhaps longer, before resources were recovered.…
Story
The ledger behind the call: what AFRINIC needed to show for Resource Transfer Policy Draft 4
On 5 October 2020, a fourth version of AFRINIC’s Resource Transfer Policy became the text that mattered. The public meeting in September had discussed the policy project, but it could not have approved words that had not yet been submitted. Once AFPUB-2019-V4-003-DRAFT04 arrived…
Story
The Longer Clock and the Shorter Fuse: AFRINIC’s Draft 2 Abuse-Contact Paradox
AFRINIC’s second abuse-contact draft relaxed the timetable for proving that a mailbox worked, yet sharpened what could happen when the proof failed. The proposal’s real significance lies in that mismatch: a modest record-accuracy test was redesigned as a possible gateway to loss…
Story
Four Repairs, Four Gates: The Private Authority Map Inside AFRINIC’s PDP Bis Draft 4
On 29 October 2018, AFRINIC published a proposed rulebook in which PDWG chairs would have up to two weeks to pronounce on consensus, yet their decision still sat inside a longer chain: a Board-appointed committee could review process, the Board could remand a proposal on…
Story
The Million-Address Switch: What SL-Update Draft 1 Actually Changed
On 28 October 2018, three authors published a proposal that would rewrite a single paragraph in AFRINIC’s Soft Landing policy. The change was compact, but the reserve behind it was not: an unused /12, containing 1,048,576 IPv4 addresses. SL-Update Draft 1 proposed taking the…
Story
The record outside the contract: AFRINIC’s first legacy-transfer draft
AFRINIC said it maintained inherited Internet number records for organisations with which it had no ordinary contract. That arrangement could persist while an address block stayed put. A proposed transfer made the anomaly urgent: the registry needed reliable evidence of who could…
Story
A routing identity without a second upstream: how Draft 1 challenged AFRINIC’s multihoming proxy
A routing identity without a second upstream: how Draft 1 challenged AFRINIC’s multihoming proxy intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
The reciprocal bridge AFRINIC drafted before it had a transfer path
A 2018 proposal tried to solve a deceptively practical problem: how two regional registries could recognise the same cross-border resource transfer without mistaking their shared recordkeeping for ownership of the resource. Its best provisions made the ledger follow reality; its…
Story
What the Simple PDP Update Took Away—and Where Its Discretion Went
AFRINIC’s Simple PDP Update Draft 1 approached process reform with a red pen: shorten notices, move the moment of decision, narrow the objections that counted at Last Call, and make mailing-list participation less subordinate to a meeting room. That subtraction offered a credible…
Story
The resolution with two numbers: what AFRINIC’s IPv6 PI ratification did — and did not — put into effect
AFRINIC’s August 2018 adoption of an IPv6 provider-independent addressing update removed an obsolete eligibility barrier and added a useful correction route, but the organisation’s own records disagree over the resolution number and show that implementation continued after the…
Story
Two words, two directions: AFRINIC’s IPv6 sub-assignment redline
On 22 August 2018, the words “semi-permanent connectivity” appeared in an AFRINIC proposal about IPv6 provider-independent assignments. They seemed to tighten a familiar prohibition. Yet the same revision removed a numerical limit, discarded a peculiar restriction on…
Europe and Middle East Cloud Services Trends
Four AS Identities Around Internetmanufaktur Karlsruhe
Public records around Internetmanufaktur Karlsruhe become useful when company chronology, number-resource ledgers, routing observations, exchange metadata and bounded measurements remain separate evidence layers.
Story
AFRINIC called an interim takedown order a legal confirmation. The order says less
The Mauritius Supreme Court temporarily barred Cloud Innovation from falsely attributing judicial approval to AFRINIC-address leasing and ordered related material removed. AFRINIC then presented that ex parte order as confirmation of a wider legal position. The published ruling…
Story
The five-day mailbox: when AFRINIC Draft 1 turned contactability into compliance
Two messages, one code and five business days separated a useful registry check from a proposed breach finding. AFRINIC’s first Abuse Contact Policy Update draft began with the practical need for a reachable network-abuse desk, then crossed into prescribing how that desk must…
Story
The IPv6 door that opened without an IPv4 past
An African enterprise planning a second upstream faces a deceptively simple choice: accept provider-assigned IPv6 and prepare to renumber if the commercial relationship changes, or seek a provider-independent prefix that can preserve its public network identity across both paths.…
Story
AFRINIC's 2017 accounts: approval before completion
Resolution 201803.403 fixed an important responsibility: AFRINIC's Board approved the 2017 financial statements before the auditors signed their report, then authorised the chief executive and chair to sign both the accounts and a representation letter. That sequence was orderly…
Story
The seven-year error in AFRINIC’s IPv6 manual
Seven years after newer Internet guidance had displaced an old formula for sizing IPv6 assignments, AFRINIC’s working manual still directed members and staff towards the obsolete text. The proposal that repaired the mistake looked like housekeeping. In fact, it exposed a serious…
Story
The narrow door through AFRINIC’s secrecy wall
Resolution 201803.402 did something modest but indispensable: it allowed directors and former directors to give an independent investigation committee confidential information that was reasonably necessary for its work. That permission stopped AFRINIC’s own secrecy rule from…
Story
The Seat That Members Refused to Fill
Resolution 201803.401 solved a real nomination conflict by building a one-seat route back to AFRINIC’s members, but its unwritten bylaw foundation and the Board’s proximity to the candidate gate made refusal—not institutional confidence—the decisive test of legitimacy.