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 10:24:31 CEST 2011
Not a bad idea which is why I suggested something like the WDPRS to deal with this sort of case. It is not like hijacking netblocks is anything new .. is there already some RIPE policy document on dealing with these? On Thu, Jul 28, 2011 at 1:42 PM, Frank Gadegast <ripe-anti-spam-wg at powerweb.de> wrote: > > Looks like to me, that RIPE NCC should defny compare RIPEs netblocks > to several blacklists. This will indicate highjacked or misused > netblocks quite easily. > > Also looks like to me, that we could keep IPv4 much longer, if > all those blocks could be reallocated. > > -- 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 ]