Hi Brett, I wish it were this simple. I agree that IPv6 adoption is the way to go, but removing IPv4 from RIPE services I think will probably achieve the opposite effect (as well as breaking a lot of things). Not everyone is a residential ISP here, so for instance my home ISP doesn't do IPv6 (https://www.havevirginmediaenabledipv6yet.co.uk/). Our own networks are fully dual-stack on everything, but I can't control anyone else's. It's easy to say they'd kick into gear and deploy it if you did that but I think it's highly unlikely. Enabling IPv6 at that sort of scale isn't a case of just flicking a switch, and the bother to a handful of engineers who can't access the RIPE Portal is not going to be the pushing force to make that happen I think. Some UK ISPs are definitely making moves in the right direction (especially Sky at the UK IPv6 Council to my knowledge) but these things will take time, technically to roll out and administratively to convince people to allow for the engineering. To top it off, it's prohibitive to new members as well, people have to get into this community somehow and if we're gating them on IPv6 which at that point, they likely don't control (home ISPs and such), it's yet another barrier to entry and learning resources. Symbolically, sure - I think it gets the point across. Realistically, I think it's going to break a lot of things and be more aggro than it's worth. Warm regards, -- Connor McFarlane Inferno Communications w: inferno.co.uk e: connor@inferno.co.uk t: +44 (0) 3337 999 001 Please direct any new support requests to support@inferno.co.uk rather than myself directly. -----Original Message----- From: Brett Sheffield <ripe@gladserv.com> Sent: 28 May 2025 9:21 AM To: members-discuss@ripe.net Subject: [members-discuss] Re: Reminder that Charging Scheme Task Force comments are open until the end of the month 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/