<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
Stephane,</div>
<div id="bloop_sign_1515348735308130048" class="bloop_sign"><br>
</div>
<div id="bloop_sign_1515348735308130048" class="bloop_sign">On January 6, 2018 at 12:48:15 PM, Stephane Bortzmeyer (<a href="mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>) wrote:</div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">
<span>
<div>
<div></div>
<div>Waiting for data is wise, expecting to have perfect data is just procrastination.</div>
</div>
</span></blockquote>
</div>
<p>Strawman: no one is suggesting we are expecting perfect data. </p>
<div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">
<span>
<div>
<div>Let me add that the # of users behind a broken resolver is not the<br>
best metric: some amount of breakage is unavoidable, the real problem<br>
is how long will it take to fix it.<span class="Apple-converted-space"> </span></div>
</div>
</span></blockquote>
</div>
<p>While I’d agree time to repair is important, I personally think the worrisome part is what happens when previously working resolvers spontaneously stop working until there is manual intervention. I assume the MTTR will be quite low: it isn’t that hard to
turn off DNSSEC validation (as a first step to stop the screaming). The unpleasant scenario is where someone has gone to great lengths to do the right thing and have (someone else set up) a resilient, redundant validating resolver infrastructure supporting
some mission critical application and, because they didn’t know to update the KSK, have that resolver infrastructure simply fall over.</p>
<p>And yes, this is also unmeasurable.</p>
<p>Regards,</p>
<p>-drc</p>
<p><br>
</p>
</div>
</body>
</html>