Hello Martin, Randy, all
Please allow me to provide a bit more context regarding the processing
times shown in the report of the Charging Scheme Task Force.
First, these figures are averages based on samples and experience in
Registration Services. Actual cases may be completed faster, or
sometimes significantly slower.
Second, the four categories mentioned in the Charging Scheme Task Force
report cover a range of scenarios, and this grouping creates some
cluster effects that can be confusing.
For example, policy transfers of PI resources within the RIPE NCC region
can involve:
- two members,
- a member and a non-member
- two non-members.
Transfers between two members are usually below the average of 75
minutes, while those involving non-members usually take a bit longer,
especially when the receiving party is new to the RIPE NCC and
additional checks are required.
The Legacy Updates group is similar. Randy is correct, updates of legacy
resources under contract between two existing members are typically far
below the 360-minute average, but they represent only a small portion of
this group. The longer processing times mainly occur when a new contract
must be signed with the RIPE NCC or a sponsoring member, or when only
one party has a contractual relationship. In particular, cases where the
offering party has no contract (while the receiving party has or will
have one) can take significantly longer, as the RIPE NCC must perform
extensive due-diligence checks before the Legacy update can be completed.
I hope this clarifies.
Kind regards,
Marco Schmidt
Manager Registration Services
RIPE NCC
On 29/10/2025 02:05, Randy Bush wrote:
hi clara
as usual, i am a bit confused; yes, a low bar. have sympathy; you have
been doing this *far* longer than i.
CSTFR sez:
it takes staff an average of 75 minutes to process each intra-RIR
transfer ticket, 200 minutes for an inter-RIR or M&A transfer, six
hours for a legacy transfer between parties with contractual
relationships with the RIPE NCC
looking at table 7, i think we're comparing "RIPE NCC Region Transfers"
with "Legacy Updates," whatever the heck they are. i suspect that they
are not inter-member transfers of legacy space. as you were on the
CSTF, so i hope you remember what these numbers actually measure and
could please whack me with a clue bat.
Clara:
legacy status, regardless of whether there is a contractual
relationship or not, need to undergo a more stringent diligence
process for transfers that puts additional burden on the NCC
i naïvely assume that the extra diligence of provenance is incurred once
when the space is first registered, e.g. when the holder becomes a
member or it is acquired by a member. and that cost would be a one time
cost. from then on, why is it not just space with a different paint
job?
if member A transfers legacy space to member B why the heck would it
take significantly more effort than if A transfers non-legacy space to
B? can someone from the registry comment?
similarly if A transfers legacy space to B as non-legacy, does it
really require less effort than if B receives it as legacy space?
randy, trying to understand what problems we really need to solve
-----
To unsubscribe from this mailing list or change your subscription options,
please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
-----
To unsubscribe from this mailing list or change your subscription options,
please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
