[members-discuss] RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available

Which, by strange coincidence, almost identical to simple flat fee of 0.1 € per v4 address per year.

The only difference is that owner of single /24 can pay 25 € per year and owner of /16 - 6375 € without steps or limitations required.

Still giving RIPE approx 60 mil budget together.

Literally everyone benefits - including companies that actually need a lot of addresses and currently buying them on aftermarket terribly overpriced.

> On 1 Apr 2024, at 15:38, ivaylo <ivaylo at bglans.net> wrote:
> 
> 
> The subject of this discussion go a lot ofside. I dont know why you bloat the theme (maybe it is intensionly ?) leading it to IPV4 holding. Our main focus _SHOULD_ be RIPE budget and financing + sustainabla operation in the next year and in the future at all. This of course is related with the members fee.
> 
> I done a little research and calculations, to tune my initial propousal so: By IANA public documents current delegated resources to RIPE are:
> 
> 86016     IPV4 /19 blocks
> 66624     IPV6 /27 blocks
> 42882     ASN
> 
> If we have a hard coded limits for each LIR, equal steps up, and member fee of 750 EURO per year, each LIR can hold up to:
> 
> 1 x /19 IPV4 BLOCK (sumary = 32 x /24 networks)
> 1 x /27 IPV6 BLOCK (sumary = 32 x /32 networks)
> 16 ASN numbers
> 
> After pass one of the above parameters even with one /24 IPV4, /32 IPV6, or ASN, +750 euro (1500 euro RIPE fee) up to the next proporcional limit:
> 
> 2 x /19 IPV4 BLOCK (sumary = 64 x /24 networks)
> 2 x /27 IPV6 BLOCK (sumary = 64 x /32 networks)
> 32 ASN numbers
> 
> and so on...
> 
> This will generate 64 512 000 euros annual budget for RIPE which is absolutely enough for normal operations in each of the next 10 years, without need to increse members fee each year.
> 
> If somebody is afraid, that other RIRs will not keep going with RIPE fees, and there will be posibly leave of the big resource holders, keep in mind that all small members from the other RIRs will move to RIPE. Also good luck moving to ARIN db mess, the risk to lost route of your prefixes is nearly 90%.
> 
> ----------
> Off topic: About IPV4/IPV6 resources, it is imposible to create kind of ipv4 adress space extension. Many hardware do lookup over the ip header, it is not only software related. Even somebody develope a public standart about that, will take decades before all replacing equipment all over the world and another decades all to be workable. We have working IPV6, right now more than 52% has IPV6 connectivity. Biggest EU access operator already
> give dual stack IPV4/IPV6 even to their end users, and activlly deploy IPV6 stack into their networks. It is much more cheaper in long perspective than to buy/rent IPV4 (NAT/proxy your clients/services over IPV4 and give them IPV6 real addresses). After 2-3 years the core of the Internet will be over IPV6, yes we will need to support IPV4 for the next 10-15 years to provide backward connectivity, but it is a dead end. All who thinks they will do a big profit from IPV4 adresses they hold, do seriously mistake in their logic, but anyway it is their problem. Those who dont implement IPV6 because "yay it is so scary and not working" in one moment will have to do this fast without experience, because will have seroius troubles with IPV4 connectivity.
> 
> 
> 
> 
> Ivaylo Josifov
> VarnaIX / Varteh LTD
> +359 52 969393
> Varna, Bulgaria
> 
> _______________________________________________
> members-discuss mailing list
> members-discuss at ripe.net
> https://mailman.ripe.net/
> Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/mihail%40fedorov.net