Summary

  • APNIC's adopted 2027 Activity Plan targets a comprehensive public test environment covering key registry interfaces in Q3 2027.
  • APNIC already documents a testbed for the NIR API. The new plan names a wider public rehearsal but has yet to list its interfaces and access rules.

A registry change is easiest to applaud before anybody has to use it. APNIC has now put a place to test those changes on the calendar.

Its Executive Council minutes, adopted on 19 October, say Member feedback prompted work on a public test environment for registry, resource management and product changes before release. The Council unanimously adopted the attached 2027 Activity Plan and Budget. Under Registry Technology, that plan targets a “comprehensive public test environment” covering key APNIC registry system interfaces in Q3 2027. The board has approved a target quarter for a service still to be built.

There is already a smaller demonstration of the idea. APNIC's NIR API testbed documentation says the interface lets National Internet Registries manage registration information for their subaccounts. The basics describe test objects, asynchronous tasks and idempotent requests. APNIC's 2021 annual report records the establishment of an external test environment for that NIR API. It gives a user something better than a diagram: a documented sequence of actions and responses.

The 2027 commitment reaches beyond that specialist API. The minutes name registry and resource management changes as well as products; the activity plan says “key” interfaces in the plural. A usable rehearsal must let its intended users run realistic sequences, encounter validation errors and send the resulting evidence back before a release reaches the authoritative ledger. A screen that merely displays a future interface would leave the risky part untested.

The published plan does not yet name the interface inventory, eligible users, authentication method, test-data boundary, reset rules or the build version a tester will see. Those are the release facts that would turn the Q3 target into a working public service. A registry should be able to show, for example, how a mistaken test delegation is discarded and how a fixed validation rule is retested without changing a live allocation. The NIR API's task and idempotency model offers one concrete starting point; it does not define every surface the new environment will cover.

APNIC has made a useful promise: let people handle the machinery before it becomes the only machinery they can use. Its next publication should be a tester's guide, with the permitted actions, isolation boundary and feedback route written as plainly as the deadline.