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 Policy Compliance Dashboard appeal tested reviewability of a non-consensus assessment
The Policy Compliance Dashboard looked like an administrative instrument, but its classifications sat upstream of notices and potentially serious registry actions. When the co-chairs concluded that significant objections remained, the ensuing appeal posed a more important…
Story
The date that made the appeal: Draft 4 and the limits of internal review
On 7 October 2020, after a last call begun on 21 September and amid disagreement over whether changes in Draft 4 had received enough final review, the co-chairs said consensus was maintained. The two appeal records that followed did not ask the Appeal Committee to choose whether…
Story
When ‘No Consensus’ Must Give Reasons: The 2020 RPKI AS0 Draft 2 Appeal
In 2020, a proposal for a machine-readable routing-security signal was halted by a distinctly human judgement: AFRINIC’s co-chairs assessed that its second draft lacked consensus. The ensuing appeal put the negative decision itself under scrutiny. Its enduring significance lies…
Story
The dashboard that could reveal a difference but could not create a punishment
A proposed MyAFRINIC screen promised to put payment records, documents, contact history, routing-adjacent signals and transfer questions in one private view. That convenience could have made registry records easier to correct. It also risked making fundamentally different kinds…
Story
The Six-Month Return Clock: Draft 8 and the Limit of AFRINIC’s RSA Power
For an operator, six months is not an abstract grace period. It can be the interval between an adverse registry finding and the forced unwinding of part of a live address portfolio: customer migrations, reverse-DNS changes, routing-security dependencies, transfer choices, legal…
Story
The Penalty Draft 4 Left Undefined
AFRINIC’s fourth abuse-contact proposal looked softer because it erased an elaborate failure ladder and its express route toward revocation procedures. Yet the shorter text preserved the power that mattered most: discretion to warn a resource holder and block unspecified services…
Story
Two Clauses, One Broken Bridge
AFRINIC’s third draft of its Resource Transfer Policy changed only two provisions: section 5.7.3.2 imposed a twelve-month post-transfer restriction on a source seeking more AFRINIC IPv4 space, and section 5.7.4.3 preserved the legacy status of transferred legacy resources.…
Story
Eighteen Days to Redraw a Boundary: What AFRINIC’s Draft 5 Left Unsettled
AFRINIC’s official details and current proposal list place eighteen days between Draft 4 and Draft 5 of its abuse-contact proposal, then only twelve days between Draft 5 and the AFRINIC-31 discussion. That narrow interval matters because the new draft made a genuine concession…
Story
Four Weeks to Show the Work: Evidence Before AFRINIC Consensus
At AFRINIC-31, a proposal about impact analysis exposed a harder question than whether staff could meet a deadline. It asked whether people should have a timely, shared account of technical, operational, financial and legal effects before they were asked to accept a rule—and what…
Story
The Zero That Had to Move First: AFRINIC’s First AS0 Draft and the Design of Reversible Warning
On 4 November 2019, AFRINIC published its first proposal to originate AS0 ROAs for address space recorded as unallocated. The idea offered operators a useful authenticated warning: ordinary public routing should not emerge from space that the registry ledger said nobody had been…
Story
The Electorate Behind the Chair: What AFRINIC’s 2019 Draft Could—and Could Not—Authorise
In November 2019, a proposal to formalise elections for the chairs of AFRINIC’s Policy Development Working Group offered a six-month mailing-list electorate, electronic voting and a full procedural calendar. It also placed candidate screening, objections, ratification, vacancy…
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…