[anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Previous message (by thread): [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Next message (by thread): [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis
ripedenis at yahoo.co.uk
Thu Nov 5 21:06:13 CET 2015
Hi Gert Thanks for the quick response and support. On 05/11/2015 20:56, Gert Doering wrote: > Hi, > > On Thu, Nov 05, 2015 at 07:40:58PM +0000, ripedenis at 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) I agree a full implementation of cross registry auth with all 4 other RIRs would be great....but how far has that gone in the last 6 months since the last RIPE Meeting? > >> 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!". Agreed. > > (NB: did you intentionally not copy db-wg?) I put this idea on the table before the last RIPE Meeting. I even wrote a RIPE Labs article on it. I wasn't there but tried to get it input to the BOFF on the issue. But I was pretty much ignored. So I thought this time I will target the people who make the most complaints about the consequences of the problem. If these guys like the idea then maybe the DB WG will pick it up :) cheers denis > > Gert Doering > -- NetMaster >
- Previous message (by thread): [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Next message (by thread): [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]