Summary

  • On 7 January 2009, Vincent Ngundi, identified as chair of the PDP-MG, transmitted Douglas Onyango's first IPv4 Soft Landing draft to AFRINIC's RPD list for review and discussion. The posting did not itself establish policy, consensus, representative authority, ownership or implementation.
  • The draft would preserve ordinary policy until a request could not be met without the prospective final /8, or could be met only by emptying the pool outside that /8. It then proposed a minimum-sized /23 unit, a one-unit-per-application ceiling for existing LIRs, a four-unit maximum for new LIRs, an IPv6-plan condition for further IPv4, an eight-month planning horizon and a /16 reserve with two purposes and a release condition.
  • The strongest case for the design is temporal fairness: smaller recurrent allocations could preserve options for later and new entrants while a reserve protected shared infrastructure and unforeseen needs. The hardest weaknesses were not scarcity itself but undefined judgment—especially what AFRINIC's “ratification” of an IPv6 plan meant, how use would be observed, how a disagreement could be reviewed and whether the shorter horizon would conserve anything.
  • This article analyzes only the first draft as posted on 7 January 2009, not the later ratified policy, later amendments or implementation. The sealed record supplies no measured depletion effect, beneficiary analysis, applicant distribution, plan-ratification standard or evidence of real-world outcomes.
  • AFRINIC's legitimate role here is that of a private technical coordinator and bookkeeper allocating a still-unallocated stock. Scarcity does not make it a sovereign, legislature, regulator, police force, prosecutor, court, punisher, confiscator or owner of issued number resources.

The act was circulation, not settlement

The institutional act under examination lasted no longer than it took to send a message. At 05:37:40 UTC on 7 January 2009, Vincent Ngundi, writing as chair of the PDP-MG, placed a proposal authored by Douglas Onyango before the RPD mailing list. The reproduced document carried a 5 January date, identified Onyango with Sitronics Telecom Solutions Uganda, and labeled itself a draft. Ngundi said the group had received it on 6 January. His request was for review and discussion. Roughly an hour later, a substantially identical transmission circulated, with a small difference in whether the invitation addressed members or the community.

That duplicate corroborates circulation; it is not a second version and not a second vote.

This documentary status matters because the proposal's subject—access to a finite common pool—can make an opening move look more authoritative in retrospect than it was at the time. A contemporary description of AFRINIC's policy process said that anyone could submit a proposal, that list discussion would run for at least 30 days, that the proposal could be presented at a public policy meeting, followed by last call, and then considered by the Board. Whatever one thinks of that procedure, it places the 7 January email near the beginning of a sequence. The message put language into circulation. It did not enact that language.

Nothing in the sealed record shows that posting established consensus, a representative mandate, legitimacy, title to address space or binding power. A policy list is a venue for technical coordination, not a legislature. Participation does not turn its contributors into an electorate for every operator in a region, and the chair's transmission does not turn a proposal into law. Those limits do not make the post unimportant. They identify exactly why it is important: it is the earliest authenticated public expression in this record of a particular rationing design, before discussion began changing its assumptions.

The design should therefore be read in two registers at once. As a document, it is strong evidence of what the first draft said. As an institutional outcome, it proves almost nothing beyond circulation and an invitation to discuss. It cannot prove that the mechanism was adopted, implemented, enforced, effective or supported. Nor can later ratification be projected backwards to lend the first posting a status it did not possess on 7 January.

That temporal discipline is essential. By 12 January, the author was already discussing altered timing and utilization ideas. A later official AFRINIC page records further revisions and eventual ratification of a later version. Those records demonstrate change; they are not permission to import later clauses, thresholds, identifiers, ceilings or results into the first draft. This article stops at the first-post mechanism. It does not retell the later Soft Landing history, final policy, implementation, depletion or waiting-list administration.

A contingent final pool

The first draft did not assume its own precondition had already occurred. It said it would become applicable only if the Global Policy for Remaining IPv4 was ratified. That global proposal contemplated distribution of one /8 to each regional Internet registry when the IANA pool reached a specified threshold. An official record still described it as proposed and in final call in early February 2009. The ICANN Board ratified it on 6 March, after the post being analyzed. On 7 January, therefore, the final /8 was prospective and the global policy was a future contingency, not a completed grant and certainly not a source of sovereign title.

Within that contingency, the draft divided time into a Current Phase and an Exhaustion Phase. During the Current Phase, the existing allocation policy would continue. The phase change came when an LIR request could not be fulfilled from the pool excluding the last /8, or could be fulfilled only by emptying that pool. The draft called this request the last accepted before the Exhaustion Phase.

That wording creates two related but not perfectly interchangeable edge cases. One is a request too large for the stock outside the final /8. The other is a request that fits exactly but consumes all of that stock. The text's treatment of the “last accepted” request is awkward enough that it should remain visible rather than be silently repaired by an interpreter. The operational question is whether the trigger request is fulfilled under ordinary rules and where its addresses come from, particularly when fulfilling it would reach or cross the line around the last /8.

The sealed record establishes the words of the trigger, not a later operational resolution of every boundary case.

The trigger was the first control point in the proposed instrument. Before it, documented demand could be considered under existing policy. After it, access would be fragmented and conditioned. In economic terms, the rule would exchange the ability to satisfy a larger present request for the option of retaining units for future requests. In administrative terms, it would change a common pool from a stock allocated under ordinary criteria into a stock deliberately paced through smaller releases.

A /8 contains 16,777,216 numerical addresses. That arithmetic describes the scale of the block, not the number of independently routable networks, active endpoints, customers or units of economic value. The draft's mechanism was not a claim that every one of those numerical positions was interchangeable in operation. It was a rule for how a coordinator would record allocations from an unallocated block.

This is the first distinction the scarcity debate must preserve. Depletion of a centrally administered free pool is real in the narrow sense that a finite stock can be allocated only once from that pool. It is not the disappearance of all usable IPv4 from running networks. It also does not prove that the coordinator owns every address, or that administrative scarcity grants permanent jurisdiction over already-issued holdings. A finite unallocated stock demands choices about sequence and quantity. It does not turn bookkeeping proximity into sovereignty.

The rationing unit and the two applicant classes

In the Exhaustion Phase, the draft substituted a /23 containing 512 numerical addresses for the /22 containing 1,024 addresses that it described as the then-current minimum allocation. The /23 was not stated as eternally fixed. The text connected it to whatever minimum allocation size applied: if that general minimum changed, the Soft Landing minimum would change accordingly. The mechanism was therefore a relative small-unit rule expressed through the minimum then in force, not simply an immutable preference for the number 512.

The draft then treated existing and new local Internet registries differently. An existing LIR could receive only one minimum-sized allocation per application, even if its documented need supported more. It could apply again, but additional IPv4 depended on beginning to use IPv6 according to a plan AFRINIC had ratified. The “per application” qualification is crucial. The first text did not impose an explicit lifetime maximum of one block on an existing LIR. Reading it as a one-block lifetime cap would materially exaggerate the restriction and erase the significance of repeated applications.

A new LIR faced a different ceiling. It could receive no more than four minimum-sized blocks, issued one at a time. At the initial /23 unit, that meant a maximum stated sequence of four blocks rather than the uncapped series theoretically available to an existing LIR through later applications. Additional blocks for the new LIR were likewise conditional on beginning IPv6 use under a ratified plan. The four-block maximum belonged to new LIRs only; extending it to existing LIRs would collapse the proposal's deliberate distinction between the classes.

The differentiation reveals the bargain inside the draft. Existing operators retained access through serial applications but lost the ability to satisfy a larger documented need in one allocation. New entrants gained a defined opportunity to receive more than one small unit but faced an aggregate ceiling. The design could be defended as a way to reserve entry opportunities while permitting incumbents to return as needs developed. It could also change behavior: a per-application cap may encourage more applications, make processing speed more consequential and turn administrative touchpoints into part of the allocation experience.

The first record cannot tell us whether any of those effects occurred. It contains no request-frequency data, applicant distribution, queue information, processing-cost study, behavioral model or measured account of who would benefit. It does not identify actual winners. The ceiling can be analyzed as an incentive structure, but not reported as an outcome.

Nor should small units be romanticized as intrinsically fair. A /23 allocation may preserve more units for later applicants, but it can also leave a present applicant short of documented operational need. The trade is between current fulfillment and future option value. That is a real policy choice over unallocated stock; neither side of it can be resolved by the arithmetic alone.

The IPv6 gate converted arithmetic into judgment

Quantity was only one half of the mechanism. The draft required an IPv6 adoption plan intended for implementation within eight months and said AFRINIC would ratify that plan. If an LIR did not have IPv6 space, AFRINIC would allocate it under the then-current IPv6 policy together with the /23 IPv4 allocation after ratification. Before receiving further IPv4, the LIR had to begin using IPv6 under the approved plan.

As written, this was a condition on access to additional, unallocated IPv4. It was not seizure of issued space, disconnection, punishment for using IPv4 or a sovereign command over network architecture. It did not confer police, prosecutorial or judicial power. It is still institutionally important because it joined a clear numerical rule to a discretionary assessment. Counting one /23 is straightforward. Deciding whether a plan deserves ratification and whether an operator has begun to use IPv6 requires a standard, evidence and a decision maker.

The first post did not provide those things in operational detail. It did not define what made an eight-month plan credible, which elements AFRINIC would assess, how consistent decisions would be produced, what evidence would demonstrate that use had begun, how long review could take, whether reasons would be published, who could challenge a rejection or what appeal path existed. It stated no consequence of disagreement beyond the allocation condition itself. Those are first-class-source gaps, not proof that no internal practice or later clarification existed. Within the sealed first-post record, however, they remain unknown.

McTim's immediate 7 January reply isolated the problem by questioning whether ratifying a member's plan intruded too far. The objection is evidence of one participant's concern, not a community finding. Yet it points to the exact design tension: the closer the plan test came to evaluating an operator's technology program rather than confirming an objectively observable step, the more discretion it placed in the bookkeeper's hands.

IPv6 preparation could plausibly have been advanced without claiming authority over an operator's broader choices. Offering IPv6 space alongside a terminal IPv4 allocation made dual-stack preparation concrete. Requiring a narrowly specified sign of deployment before another rationed allocation could align access to a common stock with a transition goal. But the legitimacy of that narrow instrument depends on its boundaries. A registry may administer eligibility for an unallocated pool. It should not convert an undefined policy preference into a general veto over protocol choices, business models or existing holdings.

Running-Code Primacy supplies the controlling test. Stable networks and deterministic coordination come before institutional ambition. Registry records coordinate uniqueness and describe operational allocations; they do not create routing reality. Encouraging IPv6 is consistent with the coordinator's technical role when the condition is explicit, measurable and confined to the remaining common pool. Treating the same condition as authority to discipline an operator beyond that pool would not be. The first draft did not make that punitive move, so it should not be accused of having done so.

Its defect was more modest and more remediable: the gate was underdefined.

Eight months and an unmeasured conservation claim

The draft also shortened the planning and allocation or assignment horizon from twelve months to eight months. It said the purpose was to reduce the quantity of unused addresses held by one party while others lacked them. That is an attributed rationale in the proposal, not a measured effect.

The logic is understandable. If an applicant receives only what it expects to require over eight months rather than twelve, less headroom may sit unused at the moment of allocation. Across a terminal pool, repeating that reduction could preserve options for later applicants. But another path is equally plausible: shorter horizons can produce more frequent requests. McTim questioned whether the eight-month interval would conserve addresses and suggested it might simply increase request frequency. Mark Elkins, responding on 8 January, also resisted the eight-month period and suggested postponing special rules until a smaller remainder.

Neither position is established as correct by the sealed evidence. There is no demand series, burn-rate model, utilization distribution, analyst-capacity estimate or quantified projection of how much longer the pool would last. There is no basis for saying the horizon preserved a particular number of addresses or a particular number of months. There is also no basis for asserting that it necessarily increased workload. What the record supports is a disputed mechanism: one side anticipated reduced unused headroom; a contemporary critic identified request frequency as an offsetting channel.

That distinction is useful because “conservation” can hide several different outcomes. The stock might be allocated more slowly. The same stock might be allocated through more transactions over roughly the same period. Distribution might broaden even if the terminal date barely moved. Or administrative delay might become a de facto rationing mechanism. The first post supplies no evidence to choose among these possibilities.

A credible evaluation would have required measurements designed before the phase began: application counts, repeat frequency, approved quantities, processing time, utilization evidence and remaining stock by applicant class.

The moral language of unused space must also be handled carefully. Scarce IPv4 holdings can function as productive operator capital, supporting continuity and planned growth. A forecast that proves high is not by itself proof of hoarding, and need-based allocation criteria do not license punishment of existing holders. At the same time, acknowledging productive capital does not abolish the finite central stock. The narrow question was how much newly unallocated space the coordinator should release at once. It was not whether the registry could pass judgment on all uses of already-issued resources.

A reserve with two jobs

From the final /8, the draft reserved one /16—65,536 numerical addresses—for unforeseen future use. It also designated that same /16 as the source of /24 blocks, each containing 256 numerical addresses, for root servers, generic and country-code top-level-domain registries, internationalized-domain-name registries and Internet exchange points. The reserve therefore had two jobs: contingency capacity and a supply for identified shared-infrastructure categories.

This detail prevents two tempting but inaccurate descriptions. The /16 was not wholly untouched, because the draft anticipated /24 allocations from it. It was not wholly dedicated to critical infrastructure, because the text also named unforeseen future use. And it was not a permanent exclusion from allocation. If the /16 remained unused after the rest of the /8 had been allocated, the draft returned it to the pool under the same policy.

The reserve was thus a postponement device with a release valve. Its option value came from holding space back while uncertainty remained. The release condition prevented unused contingency space from being stranded forever once the rest of the pool was gone. That combination is defensible, but putting two purposes into one block also made accounting more important. Each /24 granted to an identified infrastructure category would reduce what remained for the unforeseen. Each unforeseen allocation would change what remained for the listed categories. The first text did not supply separate sub-ceilings or a published ledger for the two uses.

McTim questioned the tension between calling the /16 a reserve and spending portions of it on specified infrastructure. Mark Elkins also asked about the mixed design and regional use. Their messages do not establish that the reserve was illegitimate or unworkable. They show that the dual-purpose description was noticed immediately and that the first text left room for divergent understandings.

A cleaner design could have separated a quantified infrastructure bucket from a contingency bucket, with distinct criteria and balances. That would reduce flexibility but improve observability. Alternatively, a shared /16 could remain flexible if decisions, balances and the event triggering release were published consistently. The draft's arithmetic identified the outer block and the unit of infrastructure allocation. It did not finish the governance of competition inside the reserve.

The strongest case for the first draft

The fair contrary case begins with finitude, not institutional ambition. A terminal free pool cannot satisfy every demand indefinitely. Allocations arrive in uneven sizes, and honoring the largest documented requests under ordinary rules could leave later applicants—especially new LIRs—with no access at all. A smaller recurrent unit can distribute opportunity over time. Treating new entrants separately can preserve a pathway for networks that do not yet exist. A limited reserve can protect shared infrastructure and genuine unforeseen needs.

Pairing an IPv6 allocation with a transition plan can turn general encouragement into a practical dual-stack step.

On this view, the draft was a reversible allocation rule for an unallocated common stock. It neither claimed ownership of issued resources nor purported to regulate the whole Internet. Its limits were attached to new allocations from a pool whose administration necessarily required choices. The per-application unit allowed an existing LIR to return rather than imposing a lifetime one-block ban. The four-block ceiling gave a new LIR a bounded runway. The reserve would re-enter the pool if it remained unused after the rest had gone. Those features look less like confiscation than an attempt to preserve options under uncertainty.

That case deserves its full strength. It would be a straw man to say supporters wanted AFRINIC to punish IPv4 users, seize allocations or govern operators as a sovereign. The sealed record does not show those intentions or acts. It would be equally wrong to deny the practical need for some allocation sequence merely because all-network IPv4 did not vanish when the central pool depleted.

The response is that a legitimate objective does not complete an instrument. The first draft's numerical elements were more developed than its safeguards. It did not resolve whether /23 was being described as a floor or a ceiling clearly enough for every reader; McTim raised that ambiguity immediately. It did not define plan ratification, evidence of starting IPv6, reasons, time limits, review or appeal. It did not separate the reserve's purposes. It did not model the eight-month horizon or answer the possibility of more frequent requests. It offered a phase trigger whose exact-edge cases deserved clearer operational wording.

Narrow rationing can therefore be defensible only if discretion is observable, bounded and reviewable. Quantity rules should identify whether they are minima, maxima or both. Transition conditions should specify the smallest evidence relevant to access, not invite a broad assessment of business or architecture. Reserve use should be accounted for by purpose. Exceptions should be explained. The institution should say how an erroneous decision is reversed. Most importantly, every condition should terminate with the unallocated stock rather than migrate into control of already-issued holdings.

What the replies can and cannot prove

The first days of discussion are valuable because they stress-tested the words before later amendments blurred which concern belonged to which version. McTim's 7 January response questioned the /23 wording, AFRINIC's role in ratifying an applicant's IPv6 plan, the expected effect of eight rather than twelve months, the reserve's mixed identity and the draft's conditional dependence on the global policy. These are attributed objections from one participant. They are not findings, a vote or evidence that every reader agreed.

On 8 January, Mark Elkins opposed the eight-month horizon, suggested waiting until a smaller remainder before introducing special rules, raised the position of new or lightly resourced members, and asked about regional use and the reserve. His alternative belongs to him, not to the initial mechanism. It clarifies a timing choice: rationing early preserves more tail for future access but constrains present needs sooner; rationing later satisfies more ordinary demand but leaves less tail to distribute.

A further follow-up contrasted regional restrictions with market allocation. That contribution establishes that the market-versus-regional-rule question entered the discussion. It does not turn market allocation into the proposal, demonstrate market outcomes or establish consensus. The record contains no price evidence, transaction data or measured movement of resources.

By 12 January, the author discussed changed timing and utilization ideas. That message is useful only as a fence. It confirms that the conversation had moved beyond the 7 January text. The changed ideas must not be smuggled backwards into a reconstruction of the first mechanism.

Mailing-list replies can expose ambiguity with unusual clarity, but they have strict evidentiary limits. A critic's question shows that a phrase admitted a contested reading. It does not prove the mechanism failed. A proposed alternative shows another design was imaginable. It does not prove adoption. Silence from other participants proves neither agreement nor opposition. The archive authenticates the exchange, not the unstated motives or representative standing of its participants.

First-class evidence gaps

The source base is strongest at the center and thin around the edges. The first mailing-list post is an authenticated public record of the reproduced draft, and it is sufficient to establish the mechanism circulated on 7 January. The duplicate corroborates same-day circulation. Replies establish named participants' objections. Official later records keep chronology from leaking backwards. Current NRS and Heng Lu materials provide the institutional doctrine used to evaluate the mechanism. None of those roles should be swapped.

Several first-class gaps remain explicit. There is no sealed internal PDP-MG receipt record beyond the chair's statement that the proposal was received on 6 January. There is no sealed original proposal-site snapshot or standalone first-version document independent of the mailing-list reproduction. The post is the backbone because it contains the text, but independent archival redundancy for that first version is absent.

There is no sealed first-class demand dataset, depletion model, applicant distribution or quantified estimate of how much the /23 unit or eight-month horizon would extend the pool. There are no queue statistics, request-frequency estimates or analyst-cost measurements. Consequently, the draft's conservation rationale and the reply's frequency concern remain competing hypotheses.

There is no sealed first-class definition of AFRINIC's standard for ratifying an IPv6 plan, evidence showing that an LIR had begun using IPv6, review or appeal machinery, or consequences of disagreement beyond denial of the additional allocation described by the condition. One cannot infer a hidden standard. One also cannot infer that no standard could later have been supplied. At the instant of first circulation, the public text left it undefined.

There is no sealed first-class evidence identifying intended or actual beneficiaries beyond the applicant and infrastructure categories written into the draft. The sources do not prove discriminatory impact, depletion extension, applicant behavior, market prices, routing effects, operator costs or implementation. Nor do they establish consensus, representative mandate, title, sovereign authority or real-world effectiveness.

Finally, none of the current doctrine or context materials in the sealed set independently reproduces a 2009 record of the first-post mechanism. The NRS charter and current Heng Lu materials are first-class for the project's institutional principles; they are not retrospective evidence of the author's intent or the participants' beliefs. Current LARUS material concerns continuity and bounded coordinator authority, not the 2009 event. The BTW article marks a collision boundary around a broader later-pool story; it cannot supply this article with later economics or history.

Naming those gaps is not an admission that the analysis has failed. It is how the analysis avoids turning plausible mechanisms into invented outcomes. Absence of evidence in the sealed record means a proposition is unestablished here. It does not prove that the proposition never existed in another record.

Bookkeeping authority at the scarcity boundary

The first draft sat at the legitimate edge of a registry's function. Someone had to maintain unique records and decide how an unallocated common stock would be distributed. Quantity limits, eligibility rules, a trigger and a reserve can all be tools of technical coordination. Their legitimacy arises from their narrow service to uniqueness, accuracy, security and continuity—not from a claim that the coordinator owns the resource or rules the operators who use it.

AFRINIC is a private technical coordinator and bookkeeper. It is not a sovereign, legislature, regulator, police force, prosecutor, court, punisher, confiscator or owner of issued number resources. Administration of the remaining free pool does not create any of those powers. Proximity to valuable ledger entries does not create jurisdiction. A recorded allocation coordinates operational uniqueness; the record does not manufacture the running network or establish title by decree.

That boundary produces a precise reading of the proposal. A ceiling on a new allocation from an unallocated stock can be an administrative criterion. An IPv6 step attached to a later allocation can be assessed as a proposed eligibility condition. Neither entails a power to seize existing holdings, punish conduct, dictate all protocol choices or adjudicate private rights. The first draft did not claim such acts, and criticism should not inflate it into them.

Yet temporary mechanisms can seed durable institutional assumptions. If the ability to ration the tail is narrated as proof that the registry owns or governs all number resources, scarcity administration becomes a ladder to authority the coordination function cannot support. The Policy Mirror doctrine blocks that move: a rule may organize access to an unallocated pool while the pool exists, but it must not become permanent control over issued holdings. The ledger describes and coordinates; it does not create operational reality.

The reverse error is also serious. Saying a registry lacks sovereignty does not mean every allocation rule is meaningless. A final unallocated block is arithmetically finite. If all requests cannot be met, sequencing is unavoidable. Denying that fact would hide rather than limit discretion. The sound approach is to name the narrow power actually at issue, demand observable procedures around it, and refuse to let it escape its object.

This makes the first draft historically revealing even without importing later history. It captured the moment when scarcity changed the form of administrative choice. The proposed final /8 would no longer be merely the next block in an ordinary allocation process. It would become a rationing instrument: divided into small units, released differently to incumbents and entrants, linked to a technology-transition condition, planned over a shorter horizon and partially withheld for future contingencies and shared infrastructure.

Its durable lesson is not that the design was necessarily right or wrong. It is that scarcity rules should be evaluated at the point where arithmetic turns into judgment. The /23 can be counted. The four-block ceiling can be counted. The /16 can be accounted for. “Ratification” of a plan cannot be trusted on arithmetic alone. The quality of the instrument depends on whether that judgment is defined, explained, reviewable and confined to the pool it administers.

A narrow verdict on the first posting

As an initial proposal, the 7 January draft had a coherent purpose and an incomplete control surface. It correctly treated the terminal pool as a sequence of options rather than a single undifferentiated remainder. It recognized later entrants, distinguished applicant classes, paired transition support with remaining IPv4, reduced the release unit and preserved a reserve with an eventual return condition. Those are intelligible answers to the problem of lumpy demand against finite stock.

But the first text asked its readers to accept too much administrative judgment without specifying how that judgment would operate. The plan condition was the clearest example. The reserve's mixed purposes and the horizon's untested rationale added uncertainty. The trigger needed tighter edge-case language. The draft's invitation to discuss was therefore not a formality; it was necessary to turn a plausible rationing concept into a rule that could be audited.

The appropriate conclusion is bounded. The post did not settle the legitimacy of Soft Landing, prove its effectiveness or authorize later actions. It recorded a proposed switch in how AFRINIC would coordinate a future unallocated block. The strongest version of that switch was a temporary, reversible and transparent allocation mechanism. Its dangerous version would be a precedent for discretionary control detached from the free pool. The first draft contained ingredients for the former and ambiguities that could enable the latter, but the sealed record does not show which outcome followed.

Administrative depletion of the central free pool must not be confused with the disappearance of usable IPv4 or with registry ownership. Rationing an unallocated stock can be a sound coordination choice without becoming permanent authority over issued holdings. That is the line on which the first proposal should be judged—and the line the act of posting did not itself have the power to move.

Sources