This is one of those one in a million type occurences .. and given that your company is a listed one - so that contact information is available in a multitude of other places, that same death threat would probably have been phoned in to your office receptionist instead of your colleague, from whoever was crazy enough to make it.<div> </div><div>That does not sound like any kind of argument to do what you ask for .. and making it hard will simply add to the already extremely high quantum of abuse issues in the RIPE area. On Thursday, June 20, 2013, Benedikt Stockebrand wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Frank and list, Frank Gadegast <<a href="javascript:;" onclick="_e(event, 'cvml', 'ripe-anti-spam-wg@powerweb.de')">ripe-anti-spam-wg@powerweb.de</a>> 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. <a href="http://www.stepladder-it.com/" target="_blank">http://www.stepladder-it.com/</a> </blockquote></div> -- --srs (iPad)