They seem to have made the announcement about 12 hours or so ago, so why not give them a bit of time? (
Surely 12 hours is more than enough?
As far as I am aware, nothing is on fire. Given the lack of time criticality, I would have thought it’d be more important to the technical communities to have more concrete data to present. Given propagation delays in non-technical circles, I believe ICANN comms felt doing a “normal” press announcement-style approach sooner rather than later and then providing more details to folks who were interested later was a better approach. YMMV.
Providing timely, prompt and clear information is a crucial part of the root KSK rollover. In some ways it’s the most crucial. So it’s a shame that didn’t happen as expected for something so significant as last night's showstopper. And so close to the finishing line too.
We made an announcement within a few hours of making the decision to postpone the KSK rollover and are proceeding to attempt to gather more information to inform the community. Do you feel the fact that we did not send that announcement to technical mailing lists despite not having that additional information have an operational impact on resolver operators?
Regards,
-drc