Summary

  • Prop-171 would make upstream address holders responsible for a workable route to downstream teams that can investigate abuse reports. It would not require every customer contact to be published.
  • The proposal left APNIC 62 without consensus. Existing monitoring and response duties remain; the disputed addition is how responsibility follows a report across organisations.

Someone has received the abuse report. Does that person know who can investigate it?

For the person sending it, the difference means more than another email. If the report stops at the wrong desk, finding the right team becomes another job. That possible gap—not an accusation against a particular operator—is the problem behind APNIC's prop-171.

The organisation named in an internet address record may supply address space to a customer that runs the affected systems. The supplier can maintain the public contact while the customer holds the logs, knows the service and can make a change. A working mailbox gets a reporter into that relationship. It does not, on its own, describe the route through it.

There is an important qualification. APNIC's active policy, section 5.3.3, already requires monitored contacts and prompt responses aimed at resolving abuse complaints. Describing today's rule as merely an email-delivery test would erase that obligation. Contact validation, whose history includes the implemented prop-125, checks something narrower than the handling of an individual incident.

Who forwards it—and who can prove it?

Tsung-Yi Yu and Alban Kwan's first draft of prop-171 would put responsibility for a dependable downstream route on the upstream holder. It permits different arrangements: the customer can operate the registered contact, a central upstream desk can forward reports, or another effective method can connect the parties. It does not demand a public directory of every customer's staff.

Different networks would not have to build identical help desks. But what would count as proof that a route works? A contact list tells you whom to approach. A forwarding log records an attempt. Confirmation from the investigating team shows a further step. None of these proves that the complaint is valid or that the reporter's preferred remedy is appropriate.

The Secretariat's assessment on the proposal page puts those practical details at the centre of the debate. It asks how the operational route would be defined and validated, notes possible complexity from fine-grained contacts, and raises workload and enforcement expectations. Some existing customer-specific or upstream-managed IRT arrangements may already cover the intended cases. The new obligation therefore needs a clearer boundary than “make someone accountable”.

The draft expressly avoids a new audit system, changes to validation timing and new APNIC investigative or enforcement powers. Those exclusions matter, but they do not specify how to assess compliance with the proposed handoff duty. Implementation arrangements and timing remain undetermined. Calling the task administrative does not make it costless.

Nor is the size of the problem established by the draft. The authors describe a substantial share of certain contact problems as arising downstream, but provide no counts, observation period or reproducible method. That is their account of the motivation, not a measured regional failure rate.

A proposal sent back, not a rule switched on

The APNIC 62 report records no consensus on prop-171 at the September 2026 meeting in Mumbai. The current proposals list places it back in mailing-list discussion. The individual page's older conference label should not be read as a later decision.

APNIC's 25 September account describes support for better abuse handling alongside disagreement about responsibilities, overhead and the method. Failure to agree on this text neither adopts it nor proves that the operational concern is imaginary. Under the policy-development process, discussion is still several decisions away from implementation.

The next useful draft would make a small but consequential distinction observable: who accepted the message, who took responsibility for investigating it, and how the first party knows the second has it. An answer need not expose a customer's private contact details or make APNIC decide the merits of a complaint. It does need to explain what a reporter can reasonably expect after “received”.