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/anti-abuse-wg@ripe.net/
[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 ]
Suresh Ramasubramanian
ops.lists at gmail.com
Fri Nov 6 01:31:53 CET 2015
+1 here - though for step 3 it might be an idea to check just how many such objects are there and with what frequency they pop up. Some of these funny announcements can be short lived indeed - only lasting a few hours. --srs > On 06-Nov-2015, at 1:29 AM, Bengt Gördén <bengan at resilans.se> wrote: > > I don't see any immediate pitfalls in your 4-step. The only small, very small, thing is step 3 and it can be abused. But only for <24h
- 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 ]