Hi Carol,
Yes indeed, the consistency problems in the RIPE database are well known and are even well documented in:
[...]
Our plans to deal with them are also documented in:
[...]
We do plan to try to eliminate multiple objects pointing to the same person, as well as other clean ups of the person data. [As a side note, this project is now well underway.]
I know - this was mentioned by you(?) at the last RIPE CoCo meeting in September. I also know that RIPE NCC did, does an most probably will do a hard but nevertheless excellent job in "cleaning up" the RIPE database. But this is just one point for me.
We have not however discussed limiting the ability to enter data in the RIPE database, outside of the current and proposed authorization mechanisms. That would certainly be a significant change of course, and for that reason, I have cc'd the RIPE Database working group on this mail to get their feedback on this idea.
The other point is to prevent the RIPE database from further pollution. There should be some settings to guarantee this. What is your opinion: should I post my suggestions just to 'lir-wg@ripe.net'and 'db-wg@ ripe.net' or in addition also to 'local-ir@ripe.net'? Many greetings, Carsten -- Carsten Schiefner mailto:schiefner@contrib.com TCP/IP GmbH, Berlin (Germany) - Contrib.Net http://www.contrib.com Phone: +49.30.44 33 66-0 Fax: +49.30.44 33 66-15 ======================================================================