11 Jan
2018
11 Jan
'18
2:27 a.m.
On Thu, Jan 11, 2018 at 01:17:09AM +0000, denis walker wrote:
Unless it has been modified recently there is the reclaim functionality that will allow the resource holder to delete the ROUTE(6) object https://labs.ripe.net/Members/denis/reclaim-functionality-for-resource-holde... But this does rely on the new resource holder knowing the 'potentially rogue' ROUTE(6) object exists. So maybe it is down to a procedural or administrative issue around the transfer process.
Good pointer, perhaps the issue is resolved if "towards RIPE NCC"-migrations are procedurally forced to go through the 'reclaim' process for ROUTE(6) objects, to ensure no objects exist that the (new) owner didn't approve of? Kind regards, Job