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/[email protected]/
[anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Previous message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Next message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo.vegoda at icann.org
Thu Apr 8 22:33:21 CEST 2010
On 8 Apr 2010, at 6:29, Frank Gadegast wrote: [...] > This document describes the implementation of an abuse monitor system > at RIPE NCC. Its intention is to ensure working abuse contacts on the > members side and to improve the awareness, responsiveness and work flow > for abuse reports for the reporting (and abused) internet users and the > RIPE members (owning the misused services). I still don't understand how a system similar to the one proposed would compel members to deal with abuse reports. Presumably a member could just send all their incoming abuse reports to /dev/null. As I understand it, the people who want to receive reports to help them keep their networks clean already publish IRT objects. A system like the one proposed would add an extra layer between the complainant and the relevant network and could well become a target for abuse itself. I am not sure how it would make network managers want to deal with abuse complaints that they are currently ignoring, though. Can you expand on that? Thanks, Leo
- Previous message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Next message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]