<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>Dear RSSAC Caucus, </div><div><br></div><div> Thank you for your feedback on the TTL document. The editors studied all the comments received from RSSAC Caucus, RSSAC and from ICANN on this report, and addressed all of them. </div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0);"><div><br></div><div>Attached please find a revised version of the document. The major changes in this revision are: </div><div><br></div><div> 1) moved the problem statement to the introduction to properly motivate the discussion. </div><div> 2) added a section describing lab experiment to prove the signature validity problem can really happen.</div><div> 3) explained the (rare) conditions under which signature validity problems could occur.</div><div> 4) added caucus member’s input on mitigation options. </div><div> 5) editorial changes through out the document for factual corrections. </div><div><br></div><div> Please see four documents: </div><div><br></div><div> 1) clean, REDLINE (word and PDF) version of the latest advisory. </div><div> 2) a document listing how each comments are addressed by the editors. </div><div><br></div><div> With that, thank you very much for your input. Please let us know if there are any additional feedback that you have on this document. Duane will solicit further feedback from root server operators. Our goal is to finalize this document by IETF 93 and send it to RSSAC for action. </div><div><br></div><div>Best, </div><div>Steve</div></div></span></body></html>