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] [routing-wg] AS43890
- Previous message (by thread): [anti-abuse-wg] [routing-wg] AS43890
- Next message (by thread): [anti-abuse-wg] [routing-wg] AS43890
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Nov 17 22:16:08 CET 2014
In message <20141117084633.GA20482 at Space.Net>, Gert Doering <gert at space.net> wrote: >MCCI should really, really clean up all route objects that cover parts >of their address space but point to other origin ASes. Wait, so you are saying that the *Iranians* should be responsible for cleaning up the mess that was left behind by their predecessors, i.e. the folks who had the 188.229.0.0/17 block before the Iranians did?? Can they even remove those route objects, given that they didn't even create them in the first place? Can any arbitrary RIPE member remove route objects that were created by any other RIPE member? Regards, rfg
- Previous message (by thread): [anti-abuse-wg] [routing-wg] AS43890
- Next message (by thread): [anti-abuse-wg] [routing-wg] AS43890
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]