Registries & Policy

APNIC 62 policy meeting: two proposals reach consensus, IPv4 delegation increase returns to the list

At APNIC 62 in Mumbai, prop-169 and prop-170 reached consensus, while prop-168, which would raise the maximum IPv4 delegation to a /22, was returned for more discussion.

BYOIP.info Editorial Change dated

What changed

The Policy SIG at APNIC 62 (Mumbai, September 2026) considered seven proposals. APNIC's write-up, published 25 September, gives these outcomes:

Proposal Topic Outcome
prop-169 Align IPv4 needs-assessment wording with current delegation practice Consensus
prop-170 Optional nibble-boundary-aligned IPv6 allocations when operationally justified Consensus
prop-168 Raise the maximum IPv4 delegation from a /23 to a /22, plus a reserved pool for new entrants using NAT64/DNS64 No consensus; returned to mailing list
prop-164 Allow IPv6 allocations smaller than a /32 (down to a /40) on nibble boundaries No consensus; returned to mailing list
prop-171 Operational accountability for abuse contacts in sub-allocated space No consensus; returned to mailing list
prop-165 A single IPv4 /24 for IPv6-only networks for transition services No consensus call (revised version arrived shortly before the meeting)
prop-172 A formal definition of Internet abuse involving IP addresses No consensus call (exploratory)

The two consensus proposals continue through APNIC's Policy Development Process. The other proposals will be discussed on the Policy SIG mailing list ahead of APRICOT 2027 / APNIC 63.

Why it matters for BYOIP teams

  • With prop-168 returned, the maximum from APNIC's remaining IPv4 pool stays at a /23 for now. Teams in the region planning to bring IPv4 to a cloud should continue to assume that larger blocks come from transfers or leasing.
  • prop-170, if implemented, would let applicants request IPv6 allocations aligned to nibble boundaries, which simplifies reverse DNS delegation and address planning for BYOIPv6 deployments.
  • prop-171 and prop-172 are early signals about abuse-contact expectations in sub-allocated space, which is relevant to leased address space.

What to check

  • The proposal pages for the exact text of prop-169 and prop-170.
  • The Policy SIG mailing list if you want to comment on prop-168 before APNIC 63.

Sources

  1. APNIC 62 Policy SIG reviews seven policy proposals, with two reaching consensus

    APNIC Blog · published 25 Sept 2026 · checked 30 Sept 2026

  2. prop-168 Increase to maximum IPv4 delegations

    APNIC · checked 30 Sept 2026

  3. prop-169 Aligning IPv4 LIR needs assessment with current IPv4 delegation policy

    APNIC · checked 30 Sept 2026

  4. prop-170 Nibble-boundary alignment for IPv6 allocations

    APNIC · checked 30 Sept 2026

Related resources

Topicsapnicpolicyipv4ipv6