[acm-tf] Abuse Contact Information - Policy Proposal

Well - I find it useful to search for bad actors who get multiple
netblocks on RIPE

whois -h whois.ripe.net -i mnt-by OBJECT gets me all the netblocks the
botmaster / spammer has, if I choose the query (admin-c, tech-c,
mnt-by etc) correctly - and of course crosscheck by noting the same
badness in those other blocks I find.

If the spammer says his abuse-c is unsubscribe at gmail.com that's yet
another way for me to find him

On Mon, Oct 17, 2011 at 6:01 PM, Denis Walker <denis at ripe.net> wrote:
> We can make the "abuse-c:" attribute inverse searchable. But what is the
> use case? What question do you want this query to answer?
>
> whois -h whois.ripe.net -i abuse-c crew-ripe
>
> What this will tell you is what objects in the RIPE Database have an
> abuse-c with the value crew-ripe. It is a list of objects that this
> abuse handler is responsible for.
>
> It is the opposite of the Abuse Finder. This says I have a resource, now
> tell me who is responsible for the abuse handling. You are saying I have
> an abuse handler, now tell me what resources he is responsible for.



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)