<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear Accuracy Scoping Team colleagues, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Per the group's request from a couple of weeks ago, please find below some comments/response from ICANN Org/Compliance to the Gap Analysis Proposal D re potential Registrar Audit(s). ICANN Org and Compliance colleagues would be happy to
answer further questions the group might have after reviewing and discussing further.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in">Brian<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Comments from ICANN Org / ICANN Contractual Compliance:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i><span style="color:#2F5597">ICANN Contractual Compliance (Compliance) may proceed with registrar audit(s) that confirm compliance with Registration Data accuracy obligations within the Registrar Accreditation Agreement (RAA) and Whois
Accuracy Program Specification of the RAA, including validation and verification processes, without review of nonpublic personal data in registration data. This is consistent with Compliance’s last full registrar audit.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="color:#2F5597"> </span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="color:#2F5597">Compliance may consider taking additional steps to audit compliance with accuracy requirements, such as obtaining and reviewing records that contain personal data in registration data and specifically demonstrate
verification and validation of redacted registration data. However, prior to taking any further steps in this area that would involve the processing of redacted registration data collected by registrars, ICANN org believes it should solicit guidance from the
European data protection authorities prior to taking any further steps in this area, as discussed with the community at ICANN73.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="color:#2F5597"> </span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="color:#2F5597">Once the criteria for the registrar audit is established, Compliance is typically able to initiate an audit within 2 months. Compliance would first need to establish the content of the audit itself, selection
criteria, and process (e.g. single audit, batches, continuous, etc.). If registration data must be obtained through sources other than public Registration Data Director Services (RDDS), for e.g. the contracted party, data escrow provider(s), etc. this may
impact the timing of initiating or completing an audit.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Marika Konings <marika.konings@icann.org><br>
<b>Date: </b>Tuesday, April 19, 2022 at 12:20 AM<br>
<b>To: </b>"gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org><br>
<b>Subject: </b>[GNSO-Accuracy-ST] Thursday's meeting to continue development of details of proposals with those interested<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Similar to last week’s meeting, coming Thursday’s meeting will be dedicated to working on the details of the different proposals as outlined here (<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit?pli=1__;!!PtGJab4!oqnpzS9w8YYoLUhpldMVfkw6nHDG1WmASgACjXQKw1xAC4r8ZBQTtPfBaw5YsPnUhI3EyG60wg$">https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit?pli=1
[docs.google.com]</a>). Special thanks to Sarah for providing initial responses that the group reviewed and discussed during last week’s meeting. The staff support team has accepted these responses and added in suggestion mode some additional points and questions
that were raised during last week’s discussion (see page 12 & 13). If there is anything we missed, or any further input you would like to see considered, please add this to the document in advance of Thursday’s meeting.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For Thursday’s meeting, we’ll start off with proposal E and then circle back to proposal A, and possibly D if a response is received from ICANN org in relation to the questions that the group posed concerning a possible Registrar Audit.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Caitlin, Berry and Marika<o:p></o:p></p>
</div>
</body>
</html>