Hi Ed, That sounds like a much better timeline. :) Thanks for the update, I understand you don't want to delay it even further. -Cynthia On Thu, 4 Dec 2025, 15:35 Edward Shryane, <eshryane@ripe.net> wrote:
Hi Cynthia,
On 3 Dec 2025, at 16:12, Cynthia Revström <me@cynthia.re> wrote:
Hi Ed,
I think this is a good idea however I would advocate for pushing it back another 2-4 weeks, maybe February instead of January?
This is because the first step in your plan (on 2026-01-05) takes place as a fair number of people might still be on holiday (at least here in Sweden many are). Even if they aren't still on holiday that might be their first day back so they might not have had time to prepare.
Thanks for letting me know. We need to balance removing password support in a timely fashion with not causing operational problems for our users.
How about moving the first step to Wednesday 14th January at midday? This gives operators more time, and mid-week rather than the beginning of a week.
To ensure the community is notified properly, in addition to notifying the DB-WG, we will also notify all maintainers with passwords beforehand, using all values in : * mntner {notify, mnt-nfy, upd-to, e-mail} attribute values * {notify, e-mail} attribute values in all tech-c references in all mntners
We can also start to send notifications earlier, i.e. before the break for Christmas and New Year.
Then also move the Whois release which removes password support into February. I don't want to delay this too long.
Regards Ed Shryane RIPE NCC