Hello.
Current RIPE Charging Scheme based upon variable - LIR count. Its nice,
but its very unstable value. Its hard to make long term budget policy in
so variable situations.
Opposite to LIR count, we have IPv4 count, IPv6 count and ASN count -
what are pretty stable, because have specific end amount and cant be
changed year-by-year in large scale.
My proposal is:
1) RIPE need to make some reserve funds for compensate some looses due
sanctions, banking troubles and etc... for example 5% of total budget.
2) Change Charging Scheme from LIR based to Resource based and spare
RIPE budget spending in equal parts. Big LIRs with large amount of
resouces - will be pay more (in equal share), LIRs with small amount of
resources - will be pay less (in equal share).
We are do some investigation and most largest IPv4 holders in RIPE
region is:
orgID - Legal name - Country - IPv4 allocations - IPv4 count
---
de.telekom Deutsche Telekom AG DE 31 28972544
fr.telecom Orange S.A. FR 53 23655168
uk.microsoft Microsoft Limited UK 135 16572416
fr.sfr Societe Francaise Du Radiotelephone - SFR SA FR 119 16313344
ru.rtk PJSC Rostelecom RU 468 11123712
uk.bt British Telecommunications PLC UK 43 10948608
es.telefonica TELEFONICA DE ESPANA S.A.U. ES 43 10806016
uk.ntli Virgin Media Limited UK 41 9378816
fr.proxad Free SAS FR 8 8871936
it.tin Telecom Italia S.p.A. IT 10 7996416
it.interbusiness Telecom Italia S.p.A. IT 28 7898112
uk.bskyb Sky UK Limited UK 23 7240704
fr.bouygtel Bouygues Telecom SA FR 16 7098368
uk.tm EE Limited UK 17 7037952
tr.telekom Turk Telekomunikasyon Anonim Sirketi TR 13 6923264
se.teliase Telia Company AB SE 54 6706432
de.mediaways Telefonica Germany GmbH & Co.OHG DE 22 6414336
se.swipnet Tele2 Sverige AB SE 72 6316032
de.arcor Vodafone GmbH DE 24 6136832
If you open their financial reports you will be - their companies
without issue can be proportional equal fee for their resources in own.
On 18.04.2024 13:17, Remco van Mook wrote:
Dear colleagues,
I’d like to draw your attention to an article that was just published on RIPE
Labs, about building a stable future for the RIPE NCC.
As it touches on some very foundational aspects all across the various working
groups and NCC membership, I thought it important to share, and I would very
much like to ask everyone for their input and ideas.
In order to not spread the discussion too much across the various mailing
lists, I suggest that we use the general RIPE list (which I’ve put into the
reply-to field of this email.
I’m currently in the process of organising a BOF during RIPE 88 on this topic
as well and am looking forward to a constructive discussion!
Kind regards,
Remco van Mook
RIPE NCC Executive Board
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/ripe-list
