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 ]
MarcoH
marcoh at marcoh.net
Tue Jan 13 17:29:23 CET 2004
On Tue, Jan 13, 2004 at 05:11:18PM +0100, Sebastian Abt wrote: > > Im not sure why it should be multiple? But I think most of us on this > > list can agree with you that a valid abuse email address associated > > with each inetnum in the database would be very welcome. > > That's quite simple: I'd like to insert my customers abuse desk as well > as my own abuse desk to at least keep track of any incidents. So we end up with extending the inet(6)num template to include: abuse: [optional] [multiple] Extend mntner template with: abuse: [mandatory] [multiple] And possibly modify the database software to always list the abuse: field when not present on the inetnum resolve the mnt-by: and include the information in the inetnum response. The user will always find at least one abuse: line (or whatever we decide to call it) directly on the inet(6)num. The only thing we need then is to come up with a default on the mandatory field. I hereby suggest to copy them from the (mandatory) upd-to attributes. This will probably get people to update their mntner to include the correct information in short time. MarcoH
- 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 ]