[ksk-rollover] ICANN board meeting result and the Current status of KSK-Rollover

[Eric Osterweil]

Hi David,

Thanks, I strongly agree with your comment about looking toward (but not past) a post mortem (maybe calling it an "After Action Report, AAR," would sound a little less foreboding though). :)  I think there will be a lot of moving parts and a lot to measure after the roll.  I would, however, suggest that there will be much more to learn than what we see in the “seconds” after the roll (I lost track of where that comment came from, sorry).  I think we need to look for measures that could be useful in ascertaining when the operational ecosystem has stabilized.  For example, all of the outreach that ICANN org and others have done has taken time.  That tells me that there are DNS consumers/stakeholders (including both those we have reached, and those we have not) who may have operational reactions to the roll: changing, turning off DNSSEC, keeping it on (steady state), etc.  I think we need to factor these kinds of measurements into decisions about when we can assess the effect of the Root KSK roll.

Just my 0.02,

Eric

> On Sep 18, 2018, at 11:29 AM, David Conrad <david.conrad at icann.org> wrote:
> 
> Hi,
> 
> We (ICANN org) don’t have an opinion (individual staff members with their ICANN hats off might :)).
> 
> As you’re probably aware, currently, the DPS states (paraphrasing) we should roll the KSK after 5 years from the point the KSK is put into use.  As such, the next roll is anticipated to be after 11 Oct 2023.
> 
> However, as Matt said, we listen to the community. If the community would like us to roll more frequently, all that we in staff need to know is what that frequency is. There are, of course, operational costs associated with the roll, both at ICANN org as well as within the resolver operators community (at least for those folks who prefer to roll manually) that will vary depending on roll frequency, but presumably those costs won’t be too outrageous.
> 
> The next step would probably be to figure out how to get a consensus on what the frequency should be. I’d think that a 'post mortem' report about the current rollover would be helpful in informing that consensus. The Board has already task ICANN org with putting together such a post mortem (the analysis Matt mentioned).
> 
> Regards,
> -drc
> 
>> On Sep 18, 2018, at 3:44 AM, Olaf Kolkman <kolkman at isoc.org <mailto:kolkman at isoc.org>> wrote:
>> 
>> I agree with Michael, albeit I would phrase it slightly differently:
>> 
>> Rolling the key regularly is a strategic choise and makes a keyroll an operational reality.
>> 
>> How regular (or how frequent) is a tactic. Whether That is yearly, no monthly or once half a decade is a tactic that takes into account some of our learnings. 
>> 
>> I would really like to see that strategic position being explicit.
>> 
>> 
>> Olaf.
>> 
>> ----
>> Composed on mobile device, with clumsy thumbs and unpredictable autocorrect.
>> From: ksk-rollover <ksk-rollover-bounces at icann.org <mailto:ksk-rollover-bounces at icann.org>> on behalf of Michael StJohns <msj at nthpermutation.com <mailto:msj at nthpermutation.com>>
>> Sent: Tuesday, September 18, 2018 5:04:31 AM
>> To: Matt Larson
>> Cc: ksk-rollover at icann.org <mailto:ksk-rollover at icann.org>
>> Subject: Re: [ksk-rollover] ICANN board meeting result and the Current status of KSK-Rollover
>>  
>> On 9/17/2018 3:57 PM, Matt Larson wrote:
>> > The answer I've given when people ask this question is that we need to 
>> > get through the first rollover and analyze how it goes before we can 
>> > discuss subsequent rollovers. One can imagine that how the first 
>> > rollover goes could have a material effect on the timing of the next one.
>> 
>> This seems like a bad approach given how that we currently have interest 
>> and opportunity in the roll-over that could catalyze planning for a 
>> second roll.  This does not - and should not - need to be single 
>> threaded.    AFAICT, you're going to know most everything you need to 
>> know a few seconds to a few days after you stop signing the the old key.
>> 
>> So - I suggest you pick a date now.  Start planning for the next roll 
>> now.  If your post analysis shows a problem - adapt and overcome and 
>> adjust the dates if you need to.  It's hard to hit a target if you don't 
>> put it on calendar.
>> 
>> Later, Mike
>> 
>> 
>> _______________________________________________
>> ksk-rollover mailing list
>> ksk-rollover at icann.org <mailto:ksk-rollover at icann.org>
>> https://mm.icann.org/mailman/listinfo/ksk-rollover <https://mm.icann.org/mailman/listinfo/ksk-rollover>
>> _______________________________________________
>> ksk-rollover mailing list
>> ksk-rollover at icann.org <mailto:ksk-rollover at icann.org>
>> https://mm.icann.org/mailman/listinfo/ksk-rollover <https://mm.icann.org/mailman/listinfo/ksk-rollover>
> 
> _______________________________________________
> ksk-rollover mailing list
> ksk-rollover at icann.org <mailto:ksk-rollover at icann.org>
> https://mm.icann.org/mailman/listinfo/ksk-rollover <https://mm.icann.org/mailman/listinfo/ksk-rollover>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ksk-rollover/attachments/20180923/fd9eba84/attachment.html>