APNIC 61 debates IPv6 delegation rules and IPv4 limits

APNIC’s latest policy meeting, held alongside APRICOT 2026 in June, brought two contentious proposals to the floor. Neither prop-164 nor prop-168 secured consensus, but the discussions clarified the operational and strategic divides shaping Internet number resource policy in the Asia-Pacific region. The outcomes underscore how technical proposals often hinge on regional network diversity and long-term adoption goals rather than purely technical merits alone.

Policy proposals in focus

Prop-164, co-authored by Christopher Hawker and Luke Thompson, proposed allowing IPv6 allocations longer than a /32 with mandatory nibble boundary alignment. The rationale centered on operational convenience and routing table efficiency, particularly for large networks managing prefix hierarchies. However, the proposal did not advance to a consensus call at APNIC 61 due to insufficient feedback during prior mailing list discussions and at APNIC 60. During the Open Policy Meeting (OPM), participants weighed the benefits of simplified prefix management against potential routing table growth, reflecting the region’s varied network environments.

Prop-168 sought to increase the maximum IPv4 delegation size, framing it as a stopgap measure while IPv6 adoption accelerates. The proposal faced stronger resistance, with debate centering on whether further IPv4 policy adjustments would delay or distract from IPv6 deployment. While no consensus was reached, the discussion mapped out the core disagreements, setting a clearer agenda for APNIC 62 in Mumbai later this year.

Operational and regional challenges

The debates at APNIC 61 highlighted how regional diversity complicates policy development. The Asia-Pacific region encompasses networks of vastly different scales, from small island providers to hyperscale operators. Proposals that fail to account for this spectrum often encounter resistance, even if they address a recognized need. Hawker noted that anticipating objections during drafting—rather than relying on the OPM to surface them—can streamline the process. This approach requires authors to engage with stakeholders early, test assumptions, and revise proposals before formal discussion.

The Policy 101 session at APNIC 61 reinforced the importance of presentation and context. A technically sound proposal can stall if it does not address operational concerns or clearly link its rationale to demonstrated community needs. The session’s role-play exercise illustrated how the Policy Development Process (PDP) depends on effective communication, not just technical rigor. For new participants, understanding these nuances is as critical as mastering the procedural steps.

Next steps and broader implications

Following APNIC 61, Hawker and other proposal authors plan to revise their submissions based on feedback from the OPM and mailing list. For prop-164, this may involve clarifying the trade-offs between nibble boundary alignment and routing table growth. For prop-168, the focus will likely shift to addressing concerns about IPv4’s role in transition strategies. Both proposals will be revisited at APNIC 62, where the community will assess whether revisions have sufficiently addressed the operational and strategic concerns raised.

The discussions also underscored the role of sustained participation in shaping policy outcomes. Hawker, an APNIC 2025 Policy Fellow, observed that his engagement has evolved from learning procedures to actively refining proposals based on community feedback. This shift reflects a broader trend in the PDP, where long-term contributors increasingly prioritize analytical rigor and stakeholder engagement over procedural compliance alone.

For network operators and policy professionals, the outcomes of APNIC 61 serve as a reminder that consensus is not a formality. It requires balancing technical objectives with the practical realities of diverse network environments. The proposals’ progress—or lack thereof—will influence how the region manages IP resources in the coming years, particularly as IPv6 adoption continues to accelerate.