[members-discuss] Re: [ncc-services-wg] RIPE NCC response time

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Hank,

Hank Nussbacher wrote:
> Judging by the RIPE statistics posted in regards to hostmaster response
> time everything is great:
> http://www.ripe.net/info/stats/rs/rt-hostmaster.html
> 
> For the last 2 weeks response time is less than 1 day.
> 
> Well due to the "2007-01 Phase 2 Implementation: Direct Internet
> Resource Assignments to End Users from the RIPE NCC", I have been
> submitting tickets to move ASNs assigned to my LIR over a decade ago to
> other LIRs which are now the owner of that ASN (yet now is billed to my
> LIR).
> 
> So starting on June 16 - 6 days ago I submitted 6 "move requests" and
> even got back ticket acknowledgments: 2009063188, 2009063190, etc. and
> yesterday a 7th request.  Yet, I have not heard back from RIPE NCC.
> 
> Yet, the stats graphs shows all ticket requests answered within 1 day.

In order not to disrupt day-to-day operations like resource requests,
which have the highest priority, we have created a separate ticket queue
with lower priority for End User contracts. We have mentioned this at
http://www.ripe.net/rs/pi-existing-assignments.html.
We will take your feedback into account and add more information on the
statistics  page and acknowledgments sent to the LIR.

With regards to the billing of resources, Up to September, LIRs can
indicate which resources should stay with their LIR and which not. If in
the interface provided through the LIR Portal you select 'Not My End
User', you will not be billed for the specific resource in 2010. Move
requests are taken into account but will be handled over a longer period
of time.

I hope this clarifies, however if you have any further questions or
feedback don't hesitate to contact me.

Kind regards,

Andrea Cima
RIPE NCC


> Is it just me?!
> 
> -Hank
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko/VPwACgkQXOgsmPkFrjMsRwCgjVZvVmi20qf9n+qOMC01tCtn
JCAAn2BbgKOij34nxLfi5jIGCH1k9NZ4
=6lAN
-----END PGP SIGNATURE-----