Summary

  • Prop-169 would replace the fixed requirement to plan use of at least a /23 within a year with wording tied to the IPv4 delegation under assessment; it does not itself change eligibility or delegation limits.
  • APNIC records consensus at APNIC 62, but its public proposal overview still places Prop-169 under “Reached consensus”, not “In Implementation” or “Implemented”.

The mismatch is easy to see in one line of policy. APNIC-127 v015, Section 6.2.1, governs initial IPv4 delegations to Local Internet Registries. An applicant must already use a /24 upstream or show an immediate need for one, comply with the policies that apply to previously delegated space, and demonstrate a detailed plan to use at least a /23 within a year. The last requirement names a fixed planning size even where the delegation under review may be smaller.

Prop-169, authored by Saima Nisar, proposes to replace that fixed reference with wording tied to “the IPv4 delegation being assessed”. APNIC’s own explanation gives the practical example: if the request is for a /24, a plan for a /23 can look confusing. The proposal keeps the one-year planning horizon. It does not propose a larger delegation, a lower eligibility bar, or a different allocation ceiling. Nor does it amend transfer rules, the waiting list, routing, RPKI, WHOIS, RDAP or DNS operations.

That distinction matters because a needs test and a size limit answer different questions. A test asks whether the applicant can substantiate the request under the applicable criteria. A ceiling sets how much can be delegated. Changing the size named in a usage plan does not, by itself, change either the amount available or the applicant’s entitlement. The proposal is a wording alignment: make the plan refer to the delegation that staff are assessing rather than to a standing /23 figure.

The case for clarity does not require assuming that staff have been applying the rule mechanically or that applicants have been rejected because of it. APNIC’s Secretariat impact assessment says that internal assessment notes, guidance and applicant-facing material using the fixed /23 reference would need to be updated if the proposal proceeds. That is evidence of a documentation and operating-guidance dependency, not evidence of a particular past decision or a quantified processing burden.

The status trail is equally important. APNIC’s conference report records Prop-169 among proposals that reached consensus at the APNIC 62 Policy SIG Open Policy Meeting, held in September 2026. APNIC’s current proposal overview likewise lists it under “Reached consensus at APNIC 62”. The individual proposal page still displays an older “For discussion at APNIC 62 OPM” field. Read together, the updated overview and conference report establish the recorded meeting outcome; the stale field should not be mistaken for a fresh decision or for implementation.

Consensus at the OPM is not the same as a changed active policy. APNIC’s published Policy Development Process describes further stages: the SIG chair reports an accepted proposal at the APNIC Member Meeting, membership consensus is sought, a final mailing-list comment period follows, and maintained consensus is referred to the Executive Council for endorsement. The Secretariat implements after endorsement, usually at least three months later. APNIC’s overview currently separates proposals that reached consensus from those in implementation and those already implemented; Prop-169 remains in the first group in the reviewed record.

The operational hand-off is therefore the point to watch. If the text advances, the revised policy document, assessment notes and applicant guidance should describe the same test. An amended policy with stale forms can preserve the old ambiguity; a changed form before an effective policy can create a different one. APNIC’s sources identify the materials that may require alignment, but they do not say that the change has been implemented or specify a date when applicants should use new wording.

The reliable reading today is narrow: Section 6.2.1 still contains the active fixed-/23 wording in APNIC-127 v015; Prop-169 has recorded APNIC 62 consensus; and the public status page reviewed does not list it as implemented. The evidence does not establish how many applications are affected, whether any request has been delayed or refused because of the mismatch, or what the proposal would change in an individual assessment. Those questions need application-level records that are not in the public sources.

For LIRs, the sensible control is to prepare a needs case against the currently published policy and to distinguish the requested delegation from the plan requirement. For APNIC, the test of completion is not the conference label alone: it is whether the policy text, implementation announcement, assessment guidance and applicant-facing material converge on the same effective rule. A compact editorial change still has a real operational boundary, and version control is what makes it legible.

Sources