Topic
Consensus Capture
Within the Topic facet, Consensus Capture 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
The Flag Must Stop at the Gate: AFRINIC Draft 2 and Notice Without Punishment
An automated check sees an IPv6 assignment that is not publicly announced. That may look irregular, yet the member may be using the assignment legitimately inside its own network. On 16 November 2021, that example was offered in discussion of AFRINIC’s Policy Compliance Dashboard…
Story
When Consensus Cannot Supply Consent: AFRINIC Draft 2 and the Missing Authority to Disclose
A proposal to publish summaries of successful internet-number requests met an obstacle in AFRINIC’s own assessment: the registry had thousands of old files, no standard summaries, and no express permission from the members whose information would be repurposed. The resulting…
Story
AFRINIC Draft 2 and the Four Couplers That Would Not Meet
Four counterpart registries examined the same proposed transfer lane and found that it did not connect to the way they worked. The lesson of AFRINIC's second Resource Transfer Policy draft was not that management needed more freedom to wave a transaction through. It was that…
Story
The Two-Year Switch: When Registry Transparency Becomes a Second Data Demand
AFRINIC’s Publication of Information proposal began with a deceptively simple clock: evidence given privately to justify an accepted resource request would move towards publication two years later. The hard question was not whether registry decisions should be visible, but…
Story
The Empty Chair and the New Charter: AFRINIC’s Version 4 Legitimacy Test
On 23 August 2021, AFRINIC’s Board recorded that it had heard feedback about the rules for an internal appeal body, retired a charter that was only weeks old, and approved another before the next day’s search for volunteers. That sequence was responsive, but responsiveness and…
Story
The Appeals Stayed; AFRINIC Changed the Forum
In July 2021, with three policy appeals still unresolved, AFRINIC’s Board immediately withdrew both the charter and the members of its internal appeal forum and approved a replacement charter. The defensible purpose was to restore a correction mechanism that had stopped working.…
Story
The Board’s Narrow No: AFRINIC’s July 2021 Corporate-Law Stop
When `Board Prerogatives on the PDP` reached AFRINIC’s Board for ratification, the Board did not seize the policy process, rewrite the proposal or rule on anyone’s rights. It stopped the text at the company’s own approval gate. Resolution 202107.621 is therefore strongest as a…
Story
The Mailbox and the Case File: Drawing Draft 7’s Contactability Boundary
AFRINIC’s seventh abuse-contact proposal contained both a sensible directory rule and the seeds of a much larger institutional role. Its most important sentence placed the definition and escalation of abuse outside the registry’s remit. Its most consequential ambiguity was that…
Story
The Meaning of “End”: AFRINIC’s Draft 3 and the Discipline of Negative Routing Assertions
One sentence added to an AFRINIC policy proposal in April 2021 drew a vital line: reclaimed number resources should enter the registry’s AS0 coverage only after reclamation ends. That line can protect routing security, but only if “the end” is made into a state that outsiders can…
Story
The version gap inside AFRINIC’s transfer-policy appeal
AFRINIC’s 2020 transfer-policy dispute exposed a deceptively hard problem: when a draft changes while other internet registries are still assessing it, an appeal cannot prove compatibility—or incompatibility—by attaching an old reply to new words. It needs a versioned record that…
Story
Three seats were enough on paper: AFRINIC’s disputed quorum repair
A five-seat review body lost two members while three appeals needed somewhere to go. AFRINIC’s Board answered with a temporary permission: the three survivors could carry on. They answered in turn that they would not. That compact reversal exposes a larger institutional…
Story
Resolution 202104.602 and AFRINIC’s Twenty-Four-Hour Appointment Bridge
On 9 April 2021, AFRINIC’s Policy Liaison named Vincent Ngundi and Darwin da Costa as the Policy Development Working Group’s consensus choice but left their term lengths unresolved; on 10 April, the Board crossed that remaining gap by assigning Vincent two years and Darwin one…
Story
The Decision Before the Invitation: Resolution 202101.595 and the Order of Consent
AFRINIC’s mailing-list rules acquired two approval dates and one public comment window. The awkward fact is that the first approval came before the invitation to comment. That does not make the consultation worthless, but it does change what the consultation can honestly be said…
Story
The mailbox test that entered a meeting without a defined consequence
AFRINIC’s sixth Abuse Contact Policy Update arrived with a precise timetable for checking contact records but no operative answer to the most consequential question: what, exactly, would follow a failed check? Its passage through an online meeting exposed why delivery, response…
Story
Consensus could move Draft 2. It could not create the power the draft assumed
In September 2020, AFRINIC’s co-chairs declared consensus on a second draft about Board prerogatives in the Policy Development Process. That procedural judgement could move an identified text through a private coordination process. It could not answer the prior question that…
Story
Five Minutes at the Registry, Longer on the Network
AFRINIC’s second draft of its RPKI AS0 proposal introduced a narrow but important restraint: a separate trust anchor could let networks choose whether to receive the registry-generated warning and let observers measure it apart from ordinary holder authorisations. That choice…
Story
AFRINIC 32 and the virtual policy floor without a denominator
When AFRINIC moved its public policy meeting online in September 2020, it kept a consequential private coordination process alive; it also made the quality of access, identity, speaking order and public evidence inseparable from any claim about what the virtual room meant.
Story
The Board Could See the Risk. Draft 1 Asked Whether It Could Act
AFRINIC’s Board might have been right to notice a danger to the company or to network continuity. That observation did not, by itself, tell the Board whether it could originate policy, alter community text, stop deliberation, veto an outcome or direct somebody else to act. The…
Story
The emergency ledger: what Resolution 202006.556 proves—and what it leaves unauditable
In June 2020, AFRINIC’s Board placed a numbered decision in its corporate record: Resolution `202006.556`, adopting an organisational contingency policy. The decision could represent sensible preparation. A registry should not wait for systems, credentials, staffing or essential…
Story
One resolution, two proof burdens: what AFRINIC had to preserve in 202002.552
One resolution, two proof burdens: what AFRINIC had to preserve in 202002.552 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…