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/db-wg@ripe.net/
[db-wg] Re: abuse-c: proposal
- Previous message (by thread): [db-wg] Re: abuse-c: proposal
- Next message (by thread): [db-wg] Re: abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at TechFak.Uni-Bielefeld.DE
Mon Feb 9 10:14:43 CET 2004
> My requirements as an operator[2] are clearly not met, I get loads of > abuse complaints to my notify and changed addresses every week, which I > have to forward to either the abuse dept or /dev/null. So, the problem is mainly a marketing/education problem. No matter what change to objects or presentation will be agreed upon, nothing short of limiting access to the database would stop the uneducatable or "let's hit them all" type uncooperative tool writer. The education or usability problem can IMHO best be achieved with a dedicated interface for "abuse" purposes, be it a web interface or a dedicated whois server. No new objects are needed. -Peter
- Previous message (by thread): [db-wg] Re: abuse-c: proposal
- Next message (by thread): [db-wg] Re: abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]