<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle24
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1978030178;
mso-list-type:hybrid;
mso-list-template-ids:-1492766088 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thanks, Melina. Copying in the correct email address for the GNSO EPDP Team (please see message below). We’ll get your access to the google drive sorted shortly.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Caitlin, Berry and Marika<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">STROUNGI Melina <Melina.STROUNGI@ec.europa.eu><br>
<b>Date: </b>Tuesday, 19 January 2021 at 12:45<br>
<b>To: </b>"gnso-epdp-team-bounces@icann.org" <gnso-epdp-team-bounces@icann.org>, Marika Konings <marika.konings@icann.org><br>
<b>Cc: </b>NEMIGUENTCHEVA - GRAU Velimira <Velimira.GRAU@ec.europa.eu>, "LEWIS-EVANS, Christopher" <Christopher.Lewis-Evans@nca.gov.uk>, "Kapin, Laureen" <LKAPIN@ftc.gov><br>
<b>Subject: </b>[Ext] RE: For your review - feasibility of requiring unique contacts terminology, problem statement and examples<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Dear Caitlin, Berry and Marika,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Just to let you know that I do not appear to have access to the google docs below. I had requested access since yesterday but it doesn’t seem to have been authorized.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">In order to meet today’s deadline, please find some initial questions/comments from my side (copying also my GAC colleagues). If someone could insert them in the doc, where appropriate, it would be great.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo2"><span style="color:#1F497D">On the B&B definition of pseudonymisation, currently defined as:</span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><span style="color:#1F497D">“</span><i><span style="color:#44546A">The same unique string is used for multiple registrations by a unique data subject</span></i><span style="color:black">.”</span><span style="font-family:Wingdings;color:black">à</span><span style="color:black">
</span><span style="color:#BF9000">By ‘multiple registrations’ we mean various registrations within the
<i>same</i> registrar or within <i>multiple</i> registrars/registries?</span><span style="color:#1F497D"> (Melina/GAC)</span><o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:#BF9000">Why do we need a different definition of pseudonymisation as compared to the one in GDPR? What is the added value of such definition?</span><span style="color:#1F497D"> (Velimira/GAC)</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0cm"><span style="color:#1F497D">
</span><o:p></o:p></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo2"><span style="color:#1F497D">According to the description of the specific exercise of Phase 2a, our goal/task is :</span> “<i><span style="color:#1F497D">Addressing the feasibility
of requiring unique contacts to have a uniform anonymized email address across domain name registrations
<u>at a given Registrar</u></span></i><span style="color:#1F497D">”</span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><span style="color:#1F497D">Moreover, according to EPDP Team Recommendation #13: “<i>The EPDP Team recommends that the Registrar MUST provide an email address or a web form
<u>to facilitate email communication with the relevant contact,</u> but MUST NOT identify the contact email address or the contact itself</i>”.
</span><o:p></o:p></p>
<p class="MsoListParagraph"><span style="font-family:Wingdings;color:#1F497D">à</span><span style="color:#BF9000">Doesn’t this mean that the purpose of Phase 2a has been already defined and is limited to contactibility of the registrant? Or can we still consider
including feasibility of correlation or registrations across multiple registrars?
</span><span style="color:#1F497D">(Melina/GAC)</span><o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:#1F497D"> </span><o:p></o:p></p>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo2"><span style="color:#1F497D">ENISA’s report on pseudonymisation techniques states that:</span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><span style="color:#1F497D">‘<i>however, it is often not the choice of pseudonymisation technique utilised for one or two specific identifiers that causes the most problems;
<u>it is the implicit linkability</u> among a set of pseudonyms and other data values that are joined into a more complex data structure’</i>.</span><o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:#BF9000">The issue of linkability is precisely the point that we need to understand and this is precisely why an example of how pseudonymisation would work in the context of registries/registrars would be useful.
We need to understand how this ‘unique string’ would be shared (if shared) across registries/registrars, if and to what extent they already exchange internally personal data and if such linkability would be possible from the side of third parties (if yes,
how? By hacking/leaking the mapping table for example or also in any other way?). It is crucial for the purpose and success of the whole Phase 2a exercise to have a solid understanding on specific technical implementation details. To that end, specific case
examples provided by the contracted parties would be very useful.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Melina </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Friday, January 15, 2021 8:56 PM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] For your review - feasibility of requiring unique contacts terminology, problem statement and examples<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dear EPDP Team,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Per the action items from Thursday’s meeting, the staff support team has tried to pull together terminology, problem statements and examples for your review and input here:
<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1weQemSQ0-884ILbhmR3OLzUWouyGXMKH/edit__;!!DOxrgLBm!XBz7CoN8j7vSaR2hY5PgYVq3RC9NHMZZjjfKklby1k2ywidvwUtJiG8mYMitT8lVxZRm6_k$">
https://docs.google.com/document/d/1weQemSQ0-884ILbhmR3OLzUWouyGXMKH/edit</a>. <o:p>
</o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please provide your group’s input by Tuesday 19 January COB. Also take note of the other documents that have been posted for review as part of the action items coming out of Thursday’s meeting (see
<a href="https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17qLMYb3HC7qGYPQveXbUq5ZSzvedrQ3t8AdVdrRIdrw/edit*gid=0__;Iw!!DOxrgLBm!XBz7CoN8j7vSaR2hY5PgYVq3RC9NHMZZjjfKklby1k2ywidvwUtJiG8mYMitT8lVP5DQ140$">
https://docs.google.com/spreadsheets/d/17qLMYb3HC7qGYPQveXbUq5ZSzvedrQ3t8AdVdrRIdrw/edit#gid=0</a>).
<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>