[You don't often get email from mm@webrocket.am. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi all!
I support Brett's suggestions! Very symbolic - access to sites and APIs
only on IPv6 sockets!
I would like to draw the community's attention to the goals of revising
the current funding scheme. The main goal is to efficiently utilize IPv4
address space when it is scarce. If there are really no “free”
addresses, there is no point in changing anything. We will invent 15
categories, introduce thresholds, but it will be of no use. The
addresses have never existed and will never appear.
With frantic demand and such prices for rent and purchase of IPv4, we
can hardly economically force organizations that do not use addresses to
give them up and return them to the pool for distribution. What is even
scarier is that these owners may not make any money on their /16 unused
blocks.
If the entire membership fee is determined by the number of resources,
it would be more like RIPE NCC's commercial activities.
But on the other hand, we could fund part of the RIPE NCC budget with a
fee that would be based on the number of /24 IP networks managed by a
single RIPE member. It would be linear and simple.
According to the provided report we are 21248 and we manage 3081702
subnets /24 IPv4. If 10% of the RIPE NCC budget is formed from these
contributions calculated on IPv4 networks, it turns out:
21248*1500*0.1/3081702 - 1 EURO per network /24 per year.
If you have an insane number of networks that you don't use, it will be
very uncomfortable.... But as I understand it that is our main goal, to
get the network holders who don't use them to return IPv4 in pool. They
will either saturate the market and the value of the networks will fall
or simply return them to the pool of unused ones.
It would be very interesting to hear the opinion of these first members
of RIPE.
Best regards,
Mikhail Mayorov,
LIR with 146 /24 IPv4 total allocated
On 28.05.2025 11:21, Brett Sheffield wrote:
> If RIPE is serious about encouraging IPv6 adoption (and I think we are), we need
> to deprecate and remove support for IPv4.
>
> RIPE doesn't have the power to do that for the whole Internet, but it can send a
> clear message by removing IPv4 access to all RIPE services (API, control panel
> etc.).
>
> There's no reason not to do this. All RIPE members have IPv6, and those that
> haven't got themselves sorted can be given 12 months to do so.
>
> Taking a (mostly symbolic) action like this sends a clear signal and will likely
> be picked up by tech media outlets. It's something we *can* do as an
> organisation.
>
> Any objections?
>
> Cheers,
>
>
> Brett
-----
To unsubscribe from this mailing list or change your subscription options, please visit:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.ripe.net%2Fmailman3%2Flists%2Fmembers-discuss.ripe.net%2F&data=05%7C02%7C%7C775b739264e84bb4455208dd9ed3d574%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638841354833800043%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C4000%7C%7C%7C&sdata=8MizzWG56wvT0A7BN08kt1sRAPpw3cc1dNksJEXZaJg%3D&reserved=0
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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fmembership%2Fmail%2Fmailman-3-migration%2F&data=05%7C02%7C%7C775b739264e84bb4455208dd9ed3d574%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638841354833827764%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C4000%7C%7C%7C&sdata=86XUkjRy6Ly0SOYCuVjCMEdixg6HfEn3ohyI8xfrR%2BU%3D&reserved=0