
Please stop changing the conversation from charging scheme to IPv6. You're intentionally trying to hijack it in a clear disinformation campaign. Let thise who wanna discuss IPv6 open a separate thread between each other. On Sat, 31 May 2025, 13:25 Matthias Brumm, <matthias@brumm.net> wrote:
Am Freitag, dem 30.05.2025 um 19:38 +0300 schrieb Alexey Berezhnev:
Dear colleagues,
I would like to critically address several points raised by Mr. Walde in his recent message. While the discussion around a fair charging model is essential, the arguments presented are technically inaccurate, operationally naive, and strategically dangerous for the stability of the RIPE NCC ecosystem.
1. “IPv6 is cheaper to implement”
This claim may be true in controlled, greenfield environments. However, it completely disregards the reality of mature, production- grade IPv4 infrastructures. For any large-scale operator, IPv6 deployment entails:
* hardware and software upgrades, * dual-stack maintenance, * reworking ACLs, DPI, logging systems, and monitoring infrastructure, * and additional training, testing, and auditing processes.
This is something I do not understand. We are in a field of profession that is constantly changing. Best practices change, vendors come and go. Nobody wants you to make the transition within two months, but in the last 10 years you should have modernize your network completely and had plenty of time to make it at least v6 ready to do some minor adjustments.
Sometimes this argument act as designing a network or backbone and please don't bother me until I am retired.
Our backbone was implemented in 2016 with IPv6 at the main driver and IPv4 as a suplement. At the moment the backbone is completely replaced with new hardware.
But I do not think the network operators are the breaking point, it is the customers who are afraid of IPv6.
Matthias ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/members-discuss.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/