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 ]
Marco d'Itri
md at Linux.IT
Tue Feb 10 12:08:38 CET 2004
On Feb 09, Christian Rasmussen <chr at jay.net> 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? >> >Of course not. But how many inetnum objects have these remarks? >> How is this relevant to what we are discussing? >It is very relevant for your argument, you say this remark-thing is easy to >understand, but if very few use it, then its not relevant if it's easy to >understand or not. No, I'm not saying this. My point is that if is too difficult for users to find an abuse at example.com address when there is some text asking them to use it then it will probably be at least as difficult finding it when advertised only with something like "abuse-mailbox". >Yes, it might be a good idea to just have an "Abuse-Whois", abuse.ripe.net, >enter an IP adresse and you get the corresponding abuse address and nothing >else! It's a good idea, I think it could be easily implemented as a proxy, I'd like to know NCC's opinion about this. >Yes, but not with abuse in the maintainer. This requires defining new semantics for the mntner object. It would be possible, but we already have irt objects which are a more complete solution which exists right now. Let's try to fix them (if there is something to fix) before starting designing something new. BTW, why don't you try creating an IRT object? I know somebody who yesterday registered one after reading this thread, and it took only a few minutes to him (after understanding that the TI marketing in the documentation should be ignored). -- ciao, | Marco | [4525 acN6O2k9DLSLs]
- 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 ]