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] abuse-c
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Patrick Rother
krd at gulu.net
Mon Jan 12 10:34:50 CET 2004
> > On Fri, 9 Jan 2004, Rev Adrian Kennard wrote: > > > It seems there is a pretty clear need for an extra field in > > > inetnum and inet6num records, specifically something like an > > > abuse-c field referencing a person record. > > > > > > A lot of inetnum records I have seen have a remarks field > > > identifying the abuse ocntact, but this is in an inconsistent > > > format making it difficult to automate in any way. It also > > > seems that a lot of network administrators (admin-c) do not > > > feel they should administer their network to remove viruses, > > > etc, and get quite annoyed when contacted regarding abuse. > > > > > > What would be the procedure for proposing such a new field? On Fri, Jan 09, 2004 at 03:47:36PM +0100, Christian Rasmussen wrote: > Realistically I think the majority of inetnum objects needs to have > such a record before anything will change. Therefore I believe it > has to be mandatory for all new inetnum objects to reference an > abuse address. I suggest to make this mandatory for _all_ (new and existing) that have a tech-c entry, by copying the tech-c entries. Afterwards everyone can change his abuse-c, and I think most tools will stop spamming all other email addresses shortly if enough people ignore those reports that are sent multiple times.
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]