Dear Elmar,
Don't forget that not everyone who enters data into the RIPE Database is a member. So this statement may be better in the Database Terms and Conditions.
A good approach can be to have a clear statement in the contract with the LIRs that they are responsible for obtaining the permission to publish any personal data they maintain OR that are maintained by maintainers they created. This solves a large part of the problem.
[...]
How does this sound?
Not different. A lot of maintainers do not belong to LIRs, so there is no contract.
I was not clear enough, I suppose. I see three cases: 1. Maintainer is a LIR - we have a contract. 2. Maintainer created by LIR - bound by LIR contract. 3. Maintainer authorized/created by RIPE NCC - authenticated by RIPE NCC and bound by DB Terms and Conditions (you deleted the part that referred to this case, see below). Best regards, Janos As we will require all objects to be maintained in the future, it seems enough for me to make sure we have the above principle accepted by the _maintainers_. We may have to think over the process of creating a new maintainer. We may have to have it created by an existing maintainer or by some otherwise authenticated person (who can then assume the responsibility for the data they maintain in the future).