Summary

  • The Recommended Draft Policy would add within the ARIN service area to NRPM 4.10. The Advisory Council calls it a codification of current practice; the comments anticipate a prospective boundary for allocations issued before implementation. No checked source reports last-call completion, Board adoption or implementation.
  • Codification changes public proof even if staff review does not change. Before an amendment, the chain may require the NRPM, a contemporaneous procedure and staff interpretation. Afterwards, the condition would appear in policy. The two cohorts can have similar outcomes but different documentary authority.
  • An earlier issuance date proves timing, not unrestricted use, permanent exemption or permission to use a 4.10 allocation anywhere. Later wording likewise cannot be projected backwards. The record must bind each decision to its policy, procedure, transition rule, IPv6-deployment justification and later reviews.
  • Routing visibility is separate evidence. An out-of-region announcement cannot alone establish purpose, actual use, anycast design, continuing justification or compliance. Route observations, use findings and applicability should remain distinct, with only privacy-safe cohort aggregates made public.

The prospective boundary is already visible

The prospective boundary sits on one official policy page. ARIN-2025-8, Reserve 4.10 Space for In-Region Use, is an Under Discussion Recommended Draft Policy whose current text is dated 14 July 2025. It would replace the present sentence saying that an IPv4 allocation is set aside and dedicated to facilitate IPv6 deployment with the same sentence ending within the ARIN service area.

The page also supplies the boundary’s two sides. The Advisory Council says the amendment would codify existing practice, and the timetable says Immediate; the comments say staff has no intention to extend the restriction to 4.10 allocations issued before implementation. Its record notes earlier ambiguity concerns, later support and no proposed alternative wording. Staff may have applied an in-region understanding under the pool’s existing purpose while seeking clearer future text. But without a versioned decision record, later readers can mistake administrative continuity for textual continuity or a transition for a new entitlement.

The current NRPM demonstrates why the distinction matters. Version 2025.1, effective 3 March 2026, still lacks the service-area phrase. Section 4.10 reserves a contiguous /10; requires justification tied to immediate IPv6 deployment; gives dual-stack DNS, NAT-PT and NAT464 as examples; leaves room for staff discretion; and provides for a /24. The proposed geographical wording is therefore not yet part of the checked effective text. The problem statement says current 4.10 text has no out-of-region restriction beyond Section 9, while staff has interpreted out-of-region use as contrary to the pool’s intended purpose.

The history gives 14 July 2025 for the proposal, 26 August 2025 for Draft Policy status and 27 April 2026 for Recommended Draft Policy status. The 12 November 2025 staff review says current implementation requires use within the ARIN region, the draft would not alter review practice, and implementation is feasible. It lists no registry-operations impact or material legal issue, and estimates three months for training and document and procedure updates. These are readiness requirements, not completed implementation.

Three dates can govern one resource record

Public policy, staff interpretation and effective policy can carry different dates. The issuance-date NRPM shows what the public rule said; a contemporaneous procedure records how Registration Services applied it; an amendment’s effective date identifies when new wording governs; and a later review date identifies the evidence and rule used then. A later review may examine present facts without rewriting the original decision. Collapsing these dates into one current-policy field begins cohort drift.

Codification matters even when staff reaches the same answer. Before it, a reviewer may need the purpose sentence, guidance, procedure and decision record to explain an in-region finding. Afterwards, the requirement would be visible in policy, subject to the final scope, definitions and transition language. Public text strengthens notice and makes later departures easier to identify; that benefit disappears if the new wording is treated as though it always existed.

Existing conditions do not answer the geographical question

Section 4.10 already has a narrow purpose and a constrained allocation path. The public IPv4 request guide adds operational conditions concerning a six-month need, continuing justification, utilisation, alternative resources and possible renumbering. It also explains that reserved-pool resources are not eligible for specified-recipient transfer and that receiving one does not remove a waiting-list request.

Those conditions define the reserved pool but do not settle a later service-area sentence. A subsequent question about continued justification, use or routing must identify its governing rule. Otherwise an older /24 may be judged by wording not yet effective, or a continuing obligation may be dismissed solely because issuance came first.

The comments support only expected transition treatment at the proposal stage. They do not create a legal right, permanent guarantee or permission for every earlier holder to use a 4.10 allocation without geographical constraint, and they do not prove retroactive enforcement. They make a durable cohort record necessary.

Two cohorts, but no invented rights

If the proposal becomes effective with the described treatment, ARIN would have at least two documentary cohorts. One would contain 4.10 allocations issued before the effective date. The other would contain allocations issued under NRPM text that expressly includes within the ARIN service area. The cohorts would differ in the public wording attached to the original decision.

That distinction is not a binary of restricted and unrestricted. Earlier allocations may have been assessed under an in-region interpretation and may remain subject to their original purpose, representations, continuing justification or later rules validly applied to present review. The later cohort would have explicit text, but its meaning would still depend on adopted wording, definitions, guidance and decisions.

The safe unit of analysis is therefore not the resource’s age alone. It is the allocation-applicability record: what policy applied, what procedure interpreted it, what facts were found, what transition rule governed, and what later review did or did not decide. A cohort label should summarise that chain, not replace it.

The record protects both cohorts: earlier holders are not silently moved into later text, while future applicants are not told that an old allocation proves broader permission. Registration Services can assess facts under the applicable framework, and reviewers can distinguish changed evidence from changed policy.

Announcement, use and justification are separate findings

The ARIN 55 Day 1 transcript records staff saying that then-current practice rejected 4.4 and 4.10 requests for use outside the region. Participants separately discussed in-region justification, in-region use and out-of-region announcement or anycast. Those exchanges show why precise categories are necessary. They do not establish adopted policy, consensus or a final definition of within the ARIN service area.

A route observed abroad is a weak substitute for the decision record. It may show visibility from particular vantage points and times, but not the original IPv6-deployment justification, relevant infrastructure or users, staff’s purpose finding, anycast design, the difference between announcement and use, or the issuance rule. It may be evidence; it is not a verdict.

The reverse inference also fails. An in-region announcement does not prove all purpose or use is in-region; an out-of-region path does not prove the request was for out-of-region use. Review should state evidence scope, observation period and classification, then connect them to policy and procedure rather than treating BGP visibility as conclusive.

The practical harm is cohort drift

Cohort drift occurs when the date boundary is remembered but the governing record is not. It has two forms.

In backward drift, a later reviewer treats the explicit sentence as though it governed every 4.10 allocation from the beginning. The original NRPM, procedure and transition statement vanish, so even a conclusion matching earlier practice rests on the wrong stated basis.

In forward drift, an earlier issuance date is treated as permanent exemption or unrestricted use. That confuses absent later wording with affirmative permission and may ignore the purpose, representations, procedure or continuing conditions that governed the allocation.

Both errors damage accountability. The first invents retroactive textual authority; the second invents a right from silence. Both can be prevented by preserving the original decision basis and recording later reviews as separate events rather than editing history into the current rule.

A protected allocation-applicability receipt

ARIN need not publish protected request material to preserve this chain. It can maintain a detailed internal receipt for each decision, expose it through appropriate notice and review channels, and publish only privacy-safe aggregates. The receipt should be append-only or versioned so that corrections remain visible rather than replacing the earlier record without trace.

Receipt field What the protected record should establish Privacy-safe public expression
Decision and resource ID A stable link between the request, decision and issued /24 Aggregate count by cohort and decision period
Request and issuance dates When evidence was submitted, assessed and the allocation issued Counts by month or quarter without holder identity
NRPM 4.10 version The exact policy version governing the original decision Cohort totals by NRPM version
Procedure or interpretation version The staff procedure, guidance or interpretation used at the time Version identifier and effective range
Original IPv6-deployment justification The purpose represented by the applicant and accepted for review Categorical, non-identifying purpose totals where safe
Evidence scope and observation period What evidence was considered and over what period Public methodology and aggregate coverage
In-region purpose or use finding The factual finding made under the applicable framework Counts of findings by defined category
Out-of-region use or announcement classification A separate classification that does not collapse routing, use and purpose Aggregate categories with definitions and caveats
Effective policy and transition rule The later policy version, effective date and treatment of earlier allocations Public transition text and cohort mapping
Cohort and basis Why the allocation belongs in a pre-effective, post-effective or reviewed cohort Aggregate cohort totals and basis codes
Continued-justification review Any later review, its trigger, evidence and applicable rule Number, status and broad outcome of reviews
Decision authority and reason Who had authority and the reasoned basis for the outcome Role-level authority and reason codes
Notice and response What notice was given and whether the holder could respond Aggregate notice and response statistics
Review route Available reconsideration, escalation or review mechanism Public route and aggregate use
Correction history Every material correction, with date, authorising role and reason Count and type of corrections by cohort

The table separates historical applicability from present observation. Later route review can be attached without changing the issuance policy; correction can amend classification without erasing history; transition can be recorded without becoming permanent entitlement. Public aggregates may show allocations by NRPM version, later reviews, evidence categories, corrections and review use, but should not expose identities, designs or protected justification. Their purpose is consistency testing, not public reconstruction of case files.

What the frozen record permits ARIN to say

The checked evidence permits a limited conclusion. ARIN-2025-8 would make an in-region condition explicit; staff says it matches current implementation and would not alter review practice; the comments anticipate prospective treatment. NRPM 2025.1 lacks the phrase, and no checked source shows last-call completion, Board adoption or implementation.

The evidence does not prove that any earlier holder has unrestricted use; that a later rule has been enforced retroactively; that a request has been denied; that an allocation has been revoked; or that a disputed transfer, lease, route event or holder case exists. It also does not let routing visibility settle original justification, current purpose or compliance.

The problem is record design: identify when public text changes, preserve earlier decision bases, state transition treatment and keep later evidence separate. Otherwise codification can rewrite the past in either direction.

Sources