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] Hijacked netblocks - any SOP for these?
- Previous message (by thread): [anti-abuse-wg] Hijacked netblocks - any SOP for these?
- Next message (by thread): [anti-abuse-wg] Hijacked netblocks - any SOP for these?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Thu Jul 28 13:15:15 CEST 2011
Thanks for making that clear - but maybe fighting fire with fire isnt going to work here. Can we turn back to the question that was actually riased in the thread? 1. A complaint mechanism 2. Sources for RIPE NCC to do proactive research on misallocations / hijacks On Thu, Jul 28, 2011 at 4:43 PM, Gert Doering <gert at space.net> wrote: > > I wasn't the one that said "RIPE is ... responsible for any abuse". > > I just tried to point out how ridiculous that is. -- Suresh Ramasubramanian (ops.lists at gmail.com)
- Previous message (by thread): [anti-abuse-wg] Hijacked netblocks - any SOP for these?
- Next message (by thread): [anti-abuse-wg] Hijacked netblocks - any SOP for these?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]