Summary

  • On 14 July 2010, Vincent Ngundi, signing as chair of the AfriNIC Policy Development Process Moderation Group, said the Soft Landing proposal had received “considerable objection.” He returned it to the Resource Policy Discuss mailing list for further deliberation and possible discussion at the next face-to-face meeting, and advised the author to incorporate the comments and resubmit. That was a genuine procedural reversal, not a ceremonial closing notice.
  • The surviving objections were concrete but not reducible to a vote. They disputed the evidence for consensus, sought the calculation behind a /23 maximum, questioned the effects of four separately requested blocks on aggregation and direct end-user demand, disagreed about reserves and potentially stranded space, contested the theory of forcing IPv6 transition, identified drafting ambiguity, and urged delay until better statistics could support the thresholds.
  • The reversal deserves credit because it prevented the momentum of a 3 June meeting conclusion from automatically carrying a contested draft onward. Its weakness is equally important: the phrase “considerable objection” came without a count, denominator, materiality test, or issue-by-issue disposition. The record proves that the proposal changed procedural state, but it does not let a later reader reproduce precisely how each concern was weighed.
  • AFRINIC's legitimate role here was that of a private bookkeeper and technical coordinator. It could maintain accurate registry procedures, protect uniqueness, and send a proposal back for revision. It did not legislate for Africa, adjudicate legal rights, punish operators, confiscate assets, allocate an address through the 14 July notice, or acquire ownership power over the resources described in policy prose.

Analysis

The decision that changed the draft's direction

The most important sentence in the record is the conclusion, not the earlier assertion that the proposal had reached consensus with changes. At 09:13:10 UTC on 14 July, Vincent Ngundi announced that the PDP-MG had considered the deliberations during last call and found considerable objection to Soft Landing. The disposition followed directly: the proposal would go back to the RPD list for further deliberation and possible discussion at the next AFRINIC meeting. The author was advised to incorporate comments received during last call and resubmit.

That sequence matters. A draft moving along a private coordination process normally accumulates momentum. A meeting conclusion becomes the premise for a review window; the end of that window can then be treated as a near-automatic step toward ratification. The 14 July message broke that chain. It did not merely note dissent while allowing the draft to continue. It changed the proposal's status from one moving forward after a meeting conclusion to one requiring further discussion and new text.

The same message gives a useful internal comparison. A separate revised policy-development proposal was described as having no objections and moving onward to a recommendation for ratification. Soft Landing was treated differently. That contrast shows that “considerable objection” had a procedural consequence. It was not a decorative acknowledgment added to an otherwise predetermined result. Within the process, the finding stopped the next step.

The bounded meaning must remain exact. The PDP-MG did not finally reject or repeal a policy. It did not allocate or withdraw address space, alter a route, decide ownership, impose a sanction, or settle a legal controversy. It redirected one draft within a private technical process. Calling this a reversal accurately describes the procedural direction; enlarging it into an act of government would misdescribe both the record and AFRINIC's authority.

This distinction is not semantic caution for its own sake. Scarcity procedures can affect operator planning, application frequency, network design, and continuity costs. Those practical consequences make disciplined coordination more important, not more sovereign. A private registry's capacity to classify an objection and return a draft is valuable precisely because the decision remains reviewable and bounded. Its usefulness comes from correcting the registry's own process before implementation, not from claiming power over the public.

What was numerically at stake

The objections cannot be understood without the values in the last-call text. During the exhaustion phase described by the draft, the minimum allocation or assignment was /24, equivalent to 256 addresses, and the maximum was /23, equivalent to 512. A requester could receive up to four allocations or assignments, but the blocks had to be requested and issued separately. Eligibility required at least 90 percent utilisation of all previous allocations or assignments. The planning horizon for demonstrated need had been reduced from 12 months to eight months.

The proposal also reserved a /12 from the final /8 for future uses not yet anticipated. For each block issued during the exhaustion phase, no more than 10 percent could be used outside AFRINIC's service region, and that outside-region use was framed as supporting connectivity back to the region. If a requester did not already hold an IPv6 allocation or assignment, the process paired the IPv4 request with an IPv6 allocation or assignment.

Each number created a distinct control surface. The /23 ceiling determined how much an eligible requester could obtain in one event. The four-block limit determined how many such events could occur under the stated allowance. The 90 percent test decided how much unused capacity an organisation could retain before seeking more. The eight-month horizon compressed the period of demand recognised in one application. The /12 reserve withdrew a large portion from ordinary exhaustion-phase availability for later purposes. The 10 percent condition connected registry eligibility to a geographic-use description.

The IPv6 accompaniment linked access to a transition objective.

These controls did not all point in one direction. A low maximum might spread remaining stock across more request events and delay depletion under one model. It might also force growing networks to apply more often, split requirements, seek direct end-user space, or accept less aggregation under another. A high utilisation threshold might deter speculative requests, yet it could penalise lumpy growth, redundancy, disaster recovery, and capacity held for foreseeable expansion. A reserve might preserve flexibility for unknown needs, while vague future-release criteria could concentrate discretion.

The proposal was therefore not simply “conservation” expressed in neutral arithmetic. Its values allocated administrative dependence, timing risk, and operational adjustment among different kinds of requester.

The archived discussion proves that participants contested those mechanisms. It does not prove that any predicted effect later occurred. That line must be held carefully. Numbers in a proposal are direct facts about the proposed instrument. Forecasts about routing, depletion, incentives, or adoption remain attributed arguments unless operational evidence independently demonstrates the outcome.

From a challenged consensus claim to a formal review

On 23 June, before the formal opening notice, McTim disputed both the policy design and the process description. He said he had not seen the consensus that the PDP-MG said it saw in the room or on the list. He also advanced calculations about exhaustion, membership growth, and the amount of address space that might become inaccessible under the proposed limits. Those calculations mattered to the debate because they challenged the economic rationale of the threshold. They are not an independently verified inventory or later outcome.

McTim's numerical claims were specific. He referred to about 1,009 members, growth below 100, capacity for 7,680 LIRs under his assumptions, and the possibility that roughly 80 percent of the relevant space would be locked up. The record establishes that he made those claims as part of his objection. It does not establish that the membership assumptions were complete, that the forecast path materialised, or that the proposed policy actually produced that result. Treating the calculation as testimony rather than outcome evidence preserves its proper significance: it was a reason the draft's basis needed to be tested.

Other contributors did not form a single opposing bloc. Auwal Tata supported the concern that exhaustion could occur without the proposed cap. Douglas Onyango recalled that a change discussed at the meeting was meant to be incorporated. Alain Aina defended the objective of a gradual transition. Alan Barrett said he was unhappy with how consensus had been declared, while also stating his belief that the proposal as a whole had consensus subject to several changes. These positions show overlapping disagreements about procedure, drafting, values, and transition strategy. They do not yield a binary tally.

The formal review opened on 25 June with a complete circulated draft and an announced end date of Saturday, 10 July. That publication is part of the strongest defence of the process. Participants could inspect the actual rules, identify wording defects, debate the assumptions, and submit criticism outside the room. The procedure did not ask readers to react to a title or a summary alone. It put the operative language in view and left a stated interval for response.

Graham Beneke, who said he had not attended the meeting, immediately exposed a central evidentiary gap. He asked for the resource-planning calculation behind the /23 maximum and argued that the ceiling could make a request pointless for some networks. His intervention was a question and a practical argument, not proof that /23 was wrong. Yet the absence of a reproducible calculation is itself material when a proposed threshold determines the size and frequency of access. A qualitative process may decide values by judgment, but it should still reveal the model that makes one prefix length preferable to another.

Scott Leibrand then analysed the interaction between rationing and routing structure. In his assessment, limiting organisations to four /23 blocks could lead larger customers to seek direct end-user assignments and could reduce aggregation. Again, this is not evidence that those changes happened. It is a contemporaneous mechanism claim: if an upstream cannot supply enough space under its own limit, a customer may have an incentive to obtain space independently, with possible consequences for announcements and aggregation.

The claim required technical evaluation because it connected a conservation rule to a potentially countervailing network cost.

Badru Ntege offered a contrasting evaluation. He said that making the status quo unattractive could be a positive unintended consequence. That position made an important disagreement explicit. For some participants, administrative discomfort under constrained IPv4 access could accelerate migration. For others, deliberately worsening the IPv4 experience risked transferring cost to operators and users without proving that transition dependencies were ready. The thread records the disagreement; it does not demonstrate which prediction prevailed in running networks.

On 26 June, Mark Elkins argued that the fundamentals could move forward and be revisited after 12 or 18 months. He also suggested possible alternatives, including /22 or /21 values and /10 or /11 trigger ideas. His defence was pragmatic: do not lose a broadly useful scarcity framework because every parameter lacks final precision; deploy a workable foundation and revise it through the policy process as evidence emerges. Alan Barrett similarly answered that policies could later be changed through that process.

That defence deserves full weight. Perfect information is unavailable during a depletion transition, and a requirement to settle every future contingency can freeze useful coordination. Iteration is a normal property of technical governance. A private coordinator may reasonably choose a reversible rule, observe effects, and amend it. But the argument depends on reversibility being real. If a threshold redistributes costs or changes routing decisions before review, “we can fix it later” is not a substitute for the missing calculation. The more difficult it is to unwind operator adaptations, the stronger the case for evidence before movement.

SM identified wording and allocation-size issues. Douglas Onyango reposted an updated full text on 27 June after those comments. This demonstrates that the review was capable of producing repairs while it was open. It does not demonstrate that every substantive objection was resolved. A corrected definition and a challenged numerical rationale occupy different categories. The former may be answered by revised prose; the latter may require data, assumptions, sensitivity analysis, and an explicit decision about acceptable trade-offs.

On 2 July, S. Moonesamy reminded the list that the review would end on 10 July and asked the proposal authors to ensure that all post-meeting comments were addressed. The message points to a basic procedural obligation: a response window is useful only if questions are carried into a disposition. Merely collecting comments creates an archive; showing how material comments changed, failed to change, or delayed the draft creates an accountable decision record.

After the announced end date, Alain Aina argued on 13 July against rushing adoption. He proposed using statistics and trends to choose the later-phase thresholds and minimum and maximum values. This was not a generic request for endless delay. It went to the evidentiary basis of the scarce-resource controls. The timing also matters: the 14 July conclusion said the PDP-MG had considered deliberations during last call, while the public sequence includes a material argument immediately before closure. The record establishes proximity and subject matter, but it does not reveal the internal weighting of that message.

The next day, Ngundi recorded the finding and the return. Later events confirm that this was more than a pause in messaging. On 1 November, Paulos Nyirenda asked for revised text for discussion at the forthcoming meeting and referred back to the July conclusion. On 7 November, Douglas Onyango resubmitted a text with a /27 minimum, a /22 maximum, and no four-block limit. Compared with the last-call values, the minimum had become smaller, the maximum larger, and the repeated-block structure had changed.

That later text movement is bounded evidence. It proves that the proposal did not simply reappear with all key values untouched. It does not prove adoption, ratification, or implementation. Nor does it supply a one-to-one causal map in which Beneke caused the /22 maximum, Leibrand caused removal of the four-block limit, or any other named participant caused a specified edit. Several objections overlapped; authors could have had additional reasons; deliberations could have combined considerations. The responsible inference is that text changed after the reversal, not that the archive exposes every causal link.

Seven objection classes, not one opposition count

The first visible class concerned consensus evidence. McTim disputed seeing consensus in the meeting or list. Alan Barrett criticised the way the meeting conclusion had been declared while believing the overall proposal had support subject to changes. Douglas Onyango recalled a change that was meant to be incorporated. The dispute therefore was not simply “supporters versus opponents.” It included a question about whether the text presented for review matched the conditions attached to the earlier conclusion.

No complete denominator resolves that question. There is no complete attendance count tied to a roll call, no vote, no public matrix mapping issues to positions, and no reconstruction showing what every attendee heard or accepted. That absence does not prove there was no consensus. It limits what can be claimed from the label. A chair body's qualitative assessment can guide its private procedure, but the label cannot be inflated into a statistically representative mandate.

The second class concerned the /23 calculation. Beneke asked for it; Elkins proposed possible larger alternatives; Aina asked that statistics and trends inform the values. These interventions shared a demand for explainability even where their preferred answers differed. A threshold of 512 addresses is not self-justifying because it appears in a draft. A defensible selection would show the inventory model, requester distribution, demand horizon, uncertainty range, aggregation effects, and sensitivity to membership and end-user eligibility.

No public planning workbook survives in the event record. Consequently, a later analyst cannot reproduce the decision path from inventory assumptions to /23. That gap is more serious than a missing rhetorical explanation. Prefix thresholds are discontinuous: moving from /23 to /22 doubles the addresses in the maximum block, while a /27 minimum changes accessibility for smaller requests. A small textual change can therefore produce a large difference in allocation cadence and administrative burden.

The third class concerned aggregation and request incentives. McTim argued that small maxima would promote multiple /23 announcements. Leibrand reasoned that rationing an upstream to four /23s might push large customers toward direct end-user space and reduce aggregation. These mechanisms challenge the notion that a lower per-request maximum mechanically conserves resources without other effects. Operators respond to constraints. They may change application structure, customer architecture, routing announcements, sourcing, or timing.

The discussion did not prove such responses occurred. The 14 July act itself neither issued a block nor changed the routing table. Yet a policy review need not wait for damage before considering a plausible mechanism. Its task is to decide whether the risk is sufficiently material, whether the model can estimate it, and whether telemetry could detect it if the rule proceeds. The objection was thus relevant as a design warning even without becoming outcome evidence.

The fourth class concerned scarcity and potentially stranded inventory. McTim's figures suggested that limiting access by member and block counts could leave much of the final pool unavailable under his growth assumptions. Replies pointed out that end users enlarged the eligible population and that future policy change remained possible. This exchange exposed two different conceptions of preservation. One treated a slower release path as protection for future access. The other warned that an overly restrictive mechanism might strand stock behind rules that did not match actual demand.

Neither side can be declared empirically correct from this record. The argument depends on forecasts, eligibility, growth, and later rule changes. What can be said is that the proposal's conservation claim had a distributional mechanism. Preserving addresses in a registry pool is not identical to preserving network continuity. A block held back from today's requester remains available in one accounting sense, but the denied or delayed operator may incur cost in another. Sound coordination must measure both the inventory path and the operating consequences.

The fifth class concerned IPv6-transition theory. Aina defended a gradual transition purpose. Ntege regarded a less attractive status quo as potentially beneficial. Others challenged whether rationing IPv4 would produce the desired migration or instead impose avoidable friction. The last-call text also required an IPv6 allocation or assignment where the requester had none, tying the mechanisms together at the application level.

The critical principle is that transition policy remains subordinate to deployable networks. A registry process cannot make dependencies IPv6-capable by assertion. It cannot erase customer constraints, legacy systems, peering realities, or service continuity obligations. If administrative scarcity is meant to alter behaviour, its designers need evidence that the substitute path is operationally available and that the burden falls where adaptation is possible. Otherwise, the rule may measure procedural compliance while running systems absorb the downside.

The sixth class concerned drafting ambiguity. SM identified definition and size wording problems, and Onyango issued updated text during the review. This is the clearest example of the process functioning as direct error correction. Public inspection surfaced defects, and the proposal text moved. It is also a warning against collapsing every comment into the same category. Editorial ambiguity can often be cured by an exact replacement sentence. A disputed maximum or transition mechanism requires a different form of answer.

The seventh class was a request for evidence-based delay. Aina's 13 July intervention argued that statistics and trends should support the later-stage thresholds. Delay is sometimes portrayed as the absence of decision, but here returning the draft was itself a decision about sequence. It said, in effect, that movement toward ratification should not outrun unresolved questions. Because the draft concerned scarce-resource access, preserving the pre-implementation state while revising was a meaningful risk choice.

Taken together, these classes explain why a raw objection count would have been insufficient. One technically supported challenge to a core threshold may be more consequential than many expressions of preference. A corrected typo should not carry the same materiality as a missing calculation. A process can therefore reject mechanical voting while still documenting its reasoning. Qualitative judgment and auditability are not opposites.

The strongest case for the PDP-MG's action

The best defence begins with what the procedure demonstrably did. It made the full draft available, stated a closing date, allowed absent participants to enter the discussion, accommodated textual corrections, permitted competing technical theories, and did not treat the meeting conclusion as irreversible. When objections remained, the PDP-MG sent the proposal back. That is evidence of a functioning correction path.

The process also avoided a crude vote. Technical questions are not resolved by adding names without examining reasons. A contributor may raise several weak points; another may identify one fatal dependency. Participants may agree on the objective while disagreeing over a value, wording, or implementation condition. Alan Barrett's position illustrates the complexity: criticism of how consensus was declared coexisted with a belief that the proposal broadly had consensus subject to changes. A binary support column would have discarded that information.

There was also a serious practical argument for iteration. Elkins's suggestion that fundamentals could proceed and be revisited after 12 or 18 months recognised that depletion planning occurs under uncertainty. Barrett's point that policy could be changed through the PDP acknowledged a mechanism for learning. Requiring mathematical certainty could have made timely coordination impossible.

Finally, a volunteer technical process should not be forced to imitate a court. A complete judicial-style judgment for every comment could exhaust the people maintaining the work and deter participation. The appropriate standard is not legal formality. It is enough structure to make a consequential technical disposition understandable and reproducible: what issue was raised, what evidence supported it, how the author answered, why the chair body classified it as material or immaterial, and what state followed.

On that standard, the 14 July return was the correct direction. Faced with unresolved numerical and operational questions, the PDP-MG did not borrow authority from the earlier room and push the draft onward. It required another cycle. The action demonstrated restraint within the institution's own bounded role.

The strongest objection to the closure record

The weakness is not that the PDP-MG refused to count votes. It is that “considerable objection” was the end of the public explanation rather than the start of a disposition record. No number of objections was published. No denominator identified the relevant participant population. No materiality standard showed when a challenge becomes sufficient to stop movement. No table said which issues were answered, which remained open, which were editorial, and which drove the return.

As a result, the conclusion is authoritative only about its own procedural act: the PDP-MG found enough objection to return the proposal. It is not independently reproducible as an evaluation. A later reader can reconstruct plausible objection classes from the list, but cannot know whether the PDP-MG used the same taxonomy, gave decisive weight to one calculation, combined several concerns, or relied on some other process consideration. The archive preserves inputs and outcome while leaving the weighting function opaque.

That opacity creates two hazards. First, it weakens learning. Authors revising a draft need to know which objections require new evidence and which require clearer wording. Participants need to know whether their concern was understood. Future chairs need a lineage showing why a parameter moved. Second, the phrase can be reused outside its proper bounds. Detached from the underlying record, a consensus or objection label can be cited as if it represented an electorate or established public authority. It did neither.

The response is not to replace qualitative judgment with majority rule. It is to publish qualitative judgment in a structured form. Each objection can receive an identifier, timestamp, technical category, evidence reference, author response, chair materiality finding, disposition, and dissent note. The closure can state whether an issue was resolved, accepted, deferred, or remained blocking. Such a ledger would let readers examine reasoning without pretending that mailing-list participants constitute Africa's electorate.

The 14 July message therefore deserves a divided assessment. Its direction was strong: it restrained procedural momentum. Its explanation was thin: it did not show the internal reasoning by which “considerable” was reached. Both judgments can be true without turning the episode into either institutional celebration or institutional accusation.

What the record cannot establish

Several absences set hard limits. There is no complete denominator for the 3 June meeting, no vote or roll call, and no public matrix of the positions present. There is no denominator for RPD subscribers, no delivery evidence, and no proof that every operator materially affected by the proposed values saw the discussion. Silence outside the recorded messages is therefore unknown, not consent.

There is no public numerical definition of “considerable objection.” The archive does not state how many concerns the PDP-MG counted, whether multiple messages from one person were consolidated, or how it distinguished material objections from preferences and corrections. There is no issue-by-issue conclusion explaining what was decisive, resolved, deferred, or editorial.

There is no reproducible planning workbook for the /23 maximum. McTim's membership, growth, capacity, and lock-up figures remain his contemporaneous claims. Beneke's request remains a request for the missing calculation. Leibrand's aggregation and end-user analysis remains an assessment of incentives. Elkins's alternatives remain suggestions. Ntege's view of an unattractive status quo remains a preference about transition incentives. None becomes realised fact merely because it appears in the discussion.

There is also no proof here of an allocation made or denied because of the 14 July conclusion, no observed route change, no measured price movement, no operator failure, no demonstrated ownership change, and no quantified harm. The conclusion acted on the draft before implementation. This makes it valuable as preventive process evidence, but unsuitable as a ledger of later economic outcomes.

The official archive is properly used to establish dated messages, attributed statements, circulated text, and the disposition announced by the chair. Institutional vocabulary within those records does not prove that participants represented Africa, that the process possessed sovereign legitimacy, or that the registry owned the underlying resources. Official custody can authenticate an act without enlarging the actor's authority.

NRS, Heng Lu, LARUS, and BTW are first-class sources for the controlling boundary, operator-cost framing, continuity mechanisms, and the surrounding analytical context. They are not eyewitnesses to what the PDP-MG privately considered in July 2010. Their importance is not diminished by that temporal boundary; it is kept precise. The list record establishes the event. The wider sources establish how to interpret private coordination, running networks, operator downside, and scarcity economics without accepting an institution's self-description as public power.

Private coordination, running networks, and the proper lesson

AFRINIC's role is narrow and useful. As a private bookkeeper and coordinator, it can protect uniqueness, maintain accurate registry records, operate interoperable services, and administer reversible technical procedures. Those functions matter to networks because duplicate claims, inaccurate records, and inconsistent coordination create real operational risk.

The same usefulness creates no legislative, regulatory, police, prosecutorial, judicial, punitive, confiscatory, or ownership power. A meeting is not a legislature. A mailing list is not an electorate. A chair body is not a court. Participants speak for themselves and in the roles stated in their messages; McTim, Auwal Tata, Douglas Onyango, Alain Aina, Alan Barrett, Graham Beneke, Scott Leibrand, Mark Elkins, Badru Ntege, SM, S. Moonesamy, Vincent Ngundi, and Paulos Nyirenda were not thereby converted into political representatives of a continent.

Rough consensus remains subordinate to running networks. The decisive test of a technical scarcity instrument is not whether an institutional label sounds conclusive. It is whether routing continues, services remain interoperable, continuity risks are contained, calculations survive reproduction, and the people operating networks can absorb or reverse the imposed changes. Operators bear the downside when an eight-month horizon, 90 percent utilisation condition, small block maximum, block-count limit, reserve, or geographic-use clause fails to match operational reality.

This is why the 14 July reversal is worth studying. Procedure interrupted itself before the draft became an implemented constraint. The PDP-MG treated the public objection record as capable of falsifying the momentum created by a prior meeting conclusion. In doing so, it acted more responsibly than it would have by calling last call complete and moving ahead despite unresolved questions.

But procedure did not manufacture authority. The return to the list bound the proposal's path inside a private process; it did not bind Africa as a polity. The participants supplied technical evidence, arguments, corrections, and preferences; they did not vote on behalf of every operator or end user. The correct credit is institutional restraint, not sovereign legitimacy.

The durable design lesson is an auditable error-correction circuit. A consequential draft should have stable text, reproducible numerical models, explicit assumptions, sensitivity ranges, an objection ledger, written responses, a published materiality finding, and a reversible return path. Material changes to minimums, maximums, eligibility, geographic scope, or discretionary reserves should begin a fresh review of a newly identified text. Implementation, if it occurs, should produce telemetry against the purpose claimed for the rule.

In this episode, the return path worked while the explanation layer remained incomplete. The proposal moved back. Months later, key values were different. Yet the archive cannot reproduce the chair body's weighting or causally assign those edits. The lesson is consequently precise: preserve the power of a qualitative technical process to stop itself, and require enough evidence around that stop to keep later institutional storytelling from exceeding what the record proves.