Dear colleagues,
On 15 Sep 2025, at 11:12, Edward Shryane <eshryane@ripe.net> wrote:
Dear colleagues,
On 8 Aug 2025, at 17:03, Edward Shryane <eshryane@ripe.net> wrote:
Hi Cynthia, ...
I will gather feedback and present at RIPE 91.
The NCC were asked to solicit feedback from those who would have objects deleted due to the proposed cleanup of the RIPE-NONAUTH database. We emailed a notification to users on the 15th September. We found 16,497 RIPE-NONAUTH route(6) prefix matching an RPKI VALID ROA. We sent 514 notification emails to the maintainers of those objects. We matched 27,449 RIPE-NONAUTH route(6), as-set, aut-num objects which primary key exactly matched an object in an authoritative RIR database. We sent 1,635 notification emails to the maintainers of those objects. We received replies from 33 users. 10 of those users confirmed that a total of 15 object(s) could be deleted and 23 asked us not to delete a total of 113 objects. To summarise the feedback on why they still need the objects: * Objects belong to a third party hosting company or CDN. The ISP is just hosting those resources. * They are the maintainer of the NONAUTH objects. However, the objects are being used by ISPs. * The maintainer is actively using those NONAUTH resources. * They cannot control how the multiple service providers handle traffic. They had some issues in the past due to some policies written by those organisations. * Creation of ROA or ROUTE objects (with the same structure) is not possible in ARIN. * Network complications. They cannot get transit in their own country. They use a VPN to Europe. So, they need to be registered in NONAUTH. * Satellite service provider which customers that use their network. * The user is busy and doesn’t have time for checking this. * They are the owners of those objects and are using them. We found the feedback useful, in particular the importance of notifying maintainers in advance and allowing them to opt-out if they are still using the objects. However the continued use of RIPE-NONAUTH will make it more difficult to deprecate the database in the future. Please let me know your feedback on our findings. I will also present at the DB-WG session at RIPE91 for discussion. Regards Ed Shryane RIPE NCC