RIPE handles delay

> From: Joao Luis Silva Damas <joao at ripe.net>
 
> Apart from some HW problems, that are now fixed, we are still receiving
> updates at a rate and in a combination that the DB can't presently handle
... 
> All messages sent are queued and processed in turn. 

This together with recent comments about domain objects in RIPE DB
has started to worry me too. Our operation depends on RIPE's
ability to register IP address assignments. Based on recent
statistics it seems like we are suffering from reasons NOT
related to addresses at all.
http://www.ripe.net/meetings/ripe/ripe-33/pres/db-update/sld008.html

> Also we are going to deploy a queue control system to ensure a prompt
> response to updates more directly related to the RIPE DB intended purpose
> while still ensuring that others not so directly related will get
> processed.

This tactful comment probably means a turn to the right direction.
But I wish it was said loudly and clearly, maybe even as a complete
change in DB usage policy. We pay for address registration services,
please take the domain (non-rev-dns-related) objects elsewhere.

> We have been reporting on the situation to this and other RIPE wgs and

Would it be possible to separate reverse DNS related domain
objects from the big total of domain objects in RIPE DB report?

> > handles per month, a relly from RIPE takes now 10-20 hrs or more in some 
> > cases, regardless of the time (day or night, week or week-end) when the 
...
> > Unfortunately this is causing at least an additional 1+ day delay in the 
> > registration of new domains at the Italian NIC, as IT-NIC requests that a 
> > handle exists for each contact before the domain registration form is 

-- 
Vesa Ruokonen - Internet Services, Telia Finland