Hi, On Thu, Nov 05, 2015 at 07:40:58PM +0000, ripedenis@yahoo.co.uk wrote:
So here is my 4 step proposal that I believe could be implemented within a month. If we implemented this you can be sure that all ROUTE objects in the RIPE Database were created with the knowledge and approval of the related resource holders. I believe that is the desired goal.
This sounds like a workable and fairly low-effort approach to me which would bring lots of direct benefits. So +1, full support. (I do see some resistance in the form "but, but, what about the other databases?" - yes, we need to clean up cross-registry and all that, but cleaning up our own backyard right away without having to wait for the global solution is GOOD)
STEP 4
This is a one off cleanup of existing ROUTE objects. For all ROUTE objects currently in the RIPE Database that relate to an out of region, existing resource, send the appropriate notifications. For any that no response is received within a week, delete the ROUTE object from the RIPE Database.
I'm a bit more careful about that one, though - in principle, yes, but "one week" is a bit harsh here, so I'd go for multiple reminders and a longer time. This is a different case than "I have just added this object and it is now showing up (with an appropriate message by the DB robot), so let's just check my mail until the reminder appears!". (NB: did you intentionally not copy db-wg?) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279