j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
Apologies for the delay in responding to your question.
Any customer assignments or sub-allocations that your members make to their customers are NON-PORTABLE. This means that when a customer ceases to receive connectivity from your member, then the customer has no choice but to return the address space.
In this particular case that you are referring to, when APNIC made the allocation the following piece of standard information was included:
[snip] APNIC strongly recommends you include in your standard connectivity contract provisions that require customers to return address space back to you when they change service providers. Such wording will help to reduce the growth in the number of global routing tables, thus aiding the continuation of global connectivity for all networks. [/snip]
How this case is proceeded with depends on the contractual agreement APJII has with it's members. Your member may wish to ask the other upstream who is currently announcing the /24s to stop announcing them.
In any case, should your member come back for another allocation it should not be approved if non-portable address space is being used in the wrong manner. You may need to remove route or other objects from the whois database if you are having problems stopping the routing of these assignments.
If your member does not understand the policy fully, it would be good if APJII can educate them on this. You should also suggest to your members that when they are making assignments to their customers they should have some agreement so that when the customers are disconnected from the network they should return the resource.
I hope this information is of assistance.