<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">On Jan 24, 2017, at 8:38 PM, Paul Vixie <<a href="mailto:vixie@tisf.net" class="">vixie@tisf.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">On Tuesday, January 24, 2017 5:11:25 PM PST Jim Reid wrote:</div><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">> I suggest adding ISC to this hall of shame for implementing and deploying DLV. :-)</div><p class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;"> </p><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">if you think the root or .com would ever have been signed without the threat of dlv, then can i interest you in this fine bridge, which while you can't take it home with you, can be yours for the low low price of a nickel.</div><p class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;"> </p><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">no :-) here.</div><p class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;"> </p><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">-- </div><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;">P. Vixie</div><span id="cid:859209F6-9995-43E2-8F62-9CE929BE196A" class=""></span></div></div></blockquote></div></div></div></blockquote><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="" style="white-space: pre-wrap; font-family: 'Source Code Pro'; font-size: 13px; margin: 0px;"><br class=""></div></div></div></blockquote></div></div></div></div><div><blockquote type="cite" class=""><div class="">On Jan 25, 2017, at 6:56 AM, David Conrad <<a href="mailto:drc@virtualized.org" class="">drc@virtualized.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yes, it would have, at least for the root.<div class=""><br class=""></div><div class="">In all the discussions I had with various folks about signing the root within ICANN, there was no mention of DLV that I can recall (and I was somewhat sensitive to the topic).</div><div class=""><br class=""></div><div class="">What caused the root to be signed was the Kaminsky vulnerability.</div><div class=""><br class=""></div><div class="">I obviously can't speak for .COM. </div></div></div></blockquote><br class=""></div><div>I worked at Verisign for a very long time, including when .com was signed. While I obviously can't speak for them now, either, I suspect that if you were to ask anyone who was there at the time, their answer would be that DLV was not at all a factor in the decision to sign .com.</div><div><br class=""></div><div>Matt</div><div><br class=""></div></body></html>