On Thu, May 06, 2004 at 05:18:49PM +0200, Jeroen Massar wrote:
That is very good to hear as that is I think the main issue that some people where talking about.
Can someone sum up the issues that are left with IRT's?
There is not a problem with IRT, it's with the whole database. The problem which we are fighting here is that any ip lookup with the ripe database returns multiple attributes called e-mail and multiple other attributes containing an email address. Operational experience shows that most users aren't able to figure out which address to use when complaining so they just use all. Let me repeat again, the problem is not the IRT object itself, the probemm is that it only contains an e-mail attribute, which is used throughout the database in all objects. We just need a better representation of the data so people can easily find the correct address, without having to read the database specs. Hence the only problem now solved is the fact that the requirement for encryption held people back in creating an irt object. That is a nice change, but it will not fix the problem of being spammed with abuse complaints on various operational and personal email addresses. Grtx, MarcoH