Symbolic gestures can backfire if they introduce barriers to critical services. RIPE NCC has long maintained a position of technical neutrality, serving all members equally regardless of their internal networking choices. Deprecating IPv4 access would move RIPE NCC into a policy-driven or ideological position, rather than maintaining its role as a neutral and reliable coordination body. Regards, Arash On Wed, 28 May 2025 at 18:21, Brett Sheffield <ripe@gladserv.com> 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 -- Brett Sheffield (he/him) Gladserv Ltd ----- 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/