<!DOCTYPE html><html><head><title></title><style type="text/css">#qt p.qt-MsoNormal{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;font-size:11pt;font-family:"Calibri", sans-serif;}
#qt a:link{color:blue;text-decoration-line:underline;text-decoration-style:solid;text-decoration-color:currentcolor;text-decoration-thickness:auto;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Scenario 5<br></div><div>Given ICANN's ORG's responsibility for escrowed data and being beneficial to the data subject, it makes more sense for ICANN to perform an audit with its escrow partners who act as data processors for ICANN ORG. <br></div><div>Such an audit can be performed much easier as it involves fewer actors.<br></div><div><br></div><div>Best, <br></div><div>Theo <br></div><div><br></div><div>On Wed, Mar 15, 2023, at 1:55 PM, Nathalie Peregrine via council wrote:<br></div><blockquote type="cite" id="qt" style="overflow-wrap:break-word;"><div class="qt-WordSection1"><p class="qt-MsoNormal"><span style="" lang="EN-US">Dear councilors,</span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US"> </span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US">Please find attached the correspondence from ICANN org to Sebastien in response to his letter dated 1 December 2022 requesting updates from ICANN org on outstanding issues related to
registration data accuracy and the pending work of the Registration Data Accuracy Scoping Team.</span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US"> </span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US">This will be posted shortly on the GNSO Correspondence page.</span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US"> </span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US">Thank you!</span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US"> </span><br></p><p class="qt-MsoNormal"><span style="" lang="EN-US">Nathalie</span><br></p><p class="qt-MsoNormal"><span style=""> </span><br></p><div style="border-right-color:currentcolor;border-right-style:none;border-right-width:medium;border-bottom-color:currentcolor;border-bottom-style:none;border-bottom-width:medium;border-left-color:currentcolor;border-left-style:none;border-left-width:medium;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1;border-top-color:rgb(181, 196, 223);border-top-style:solid;border-top-width:1pt;padding-top:3pt;padding-right:0cm;padding-bottom:0cm;padding-left:0cm;"><p class="qt-MsoNormal"><b><span style="color:black;" lang="EN-US"><span class="size" style="font-size:12pt;">From: </span></span></b><span style="color:black;" lang="EN-US"><span class="size" style="font-size:12pt;">Correspondence <correspondence@icann.org><br> <b>Date: </b>Tuesday, 14 March 2023 at 17:01<br> <b>To: </b>"Sebastien@registry.godaddy" <Sebastien@registry.godaddy><br> <b>Cc: </b>Brian Gutterman <brian.gutterman@icann.org>, Amy Bivins <amy.bivins@icann.org>, Nathalie Peregrine <nathalie.peregrine@icann.org><br> <b>Subject: </b>[Ext] Registration Accuracy Data Scoping Team Request [ ref:_00D1aY7OU._5001P1VAdzl:ref ]</span></span></p></div><div><p class="qt-MsoNormal"><span lang="EN-US"> </span><br></p></div><div><div><p class="qt-MsoNormal"><span style="border-top-color:windowtext;border-top-style:solid;border-top-width:1pt;border-right-color:windowtext;border-right-style:solid;border-right-width:1pt;border-bottom-color:windowtext;border-bottom-style:solid;border-bottom-width:1pt;border-left-color:windowtext;border-left-style:solid;border-left-width:1pt;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;"><img style="width:0.3333in;height:0.3333in;" id="qt-_x0000_i1026" alt="Image removed by sender." width="32" height="32"></span></span></span><span lang="EN-US"><br> <br> <br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">Dear Sebastien Ducos,</span></span><span lang="EN-US"><br> </span></p></div><div><p class="qt-MsoNormal"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">Please find attached a letter from Brian Gutterman at ICANN. This letter will be posted shortly to the ICANN Correspondence page (</span></span><span lang="EN-US"><a href="https://www.icann.org/resources/pages/correspondence"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">https://www.icann.org/resources/pages/correspondence</span></span></a></span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">).</span></span><span lang="EN-US"><br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;"> </span></span><span lang="EN-US"><br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">Please submit any questions you may have about this message to </span></span><span lang="EN-US"><a href="mailto:correspondence@icann.org"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">correspondence@icann.org</span></span></a></span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">.</span></span><span lang="EN-US"><br> <br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">Best Regards,</span></span><span lang="EN-US"><br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">Michael Kovach</span></span><span lang="EN-US"><br> <br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:9pt;">The Correspondence Team<br> Internet Corporation for Assigned Names and Numbers (ICANN)<br> correspondence@icann.org<br> <br> www.icann.org</span></span><span lang="EN-US"><br> <br> </span><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:6pt;">ref:_00D1aY7OU._5001P1VAdzl:ref</span></span><span lang="EN-US"></span></p></div><p class="qt-MsoNormal" style=""><span lang="EN-US"> </span><br></p></div><p class="qt-MsoNormal"><span style="border-top-color:windowtext;border-top-style:solid;border-top-width:1pt;border-right-color:windowtext;border-right-style:solid;border-right-width:1pt;border-bottom-color:windowtext;border-bottom-style:solid;border-bottom-width:1pt;border-left-color:windowtext;border-left-style:solid;border-left-width:1pt;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm;" lang="EN-US"><img style="width:0.3333in;height:0.3333in;" id="qt-_x0000_i1025" alt="Image removed by sender." width="32" height="32" border="0"></span><span lang="EN-US"><br><br></span></p></div><div>_______________________________________________<br></div><div>council mailing list<br></div><div><a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br></div><div><a href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a><br></div><div><br></div><div>_______________________________________________<br></div><div>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>Gutterman to Ducos 14Mar23.pdf<br></li></ul></blockquote><div><br></div></body></html>