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
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…
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
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
Ratification was not implementation: the 107-day chain behind AFRINIC’s IPv6 manual repair
A unanimous Board vote on 8 August 2018 settled one institutional question but left two practical jobs visibly unfinished. AFRINIC still had to notify the policy chairs and put the adopted IPv6 reference update into its working manual. The resulting chain—from recommendation to…
Story
The Forecast at the Registry Door: AFRINIC’s 2018 IPv6 Allocation Rewrite
AFRINIC’s second draft of the IPv6 Initial Allocation Update tried to make the registry fit real networks rather than force every applicant through a narrow service-provider model. It widened who an LIR could serve, allowed evidence for an initial block larger than `/32`, offered…
Story
The constitution in the quiet room
PDP Bis Draft 3 tried to make AFRINIC’s policy machinery legible: four phases, named objections, reasons at the Board gate and a timed internal appeal. Its clarity was real. So was its deeper problem. A private technical registry can organise deliberation and protect the…
Story
The Fairer Lottery That Could Not Supply AFRINIC’s Missing Mandate
Draft 6 widened AFRINIC’s proposed random resource-review lottery from a few named membership categories to the entire membership. That was a genuine correction of unequal exposure. Yet a fairer pool cannot answer the prior question: what may a private registry inspect, on whose…
Story
When a /64 crosses a device boundary but control stays put
A visitor joins an office Wi-Fi network and receives a temporary IPv6 /64 from the organisation that runs the access point, router and upstream link. The address space has reached a third party, but the network has not changed hands. In March 2018, the first draft of AFRINIC’s…
Story
The rule beneath the rewrite: AFRINIC’s Draft 2 and the threshold of reverse-DNS cleanup
A resolver is sent to a nameserver that is dead, silent or unable to answer authoritatively. The apparent remedy is modest: correct the parent record so that it no longer points towards a service that is not there. Yet the correction is not consequence-free. In reverse DNS…
Story
Three edits, one private queue: what Soft Landing BIS Draft 6 clarified
On 22 September 2017, Soft Landing BIS Draft 6 made three recorded repairs: it clarified demonstrated need across exhaustion phases, reworded the recurrence clause, and said that a new IPv6-deployment `/12` replaced the old unforeseen-use `/12`. Those edits mattered because a few…
Story
When “Must Remove” Became AFRINIC’s Operational Duty
Resolution 201803.395 was a brief corporate decision with a long technical shadow. By ratifying a policy that required the removal of persistently lame reverse-DNS nameserver attributes, AFRINIC’s Board did not acquire regulatory power; it accepted responsibility for making a…
Story
The Three-Month Cure: What AFRINIC Draft 5 Did—and Did Not—Authorise
Three months stood between public identification and the proposed recovery of an Internet number resource. After trying to contact the member and correct an observed discrepancy or non-compliance, AFRINIC would publish the resources concerned; during the interval, the…
Story
Five Seats, Fourteen Days: What AFRINIC’s Second Appeal Charter Actually Changed
On 26 November 2017, AFRINIC approved a redesign of five reviewer seats while leaving an appellant just fourteen calendar days to challenge a policy chair’s decision. That juxtaposition matters. A filing window determines whether an objection can be heard; a composition rule…
Story
The appeal with a clock, but no door out of the house
On 9 November 2017, Draft 2 of AFPUB-2017-GEN-002 rearranged the controls of AFRINIC’s proposed policy process. One Chair and an assisting Vice-Chair became two chairs, each placed nearer the levers of discussion, phase progression and rough-consensus assessment. An appeal no…
Story
The consensus receipt Draft 7 never showed
On 26 December 2017, AFRINIC’s co-chairs described a Last Call dominated by repeated petition letters and one substantive objection, then urged immediate Board ratification. A later official review looked at that same procedural stage and found considerable opposition, no…
Story
Who gets to call consensus? The constitution inside AFRINIC’s PDP Bis Draft 1
Published on 28 April 2017, PDP Bis Draft 1 proposed something larger than a tidy set of meeting rules. It was an internal constitution for the process that would make later number-resource policy. One Chair, assisted by a Vice-Chair, would classify input, control movement…
Story
Thirty-two parts of a request: the queue inside AFRINIC’s Draft 4
On 31 March 2017, AFRINIC’s operative Soft Landing policy entered Phase 1 with a `/13` ceiling. Fourteen days later, on 14 April, Draft 4 proposed a `/18` ceiling instead. That was not a cosmetic adjustment. It would have reduced the largest request event from 524,288 addresses…