Summary
- IANA's free IPv4 pool was exhausted in February 2011, after each RIR received a final /8 under a globally coordinated policy. Regional communities had already begun designing final-pool and transfer rules.
- APNIC's prop-062 reached consensus in 2008, passed an eight-week final-comment period and was implemented in 2009. Later proposals continued to adjust final-pool distribution, showing that exhaustion was a transition in governance rather than the end of policy.
- Scarcity raised the economic value of allocations, the cost of delay and the advantage of incumbency. Those conditions made participation and conflicts more consequential; they did not justify treating meeting-room support, mailing-list quiet or implementation deadlines as consensus.
- Legitimate scarcity policy requires explicit distributional analysis, preserved objections, equal remote opportunity, implementation evidence, review triggers and a willingness to use temporary rules without pretending urgency resolved disagreement.
The counter changed the atmosphere before it reached zero
IPv4 exhaustion was forecast, graphed and debated for years before the central pool ended. It was not a surprise in the ordinary sense. Yet a known deadline can still transform institutional behaviour. As projected dates approached, every policy argument acquired a clock: act now or the remaining pool will be distributed under existing rules; agree now or transition will be disorderly; accept this compromise because the alternative is not another deliberative round but an irreversible allocation.
The pressure was real. Internet address blocks cannot be recalled easily after legitimate allocation. Networks needed continuity. Registries had to train staff and change systems before a threshold. Operators needed to plan. A policy accepted after the relevant pool was gone could become a historical essay rather than an operating rule.
But urgency has two meanings. Operational urgency concerns when a decision must take effect. Deliberative urgency is often used to argue that the decision deserves less scrutiny. The first can be demonstrated with inventory, implementation lead time and service consequences. The second is a political claim. It asks entities to lower the standard by which objections are addressed because the institution waited, the market accelerated or the pool declined.
The legitimacy of post-exhaustion governance depends on refusing that substitution. Scarcity can justify shorter intervals, interim measures and prioritised agendas when their necessity is public. It cannot turn rough consensus into a count of raised hands, define absent people as supporters or erase a material objection because resolution is inconvenient. The resources became scarcer; the public mandate did not become cheaper.
Exhaustion created a new political economy
When a registry could satisfy justified requests from a replenished pool, policy still allocated valuable resources, but many disputes concerned stewardship and efficient use within an expectation of continuing supply. Exhaustion changed the baseline. A grant to one organisation could mean a longer wait or no equivalent block for another. Transfer rules affected access to a market. Waiting lists, reserved pools and maximum delegation sizes determined who would receive the last fragments directly from collective inventory.
The IANA free pool ended on 3 February 2011, when the five RIRs each received a final /8. The NRO's IPv6 and exhaustion account describes that global transition and the regional role that followed. The event did not make IPv4 disappear. It shifted distribution from expanding administrative stock toward final pools, recovered space, waiting lists and transfers.
Scarcity also increased the value of historical holdings. Organisations with large earlier allocations possessed strategic flexibility that newcomers lacked. Policy arguments about need, transfer, reclamation and reservation therefore carried wealth effects even when framed as technical administration. Incumbents could finance sustained participation; prospective entrants might not know the forum existed until they needed addresses.
This did not corrupt every debate. It changed what adequate debate required. A technical objection about routing or registration remained important, but distributional questions—who gains access, who bears renumbering, who can wait, who can buy—could no longer be treated as secondary. Consensus after exhaustion had to test the social mechanism of scarcity as well as its operational feasibility.
The final /8 showed that anticipation was possible
APNIC's prop-062, Use of final /8, was submitted in July 2008, reached consensus at APNIC 26 in August, incorporated amendments, passed an eight-week call for final comments without substantial objection, received Executive Council endorsement in November and was implemented in February 2009. The process occurred before APNIC received its final IANA /8.
That history matters because it rebuts the idea that scarcity policy must always be made at the brink. The community could foresee depletion, debate a rationing model and leave time for final comment and implementation. The final /8 policy sought to preserve small delegations for new and existing account holders rather than continue ordinary depletion until nothing remained.
Later changes show that anticipatory policy was not perfect or permanent. APNIC reduced maximum access as conditions evolved and managed returned space under additional proposals. Its current exhaustion page records the sequence from the original /22 limit through later /23 arrangements and other pool changes. Governance continued because observed demand, inventory and market behaviour changed.
The lesson is not that one region found the universally correct formula. It is that an urgent threshold can be governed through staged public decisions. Forecasts allow an initial rule; implementation evidence allows adjustment. The existence of a deadline should make early deliberation a duty, not make late deliberation a formality.
Scarcity does not define the affected community
RIR policy processes are generally open beyond formal membership. The NRO describes regional policy development as open to anyone interested, with proposals and comments considered through consensus. This matters after exhaustion because the people most affected by future access may not yet be members. A start-up, municipal network or institution planning connectivity cannot vote with an existing allocation.
If scarcity debate is dominated by current holders, the constituency becomes circular: those who received resources decide how the rest are distributed. Existing members have legitimate operational knowledge and contractual stakes, but membership cannot substitute for the wider Internet community when policy determines entry.
Meeting participation can intensify this bias. Organisations with travel budgets and experienced policy staff can follow repeated versions. A potential entrant may encounter only the final call. Remote access and mailing lists help, but they do not equalise time, language, confidence or familiarity with prefix notation and registry history.
Consensus assessment should therefore ask whose absence is predictable. Were prospective entrants, small operators, public-interest networks and regions with weaker representation specifically informed? Were summaries understandable without years of archive knowledge? Was data presented by applicant class? Openness of the door is necessary, but high-stakes scarcity governance must also examine who could realistically reach it.
A raised hand became more valuable
RIR processes do not ordinarily treat a room poll as a binding vote. Chairs use expressions of support, objection and discussion to assess rough consensus. Under scarcity, however, visible support can acquire a false precision. A slide showing many green cards or online approvals looks decisive when the issue is urgent, even though the sample is self-selected and organisationally concentrated.
The APNIC PDP defines consensus as general agreement observed by chairs and requires attention to meeting and mailing-list participation. The LACNIC PDP states that consensus is not a count of yeses, noes or abstentions and focuses on whether critical technical objections have been addressed. These safeguards become more, not less, important when a policy distributes a dwindling pool.
A poll can reveal the room's state. It cannot establish that every support carries equal independence, that absent stakeholders agree or that a strong objection was answered. Employers may send several staff. Entities may approve direction while disagreeing with exact text. Some will remain silent because a chair's framing suggests closure.
The consensus announcement should explain reasons. Which objections were raised? What changes answered them? Which concerns were judged out of scope or limited public evidence, and why? A deadline can explain why chairs decide at a particular time. It cannot replace the explanation for the decision.
Silence became easier to misread
Final-comment periods often close without substantial objections. That can be meaningful evidence that a proposal's consensus was maintained. It is not automatic proof that the wider community affirmatively accepted every consequence. After long scarcity debates, silence may reflect exhaustion in both senses: the pool is depleted and entities are depleted too.
The standard should distinguish a maintained consensus from a newly manufactured one. If a proposal received broad, reasoned discussion and a final version resolves known objections, a quiet last call supports closure. If material text changed late, the absence of immediate response is weaker. If the earlier debate was narrow, final-call silence cannot supply breadth retroactively.
Chairs should state what changed and whether it affects the distributional bargain. A smaller maximum delegation, new eligibility condition, altered queue priority or transfer restriction is not editorial merely because the deadline is close. Entities need enough time to model its effect.
The archive should preserve notices and direct responses, but also the participation history. A future reviewer needs to know whether silence followed careful resolution or a rapid revision. Scarcity decisions are often irreversible at the individual allocation level; the record should be strong enough to support later legitimacy even when blocks cannot be returned.
“Something must be done” does not select the policy
Near exhaustion, most entities may agree that existing rules cannot continue unchanged. That is consensus on the problem, not necessarily on a remedy. Rationing, reservation, waiting lists, needs tests, auctions, transfers and randomised allocation distribute scarcity differently. Urgency can collapse these choices into support for whichever text is ready.
A proposal should separate the necessity decision from the design decision. The community can first agree on the risk and deadline. It can then compare mechanisms against explicit criteria: continuity, access for newcomers, resistance to gaming, administrative cost, route aggregation, legal compatibility and reviewability.
If time does not permit a fully settled permanent design, an interim rule may be more honest than declaring deep consensus around a contested architecture. The interim measure should minimise irreversible transfers, state a narrow purpose and carry a review date. Its temporary character is not weakness; it accurately represents the mandate.
This is especially important because scarcity creates path dependence. The first queue design shapes applicant behaviour. The first transfer rule creates businesses and expectations. A hurried “temporary” choice without review can become difficult to reverse once organisations invest around it.
Scarcity objections are not merely technical
Some consensus traditions emphasise technical objections, and technical quality remains central to number-resource policy. Yet scarcity choices also implicate fairness, competition, public access and regional development. An objection that a queue favours organisations able to prepare documents quickly may not describe a routing failure, but it can identify a serious defect in the distribution mechanism.
The LACNIC language about critical technical objections should be read alongside the actual policy purpose: validated rules that the registry will apply across its region. “Technical” should not become a gate that excludes evidence about predictable effects. A policy can be technically implementable and institutionally illegitimate.
Objections should be evaluated by evidence, relevance and remediability. A claim that transfers encourage hoarding can be tested with market and registration data. A concern that a minimum block is too small for practical transition can be tested operationally. A claim that newcomers deserve equal access involves normative judgment, but the community must confront it rather than dismiss it as subjective.
Chairs do not need to make every value commensurable. They need to show that material concerns were understood, answered or openly balanced. Rough consensus allows some entities to remain unconvinced. It does not allow the process to define their entire category of concern out of existence.
The staff forecast can become a scarcity constitution
Inventory data, burn rates and implementation estimates shape what options appear possible. Registry staff are often the only actors with complete operational information. Their analysis is indispensable, but assumptions can narrow debate. A forecast based on recent demand, one allocation size or one recovery rate can make a policy seem inevitable.
Impact assessments should publish ranges and scenarios. How does the pool behave under different delegation caps, eligibility rates, recovery assumptions and applicant responses? What can be known, and what depends on behaviour after announcement? How much lead time is a hard system constraint, and how much reflects scheduling preference?
Data should be updated when debate extends. A six-month-old projection can be materially stale near depletion. Versions should remain archived so entities can understand why an earlier choice looked rational. If confidential case information limits disclosure, aggregated methodology and uncertainty can still be public.
Staff should not participate as supporters or opponents where the process excludes secretariat votes from consensus. They should explain consequences and identify unimplementable text. Chairs then evaluate community arguments in light of that evidence. This separation helps prevent the inventory owner from becoming the sole author of scarcity policy.
Incumbency changed the conflict landscape
Before exhaustion, a large holder and a prospective entrant could both argue about stewardship. After exhaustion, their material positions diverged more sharply. Existing holders might benefit from transfer liquidity or restrictive new issuance. New entrants might favour preserved small blocks. Brokers, consultants and large networks acquired different interests in verification and market design.
Disclosure should therefore be routine. Entities in decisive roles should state relevant employment and resource-market interests. The point is not to discount their expertise. It lets the community interpret claims about feasibility, fraud and need against an understandable position.
Chairs and advisory bodies require stronger controls because they convert discussion into institutional action. A chair employed by a materially affected organisation can still facilitate, but should disclose and hand specific advocacy to another entity. A person who authored a proposal should not be the sole judge of whether objections to it were resolved.
Scarcity also makes concentration visible over time. Registries should publish aggregate allocation, transfer and waiting-list outcomes so the community can see whether a policy favoured certain organisation types. Without outcome data, conflict declarations describe potential bias while the actual distribution remains opaque.
Delay has winners too
Urgency rhetoric often assumes adoption is the active choice and delay is neutral. Under depletion, delay applies the existing rule for longer. That can benefit applicants already in the queue, holders who prefer a shrinking free pool, or actors positioned for the transfer market. Opposition can therefore have distributional effects even when it asks only for more discussion.
This does not make delay objections illegitimate. A flawed scarcity rule can cause irreversible harm. It means chairs should analyse the status quo as an option with beneficiaries and costs. The impact assessment should show what is expected to happen during an extension.
Where delay itself would defeat the policy objective, a narrow hold can preserve options: reserve a defined portion, freeze one category of allocation or adopt a reversible queue rule while discussion continues. Such measures need authority and safeguards. They should not be used to enact the contested substance through an “administrative” step.
Making delay visible improves debate. Entities can compare the risks of imperfect action with imperfect continuity rather than accusing one side of obstruction and the other of panic.
Exhaustion did not end stewardship
The phrase “run out” can imply the registry no longer has relevant policy choices. In practice, recovered address space, waiting lists, reserved blocks, transfers, registration accuracy and routing security remain governed. ARIN reports depletion of its free pool in September 2015 yet continues processing requests under specific reserved and waiting-list policies. RIPE NCC, LACNIC, APNIC and AFRINIC likewise operate distinct post-exhaustion arrangements.
This continuing authority means pre-exhaustion consensus cannot be treated as a permanent settlement. A final-pool rule designed for transition may govern for decades. Market behaviour, IPv6 deployment, fraud techniques and access needs change. Policy must remain reviewable even when the original allocation cannot be reversed.
Post-implementation review should ask whether the rule achieved its stated purpose, not only whether staff followed it. Did small allocations support transition? Did waiting times become arbitrary? Did transfers improve access or concentrate holdings? Did verification burdens exclude legitimate applicants? Did reserved pools remain aligned with public need?
Scarcity increases the value of empirical revision. A community that cannot create more IPv4 space can still improve how rights, records and procedures are managed.
Global coordination does not erase regional consensus
The final allocation of five /8 blocks arose through global coordination. Current global policies govern how PTI issues number resources to RIRs, while regional communities determine distribution within their service regions. A global proposal generally requires consideration across all five RIR processes.
The approaching common deadline encouraged harmonisation, but regions faced different demand, membership, market and development conditions. Equal final IANA blocks did not mean equal regional scarcity. A rule appropriate in one region could produce different access elsewhere.
Global coordination should therefore define the inter-registry mechanism without treating regional deliberation as ratification theatre. If one region raises a substantive objection, the answer is not that four others already agreed. The global process must resolve text across all required communities or acknowledge failure.
This principle protects the legitimacy of coordination. A globally urgent policy is strongest when each regional acceptance is real. Weakening one region's consensus standard to meet a central date would create a nominally uniform rule with uneven authority.
Temporary policy needs a real clock
Interim measures are often the appropriate response to uncertain scarcity, but temporary language is meaningless without a trigger. A review “later” will lose priority once systems and markets adapt. A sunset can be useful, yet automatic expiry may itself threaten continuity if no replacement is ready.
The better design selects among sunset, renewal vote, mandatory review and staged conversion according to risk. A narrow reservation might expire unless renewed. A core allocation rule may continue provisionally while a scheduled review determines amendment, avoiding service interruption. In either case, the institution must publish evidence before the date.
The review body should not be identical to the original authors and implementers. They provide crucial context, but independent entities should test whether predicted harms and benefits occurred. The community should receive enough time to act before an automatic consequence.
Temporary policy should also limit reliance interests where possible. If entities know the rule may change, contracts and systems can account for that. False permanence created by silence is harder to unwind.
Consensus summaries should become reasoned decisions
A declaration that consensus exists is not enough for a high-stakes scarcity rule. The summary should identify the problem, options considered, affected groups, material objections, changes made, remaining disagreement and why chairs concluded that objections were addressed even if not accommodated.
It should state evidence limits. If participation was geographically narrow or data uncertain, the record should say so and establish review. Confidence can be sufficient for action without pretending completeness. This candour is especially important when the pool's decline makes waiting costly.
The summary should link the exact policy version, impact analysis and implementation assumptions. Later disputes often concern whether staff applied what the community accepted. A reasoned decision creates an interpretable mandate.
Appeals should review process and consensus judgment without becoming a second policy forum. They need the summary to test whether chairs ignored a material objection, relied on a poll as a vote or treated a deadline as proof. Good reasons protect chairs from retrospective claims as much as they protect dissenters.
Participation support is part of the scarcity mechanism
A rule allocating the last blocks is only as inclusive as the process that produced it. Translation, remote participation, accessible data and sufficient notice are not conference amenities; they affect who can influence distribution.
Regions span many languages and time zones. A meeting consensus call at a difficult hour may capture only those able to stay connected. Mailing lists favour confident written English and employers willing to fund attention. Scarcity intensifies the consequence of these familiar inequalities.
Policy pages should provide concise multilingual summaries while preserving an authoritative text. Remote entities need equal access to the queue, microphones and chair questions. Asynchronous objections should be incorporated into the consensus explanation, not appended after the room has effectively decided.
Registries should publish participation diagnostics and seek missing perspectives before final decisions. Outreach must not become mobilisation for a preferred answer. It should explain the choice, deadline and ways to contribute in neutral terms.
A legitimacy stress test for post-exhaustion rules
Every scarcity proposal should answer a common set of questions. What finite inventory or administrative capacity is being allocated? Which holders and prospective users are affected? What happens under current policy during delay? Which outcomes are irreversible? What market incentives will the rule create?
It should identify evidence and uncertainty, not only a preferred forecast. It should compare plausible alternatives and show why less restrictive options fail. It should disclose relevant interests among authors, chairs and reviewers. Material objections should be recorded in their strongest form.
The process should provide meaningful asynchronous participation and avoid using room polls as votes. The consensus declaration should give reasons. Implementation should match the exact version and publish outcome data. Review should occur on a date tied to evidence, with a route for appeal or correction.
If urgency shortens any step, the decision should state the authority, necessity, compensating safeguard and restoration date. Scarcity can change procedure only transparently and proportionately. It cannot become a standing exception.
Transfers moved scarcity outside the allocation queue
Once free-pool access narrowed, organisations increasingly looked to transfers. Transfer policy did not abolish scarcity; it changed the institution through which scarcity was expressed. Price, brokerage, due diligence, title, registration and cross-regional compatibility became part of access. A registry still governed who could transfer, what need had to be shown, how records changed and which counterpart regions were compatible.
This shift complicated consensus. Current holders could describe transfers as a means of moving underused space to networks that valued it. Critics could point to speculation, concentration, unequal purchasing power or laundering of disputed control. Both positions contained technical and economic claims. A chair could not resolve them by asking only whether the database could process a transaction.
Transfer proposals therefore required evidence about market structure and the limits of registry knowledge. Public price data was often incomplete; private contracts concealed terms; organisations could restructure transactions around policy. Uncertainty was not a reason to abandon policy, but it should have shaped review. A rule adopted as a bridge under uncertain market behaviour needed outcome reporting and a route for correction.
The community also had to avoid a false comparison between “market” and “policy.” A transfer market exists through policy recognition, registration services and enforceable organisational relationships. Choosing eligibility, disclosure and verification is governance. After exhaustion, consensus had to address those choices openly rather than treat price as a neutral substitute for allocation judgment.
Fraud controls can become entry controls
Greater value creates incentives for forged authority, hijacked accounts, shell organisations and misleading need claims. Registries have legitimate reasons to strengthen validation. Yet every additional document, notarisation, corporate record or waiting period can exclude legitimate applicants from jurisdictions with weaker digital records or slower administration.
Scarcity debate often presents fraud prevention as a technical necessity beyond policy disagreement. The threat is real, but the particular control remains a choice. Entities should ask which risk it detects, error rates, available alternatives, privacy cost and appeal. A requirement that looks modest to a large operator with counsel may be prohibitive to a small network.
Impact analysis should model false positives as well as prevented fraud. Manual alternatives and proportionate review can preserve access. High-risk transactions may justify stronger checks than a small transitional allocation. Public criteria reduce the advantage of insiders who know which evidence staff will accept.
Consensus does not require publishing security-sensitive detection methods. It does require the community to authorise the burden and oversight structure. Scarcity cannot make every control self-justifying merely because bad actors seek valuable resources.
IPv6 did not make IPv4 distribution apolitical
The long-term technical answer to IPv4 limitation is IPv6 deployment. That truth can become a rhetorical shortcut: applicants needing IPv4 should deploy IPv6, so remaining IPv4 rules matter less. In operational reality, many networks require both because users, services and counterpart systems remain unevenly reachable.
A scarcity policy can encourage transition by reserving small amounts for IPv6 deployment, limiting repeated access or linking support to dual-stack plans. It should not use the existence of IPv6 to dismiss evidence about immediate connectivity, public services or entry barriers. The burden of incomplete global transition does not fall equally.
Consensus discussions need to state the policy objective precisely. Is a small block intended for translation infrastructure, general growth, emergency continuity or equitable entry? Different purposes imply different sizes and evidence. A broad appeal to transition can hide conflicting goals.
Outcome review should examine whether recipients actually obtained the intended transition benefit, while avoiding intrusive monitoring unrelated to the grant. If the mechanism does not work, scarcity is not a reason to preserve it. The community can change design while continuing to advocate IPv6.
Memory becomes part of fairness
By the time a final-pool rule is revised, entities may remember the original compromise differently. One group recalls a temporary rationing measure; another recalls a durable entitlement for newcomers. Staff may know the operational reason for a cap, while later members see only policy text. Scarcity magnifies these differences because changing the rule shifts valuable access.
Proposal archives should preserve the reasons, objections, implementation dates and outcome evidence for each stage. A later consensus call can then distinguish reliance on explicit assurances from reliance on institutional habit. Historical practice matters, but it should not acquire constitutional status merely through age.
New entities need readable histories. Otherwise incumbents who attended the original meetings possess an interpretive advantage. A public lineage from final /8 policy to later reductions, returned-pool rules, waiting lists and transfer mechanisms makes the evolution contestable by everyone.
Institutional memory is therefore not an ornamental archive. It is part of equal participation in a policy area where early decisions still distribute present value.
Reserved pools require an exit rule of their own
Communities often preserve small blocks for defined purposes such as exchange points, critical infrastructure or transitional connectivity. Reservation can protect public value from general depletion, but it also removes inventory from applicants whose needs are immediate. The category, size and release condition therefore belong in the consensus bargain.
A reserve without periodic review can outlive the assumptions that created it. Demand may be lower than forecast, eligibility too narrow or an operational alternative may emerge. Conversely, a successful reserve may appear underused precisely because it prevents a catastrophic gap that occurs rarely. Simple utilisation rates cannot settle the question.
The proposal should state the harm being insured against, expected demand, evidence threshold, queue rule and what happens to unused space. Release should not occur through an unannounced staff judgment when scarcity intensifies. Nor should preservation become automatic because the original authors described the purpose as critical.
Review should include rejected applicants and near misses, not only recipients. Those cases show whether definitions are too strict or whether organisations are redesigning requests to fit the category. Aggregate reporting protects confidentiality while making distribution visible.
Reserved pools demonstrate why exhaustion did not lower the consensus standard. The community is choosing between present access and future resilience under uncertainty. A poll can indicate preference, but only reasoned treatment of both risks creates an accountable mandate.
Fees are part of the allocation environment
Membership and service fees may not be written inside an address policy, yet they affect who can use it. After exhaustion, a small allocation accompanied by recurring cost, transfer fees or verification expense may be inaccessible to precisely the new entrant the rule claims to protect.
Policy impact analysis should identify these adjacent costs and who controls them. The policy community need not set every fee, but it should not assess fairness in a fictional zero-cost environment. If a Board later changes fees materially, the registry should examine whether the policy's distributional assumptions still hold.
This boundary preserves institutional roles while preventing economic reality from disappearing between them. Scarcity is governed through the combined effect of policy, service design and price.
Fee review should include timing as well as amount. An annual charge, upfront transfer expense and refundable deposit affect liquidity differently. Public-interest and small-network participation may depend on instalments or waivers administered under transparent criteria. These are not reasons for chairs to decide budgets through a consensus call; they are reasons to record when the policy's claimed access benefit depends on a separate financial decision and to reopen evidence if that dependency changes.
The standard protects action, not only dissent
Strong consensus rules are sometimes portrayed as obstacles to timely policy. In fact, a reasoned and inclusive process protects implementation. Applicants are more likely to accept unequal outcomes when the distribution rule and objections are visible. Staff can defend difficult decisions by pointing to a clear mandate. Courts, boards and future communities can distinguish deliberate policy from administrative improvisation.
Weak consensus creates operational cost. Disputes move into appeals, board pressure, litigation or non-compliance. Entities reopen settled issues because no reasoned record shows what was settled. Urgent adoption can therefore delay durable legitimacy.
The standard does not require unanimity or endless debate. Chairs may conclude that an objection has been answered, that evidence is limited public evidence or that a entity seeks to relitigate a resolved point. They should say why. Rough consensus is capable of decision; its discipline is attention to reasons rather than arithmetic.
Scarcity makes this capacity essential. An institution cannot satisfy everyone with a finite pool. It must instead show that the rule was made through a process in which losses were recognised, arguments were tested and authority remained accountable.
Conclusion: urgency is a condition, not a constituency
IPv4 exhaustion raised the stakes of RIR policy because address space acquired greater scarcity value, existing holdings mattered more and delay distributed resources under the status quo. It also made implementation deadlines real. None of those facts spoke with a community voice.
Urgency could justify early planning, focused agendas, refreshed forecasts, interim safeguards and explicit review. It could not vote, answer an objection or represent absent entrants. The consensus standard remained what open, bottom-up governance requires: material issues heard and addressed, reasons recorded, and no substitution of counts or silence for judgment.
The history of final /8 policies shows that communities could anticipate exhaustion and continue revising policy afterward. That is the durable lesson. Scarcity is not a single emergency that ends when a counter reaches zero. It is a long governance condition involving waiting lists, transfers, recovered space, legacy advantage and access for networks not yet formed.
A lower standard would have been most dangerous precisely when the resources were most valuable. The correct response was the opposite: richer evidence, clearer conflicts, wider participation and stronger review. Exhaustion changed what policy had to decide. It did not change who had to authorise the decision or what honest consensus meant.