On 04/11/2012 06:43 PM, Frank Gadegast wrote:
obviously not true. ripe's core task is number resource coordination, the db is a service, if ripe decided not to provide for it - then there simply wouldn't be one.
Sorry, but the above statement IS true indeed. Chris: you are mixing RIPE and RIPE NCC.
no. it is ripe's and ncc's core task. so talking about ripe as a superset or at least including ncc this is absolutely correct.
The community has a real interest in an up-to-date and working whois db,
first of all it's not up to you (or any single one else) to decide for the community. and it's e.g. my and probably many others' interest that ncc can coordinate to make ip work. what you are calling for - no matter what you call it - doesn't affect this coordination task. what you are calling for essentially also isn't a working db (it works, and you are free to talk to people to ask them to change their objects according to your ideas), but making ripe some sort of police-substitute, and forcing everybody to follow your strange ideas which are not ripe-business. but being an enlightened (errm - i mean that french thing, you know, don't mistake this for hybris, please :) ) netizen, data economy btw is a real interest for me (actually it's the law)... maybe sbdy from ncc has an estimate on introducing a refer attribute in inet*num objects. i guess this should effectively lead to a technically less complex, as more streamlined, db. regards, Chris