<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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi –<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think this is a very important issue that should be called out in the Initial Report. The Purpose O discussion should be written to note the concern regarding ICANN ‘s ability to continue publishing for the reports from the Accuracy
Reporting System in the manner that was possible before May 25<sup>th,</sup> and to note OCTO’s use of the data before May 25<sup>th</sup>, and to ask the question of whether the purposes listed in the report enable or should enable this continued use by
OCTO and by ICANN.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Margie<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-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca><br>
<b>Date: </b>Thursday, November 15, 2018 at 8:03 PM<br>
<b>To: </b>Benedict Addis <bee@theale.co.uk>, Thomas Rickert <thomas@rickert.net><br>
<b>Cc: </b>GNSO EPDP <gnso-epdp-team@icann.org>, Emily Taylor <emily@emilytaylor.eu><br>
<b>Subject: </b>Re: [Gnso-epdp-team] [Ext] Purpose O (Research) - informal small group<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Somewhat related to OCTO's use, as a result of the first WHOIS Review ICANN instituted an Accuracy Reporting System to track WHOIS accuracy. The program has been on hold since May and we need to consider what can be done to re-institute
it. With the general lack of WHOIS visibility, this program is even more important. I mentioned this in LA, but it seems to have dropped between the cracks.<br>
<br>
Alan<br>
<br>
At 15/11/2018 09:54 PM, Benedict Addis wrote:<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">* Team copied *<br>
<br>
Dear Thomas,<br>
<br>
Thank you for speaking with me yesterday about the Research purpose. In answer to your second question, I have clarified in the document that the registry will pseudonymise registration data before it is transmitted to ICANN.<br>
<br>
Regarding your first question, I have spoken to both current and former members of the OCTO team. They have provided the following additional input:<br>
<br>
<i>"Octo used registration data as part of LE [Law Enforcement] training.<br>
<br>
Like other opsec [operational security] practitioners we used reg[istration] data when collaborating with public/private sector investigators.<br>
<br>
We also used it when we were invited to work with Compliance on a particular complaint."<br>
</i><br>
and<br>
<br>
<i>"[we] used full whois when we initiated our own investigations but that activity was self-directed not explicitly part of SSR role and remit. I also used whois to report phishing and brand infringements against ICANN.<br>
<br>
Lastly I used whois as part of research into bulk registrations and other consensus policy or registrar practices that had undesirable or unintended consequences."<br>
</i><br>
I should note that prior to 25th May, OCTO used public whois data. Since then, this work is on hold.<br>
<br>
Lastly, I’m sorry that this document is reaching you at the 11th hour. I have been waiting for guidance from ICANN before sending it, which was requested over a month ago.<br>
<br>
Best,<br>
Benedict.<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">On 5 Nov 2018, at 21:36, Thomas Rickert <<a href="mailto:thomas@rickert.net">thomas@rickert.net</a>> wrote:<br>
<br>
Thanks, Benedict! <br>
<br>
Let me reiterate my input, which I think needs to make its way into the document or in a covering note. To be clear, I am not questioning that we need to look into ways to enable ICANN to do research, but I am still unclear as to what their requirements are
do to research. <br>
<br>
*<br>
More input from those conducting the research is required, especially on the questions:<br>
What data is actually required for research purposes?<br>
Would it not be sufficient to have pseundonymized data? <br>
*<br>
<br>
Best,<br>
Thomas<br>
<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Am 05.11.2018 um 22:29 schrieb Berry Cobb <<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>>:<br>
<br>
<a name="x__MailEndCompose"></a>Hi Benedict,<br>
<br>
Thank you for the update. I think it will be important to get this to the list for the full group’s consideration. Afterwards, I’ll make a few cosmetic updates and post on the wiki.<br>
<br>
Thank you.<br>
<br>
B<br>
<br>
<br>
Berry Cobb<br>
GNSO Policy Consultant<br>
@berrycobb<br>
<br>
<b>From:</b> Benedict Addis [<a href="mailto:bee@theale.co.uk">mailto:bee@theale.co.uk</a>]
<br>
<b>Sent:</b> Monday, November 5, 2018 15:38<br>
<b>To:</b> Berry Cobb<br>
<b>Cc:</b> farzaneh badii; Marika Konings; Thomas Rickert; Anderson, Marc; Emily Taylor;
<a href="mailto:matt@brandsight.com">matt@brandsight.com</a>; Amr Elsadr; Kurt Pritz; Caitlin Tubergen<br>
<b>Subject:</b> Re: [Ext] Purpose O (Research) - informal small group<br>
<br>
Dear Berry,<br>
<br>
Thanks for your message, and thank you everyone for your time.<br>
<br>
I’ve updated the workbook to incorporate the feedback from Farzaneh and Thomas.<br>
<br>
Essentially, I have clarified that the registry will pseudoymise registration data before it is transmitted to ICANN.<br>
<br>
Best,<br>
Benedict.<o:p></o:p></p>
</blockquote>
</blockquote>
<p class="MsoNormal"><br>
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document;<br>
name="Purpose O - Data_Elements_Processing_Workbook - 5 November"<br>
2018_clean.docx"<br>
Content-Description: Purpose O - Data_Elements_Processing_Workbook - 5<br>
November 2018_clean.docx<br>
Content-Disposition: attachment;<br>
filename="Purpose O - Data_Elements_Processing_Workbook - 5 November"<br>
2018_clean.docx"; size=46244; creation-date="Fri, 16 Nov 2018 02:54:40 GMT";<br>
modification-date="Fri, 16 Nov 2018 02:54:40 GMT"<br>
Content-ID: <40D88555A48696478B1752C828D12DFF@CANPRD01.PROD.OUTLOOK.COM><o:p></o:p></p>
</blockquote>
</div>
</body>
</html>