[ncc-services-wg] NCC service request - ticket robot test facility

Hello Carsten,

Thank you for that information.

To answer your question we don't know how much extra work
using the production robot would cause our resource analysts
as we don't know how many tickets would be created by
testing automated resource managment systems, however we do
know that each ticket so created would have to be manually
processed by them.

Please note that creating a ticket robot test facility would
require approximately two days for one programmer.

-- 
Best Regards 

Timothy Lowe

X-Organization: RIPE Network Coordination Centre
X-Phone:        +31 20 535 4444
X-Fax:          +31 20 535 4445






On Thu, Oct 20, 2005 at 11:03:04PM +0200, Carsten Schiefner wrote:
> Hi Timothy,
> 
> Timothy Lowe wrote:
> >One of our members has asked the RIPE NCC to
> >provide a test facility for the RIPE NCC ticket robot.
> 
> I don't have any particular view here as I don't have to deal with the 
> robot these days.
> 
> Having said that, DENIC, the german ccTLD registry, has a test registry 
> system ready for its members for more than x; x > 3 years now. And in 
> the absence of any negative feedback I consider it (happily) welcome by 
> them.
> 
> The real difference I'd see is that DENIC's robot is really an automat 
> with no human intervention - when the NCC's ticket robot by its very 
> nature requires that (aka. manpower). But I might be wrong here, see 
> first para.
> 
> So for the time being some of the comments here hold somewhat true for 
> me - is there an estimation of the additional workload on the IP 
> Resource Analysts to process these test tickets? Even by only 
> alternately approving and rejecting every single one of them? But maybe 
> even this human intervention can be automated in the test system on a 
> per LIR basis then?
> 
> Cheers,
> 
> 	Carsten