<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</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 All,</div>
<div><br>
</div>
<div>Please find attached for your review version 2.2. of the draft transition plan. Note that in this version:</div>
<ul>
<li>All redline changes from the previous version have been accepted to facilitate review of the new content.</li><li>As previously indicated, staff has provided proposed language for sections III.A.1.4.1, III.A.1.4.2 and III.A.1.4.3. Note that we have organised this content using the following approach: 1) Describe background / current state, 2) Describe the issues identified
as a result of the transition and rationale for changes, if any, to address the issues identified, 3) Current language / requirements and proposed revised language / requirements. The CWG may want to consider whether it would be helpful if the Design Teams
would follow a similar approach as they develop their proposed content for the draft transition proposal as it will facilitate consistency across the document as well as guide DT’s with regard to the information that is expected to be provided by the DT. </li><li>A proposed appendix A has been added which outlines the proposed changes to the current requirements for DNSSEC in the Authoritative Root Zone.</li></ul>
<div>We note that comments have been submitted by Andrew in relation to sections I and II. Staff is reviewing these comments and will aim to incorporate these in the next iteration of the draft proposal, unless there are any concerns or comments with regard
to the proposed changes (if so, please share those with the mailing list).</div>
<div><br>
</div>
<div>To facilitate your review, I’ve attached both a clean and redline version.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Marika</div>
<div> </div>
</body>
</html>