This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Previous message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Thu Jan 11 02:27:26 CET 2018
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-holders > 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
- Previous message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]