This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] KSK Rollover Postponed
- Previous message (by thread): [dns-wg] KSK Rollover Postponed
- Next message (by thread): [dns-wg] KSK Rollover Postponed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Thu Sep 28 13:17:11 CEST 2017
> On 28 Sep 2017, at 11:50, Michele Neylon - Blacknight <michele at blacknight.com> wrote: > > 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? Besides, if ICANN's comms people had time to put out a tweet (ugh!) and update the web site, I think they had time to post to the obvious mailing lists. 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. I appreciate how difficult and stressful last night’s decision was for everyone who was involved in making it. Plus of course the complexities of aligning all of those moving parts to be in the same place at the same time. Those considerations are however orthogonal how that decision got communicated. Or should be. Still, at least we now know the root KSK rolloover is delayed. For some definition of we.
- Previous message (by thread): [dns-wg] KSK Rollover Postponed
- Next message (by thread): [dns-wg] KSK Rollover Postponed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]