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/[email protected]/
[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 ]
MarcoH
marcoh at marcoh.net
Mon Feb 9 15:27:17 CET 2004
On Mon, Feb 09, 2004 at 01:07:30PM +0100, Marco d'Itri wrote: > I looked at the inetnum object CISBRD-CUST-ADSL-113, one of these > created by you for your broadband customers: it contains in the remarks > attributes a well visible notice about where complaints should be sent, > yet you say that you still get them at your personal email address. > Do you really think that users would understand better if they read > "abuse-mailbox: user at example.com" instead of that sentence in english > which explains what the allocation is for and who should be notified of > abuse? > I do not pretend to be an expert in user interfaces, but I think that, > for a random user, natural language should be easier to understand than > something like "abuse-mailbox". > > I think that there is a consensus that there is the need for a method to > look up the abuse desk address for an IP address, and I believe that irt > objects (which have the big advantage of existing) are fit to this. The problem is that over 10% of the inetnum objects contain a remarks: attribute to an abuse contact. With this amount of usage, I think you can justify the creation of a dedicated attribute, which is not free-form and users don't have to rely on the string around it to find the correct address. MarcoH
- 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 ]