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] 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
Thu Jun 20 16:00:57 CEST 2013
Hi Frank and list, Frank Gadegast <ripe-anti-spam-wg at powerweb.de> writes: > but an end user would never us a whois service and play with options > ... I won't bother you with the entirety of a rather scary story, but I've had a colleague listed as admin-c for a large dial-in address pool. One day he received a death threat by some end user who assumed him to be responsible for something someone has done using one of these addresses (details over a beer at the next RIPE meeting if you press me). If you make looking up the admin-c for an address as easy as some people here like, this will lead to a significant-to-unbearable extra burden on the people listed as admin-c; the result is rather likely that admin-c's will have no option but to resort to rather heavy automated filtering. I have significant doubt that this is in any way helpful. So please, try to find some sort of balance here. Evacuating an office until the police arrive isn't something you---or your management---want to happen more often than can be helped. Cheers, Benedikt -- 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 ]