Michael Holzt wrote:
On Thu, Jun 29, 2000 at 04:26:03PM +0000, Stephen Burley wrote:
That ones easy, it should never have been used for this info RIPE is the rIPe repository not the domains authority.
Perhaps it wasn't designed for this usage, but it was clearly the best system we ever had for domain registry.
No it was the best publicly available without re-engineering it, which does not give you (deNIC) the right to use it.
You could use the same person handles for a number of top level domains which reduced the work in a great way. Now we will have to cope with different person handles for every registry, with complicated update procedures and so on.
Good process, wrong DB, the software to run the identical DB structure has always been available to use and create your own (deNIC's) copy cat DB taking advantage of the fine processes put in place by the RIPE community and the engineering of the DB team in the NCC. So there was never any need to populate our DB just to take advantage of the DB structure - deNIC should have created there own.
The wiser solution would be, if the registries would have agreed on supporting the central ripe database by funding and services. I don't see how the costs can be lower for several independent registries than for one community-payed-for central registry.
Look to CENTR for this not the RIPE community.
If you want to see what can happen when all this information disappears from ripe and will be moved to other registries, just take the DeNIC (or the CORE) as an example. For both registries i don't know how to update my handles or can do it only by asking an official registrar / member.
This fragmentation of registries will only lead to unreliable and outdated informations in the databases.
That is what CENTR is for, use it.
The only domains that are in there are the reverse domains for very good reasons.
No, the ripe database contains in the moment data for at least 21 top level (country) domains.
Which is fine but i think it will also move to servers run by CENTR eventualy - and again they are there for historicaly good reasons.
designed to for this use and so give the RIPE community back the level of response from the servers/systems the community funded and frankly deserve.
The ripe database was always very well in service.
Wrong the most objects in the DB are now domain objects and most of the updates are for person obs and domain obs - as reported at all RIPE meetings - and the response time to updates is considerably impacted by the amount dom and person objects being queried and updated. Regards Stephen Burley UUNET EMEA Hostmaster
-- With kind regards
Michael Holzt