<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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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:12.0pt;
font-family:"Times New Roman",serif;}
p.gmail-m-3902333198312664094p1, li.gmail-m-3902333198312664094p1, div.gmail-m-3902333198312664094p1
{mso-style-name:gmail-m_-3902333198312664094p1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.gmail-m-3902333198312664094msolistparagraph, li.gmail-m-3902333198312664094msolistparagraph, div.gmail-m-3902333198312664094msolistparagraph
{mso-style-name:gmail-m_-3902333198312664094msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{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><!--[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><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>As I mentioned on Thursday's call, criminal acts on the Internet are not dealt with exclusively by law enforcement. The vast majority of cases are dealt with by private entities, such as in-house investigators at networks, security companies dealing with phishing, private investigators, etc. etc. See also Recital 49.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>So, a fruitful approach to finding commonalities is to begin with the WHAT: WHAT is being investigated and WHAT the goals of the exercise are. In many cases, both a private party and an LE agent may use similar methods, and may be trying to accomplish similar goals. For example see the attached use case from SSAC – both LE and private entities go through these kinds of steps, with similar goals.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Then perhaps comes the issue WHO is looking into it, and what differences that entails. The differences: Law Enforcement has a special status under the law, and may have a special GDPR basis when requesting data. And LE has some powers that private entities cannot deploy – such as arresting people and obtaining search warrants. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>So, I hope the team can consider these ideas at it proceeds.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>All best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>--greg<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> <b>On Behalf Of </b>Mueller, Milton L<br><b>Sent:</b> Wednesday, July 17, 2019 5:40 PM<br><b>To:</b> Janis Karklins <karklinsj@gmail.com><br><b>Cc:</b> gnso-epdp-team@icann.org<br><b>Subject:</b> Re: [Gnso-epdp-team] Materials for agenda item #4<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Janis:<o:p></o:p></span></p><div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>> </span>We are using cases to identify commonalities that would allow us, the Team, <span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>> </span>to develop policy recommendations how to best implement provisions of GDPR.<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I know that. That is exactly why I have proposed to consolidate them in the way I have. It seems to me that the commonalities in the cases I proposed to merge are fairly obvious. If it is a criminal case, for example, it really doesn’t matter a lot whether it is a copyright crime or a trademark crime or a phishing crime, the point is that you will have a government LEA requesting information needed to attribute and capture the criminal, which might be obtained through RDS or through subpoenas or other means. If someone can explain how the use case differs substantially in ways that affect the application of GDPR, let them do so. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Use cases are just a method that allows us to focus our attention to all necessary aspects of future policy recommendations. Therefore, cases need not be ideally drafted but rather represent/outline real life situations and help us understand concerns of different groups. <span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This comment is completely off the mark. Nothing in my document takes issue with any case because it is not “perfectly drafted.” It does not address the drafting at all. It talks about commonalities in their substance. You said: </span>“we should not try to agree on every word in the case, but rather to seek common understanding/ touch-points.<span style='color:#1F497D'>” </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Which is exactly why I proposed to consolidate cases on more general terms. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:#1F497D'>> </span>I would propose that we look at your proposal of use cases merger by e-mail <span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>> </span>exchange and in the meantime, take most supported cases and discuss them <span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>> </span>thru as suggested - thoroughly but quickly.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This is not an acceptable proposal. In effect you are saying that you will ignore my proposed consolidation, and that we will waste time going case by case through all the cases anyway, based on an illegitimate survey that excluded half of the team. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>And when you say “thoroughly but quickly” you are living in a fantasy world. That will not happen. Think of how much time we spent on a single TM case. If the use cases have any value we need carefully consider the problems they pose. That will happen more efficiently if the cases are more general. That is why we need to consolidate the cases. We will raise this issue on the call tomorrow. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:#1F497D'>> </span>I invite other Team members to join the conversation on Milton's proposal.<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>We will have that conversation tomorrow on the call.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Dr. Milton L Mueller<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Georgia Institute of Technology<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>School of Public Policy<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p></div></div></body></html>