<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; }
h3 { font-size: 1.1em; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
a { color: #3983C4 }
blockquote a { color: #777777; }
blockquote blockquote a { color: #999999; }
blockquote blockquote blockquote a { color: #BBBBBB; }
math[display="inline"] > mrow { padding:5px; }
div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">Has there been <em>any</em> feedback on the changes so far? Did the increase in the DNSKEY RR set trigger anything?</p>
<p dir="auto">Is there any advice we can give to resolver ops in a month or so? Like check your trust anchor it should now contain <blob>?</p>
<p dir="auto">—Olaf</p>
<p dir="auto">On 26 Jul 2017, at 7:08, Edward Lewis wrote:</p>
<p dir="auto"></div>
<div class="plaintext"><blockquote><p dir="auto">Wanted to "mark the occasion" and ask if there are any further concerns?<br>
<br>
RFC-5011 following servers ought to be about halfway to trusting KSK-2017 about this day, with the add-hold expiring around August 11, give or take time zones and when probing happened.<br>
<br>
That's halfway to "trusting" the key. There's still 2.5 more months (October 11) until signatures by KSK-2017 appear.<br>
<br>
_______________________________________________<br>
ksk-rollover mailing list<br>
ksk-rollover@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/ksk-rollover">https://mm.icann.org/mailman/listinfo/ksk-rollover</a></p>
</blockquote></div>
<div class="markdown"></p>
</div>
</body>
</html>