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] central whois
- Previous message (by thread): [anti-abuse-wg] central whois
- Next message (by thread): [anti-abuse-wg] central whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benedikt Stockebrand
bs at stepladder-it.com
Fri Jun 28 12:24:37 CEST 2013
Frank Gadegast <ripe-anti-spam-wg at powerweb.de> writes: > Benedikt Stockebrand wrote: >> Hi Suresh and list, >> >> >> Please explain to me why providing an excessively easy-to-use abuse >> interface won't cause such an increase in workload for the recipients of >> that list that it becomes impossible to handle. > > Thats the wrong starting point. > > If some resource holder is not willing to reduce abuse coming > from his networks, theres nothing we can do. > And it will not harm him to pubish his abuse contact in a central space, > hes not reding the abuse reports anyway ... Sorry, this is nonsense. If somebody has his home PC being part of a botnet, and someone uses that botnet to flood a victim with ping or TCP syn or <whatever> flood attacks using my IP address, then how will the mails I get as my own abuse-c find their way to the bot PC owner or his ISP's abuse-c? Your entire chain of reasoning relies on the fact that whatever IP address from an attacker your end users find in their logs identifies the abuse-c to contact. -- Business Grade IPv6 Consulting, Training, Projects Benedikt Stockebrand, Dipl.-Inform. http://www.stepladder-it.com/
- Previous message (by thread): [anti-abuse-wg] central whois
- Next message (by thread): [anti-abuse-wg] central whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]