Summary

  • APNIC 62 recorded consensus on prop-169 and prop-170; APNIC’s current proposal overview repeats that result.
  • Both live detail pages still say “For discussion at APNIC 62 OPM,” and neither proposal appears in APNIC’s implemented list.

The meeting is over. The status fields have not caught up.

APNIC’s 62 report says prop-169 and prop-170 reached consensus at the Open Policy Meeting, held during the conference in Mumbai from 4 to 10 September 2026. APNIC’s current proposal overview places both under “Reached consensus at APNIC 62.” That is a clear result, stated twice by APNIC.

Open either live detail page and the record changes tense. The prop-169 page and prop-170 page each label the current status “For discussion at APNIC 62 OPM.” Their histories stop at the pre-meeting proposal and Secretariat impact assessment. The overview’s separate “Implemented” list contains neither.

The APNIC 62 proposal agenda is an archived meeting page headed “To Be discussed at APNIC 62.” It records the planned agenda, not either proposal’s current status.

Those facts describe three different stages: consensus at a meeting, a proposal awaiting its next documented step, and implementation. APNIC has recorded the first. It has not listed the other two proposals as implemented. The live detail pages, however, still point readers toward a discussion that has already happened.

The proposals are not interchangeable. Prop-169 would replace the fixed /23 usage-plan reference in APNIC-127 section 6.2.1 with wording tied to the delegation under assessment. Prop-170 would allow conditional nibble-boundary alignment for LIR IPv6 allocations while keeping needs assessment. APNIC says prop-170 does not change the /32 minimum, apply to assignments or require existing holders to resize allocations; an overlap can still block an expansion.

APNIC estimates implementation at about three months for prop-169 and six months for prop-170, both subject to a call for editorial comments. The official pages checked here do not give a date for that call, so the clocks cannot yet be assessed against a public start date. There is no basis to call either proposal overdue.

The repair is modest and useful: update each current-status field, add the post-meeting history entry, identify the next step and publish the editorial-call date when it exists. Until those fields match the meeting record, readers have to assemble the policy’s state from multiple APNIC pages. The registry has already done the hard part—recording the outcome. Its pages now need to agree with one another.