<html xmlns:v="urn:schemas-microsoft-com:vml" 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:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-compose;
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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><div id=divtagdefaultwrapper><p class=MsoNormal>Hello All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for another productive small team meeting yesterday. As we move forward with drafting a report to the GNSO Council regarding our work in connection with Assignments 1 & 2, and how that may impact our future working regarding Assignments 3 & 4, I wanted to share some information that may be of interest to the members within the Group.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attached is a slide deck that Hans Seeuws from EURid said I could share with the Accuracy Scoping Working Group regarding EURid’s work to increase the accuracy of registrant data through their KYC initiative. This deck is based upon a similar presentation that Hans gave at a recent CENTR meeting. While I fully support the work that EURid is doing in this area, I have personally advocated the use of an alternative term given than KYC implies a very heightened level of verification on par with the banking system. I have often used KYR (Know Your Registrant). I believe the European ccTLDs have been doing some ground breaking work in the area of developing proportionate registrant verification practices and I think there are some lessons to be learned and perhaps some best practices to be implemented from our European ccTLD colleagues.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I know there was a previous discussion regarding how the cross field validation requirements contained in the 2013 RAA have never been implemented because of perceived cost issues. However, I think this provides an interesting data point on how some in the domain name ecosystem are engaged in some creative thinking. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As we move forward with potential surveys to Registrars involving NON PII data, I came across this provision in the Nominet Registrar Accreditation Agreement that may be another data point for our consideration. According to the Nominet’s RRA, Paragraph E.1.4 of Schedule 1 in the RRA states that “that you [Registrar] have a process in place for data quality validation, which complies with our Data Quality Policy, and which is auditable by us [Nominet].”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Per Nominet’s Data Quality Policy, for Accredited Channel Partner Tag holders, these must be “written processes.” See <a href="https://nominet.uk/wp-content/uploads/2018/09/13094001/Data-Quality-Policy.pdf">https://nominet.uk/wp-content/uploads/2018/09/13094001/Data-Quality-Policy.pdf</a> Therefore, I think it would be highly informative to know how these written Data Quality Processes stack up against the 2013 RAA Accuracy requirements. <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>Michael<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>