<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Helvetica Neue";}
@font-face
{font-family:HelveticaNeue;}
@font-face
{font-family:"Lucida Grande";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Lucida Grande \,serif";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
line-height:150%;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;
mso-fareast-language:EN-CA;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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;
color:black;}
span.reference-text
{mso-style-name:reference-text;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.m-377313414510063557gmail-
{mso-style-name:m_-377313414510063557gmail-;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{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;}
/* List Definitions */
@list l0
{mso-list-id:100926298;
mso-list-template-ids:-2139076412;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:637609653;
mso-list-template-ids:1729268158;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Thanks for the quick reply Stephanie and for your elaboration on proportionality.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Which of the thin data elements do you consider personal information?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Regarding proportionality, it seems to me that it would be more effective to talk about the individual elements
of proportionality in the 4-part test than to talk about proportionality as an abstract term.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="line-height:normal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">
Stephanie Perrin [mailto:stephanie.perrin@mail.utoronto.ca] <br>
<b>Sent:</b> Wednesday, May 31, 2017 3:21 PM<br>
<b>To:</b> Gomes, Chuck <cgomes@verisign.com>; gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">Definitionally, yes. I explained why in my preceding post to this thread. That does not mean we need to protect it, it means we have to examine it in terms of DP law. May I repeat the suggestion
that Canatacci made in Copenhagen in response to a question.....(I forget the precise question he was asked, sorry). If you want to figure out whether you have to protect something or not, do a privacy impact assessment.
</span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">cheers Stephanie</span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">PS I would also like to defend the concept of proportionality. You have to consider it. At the risk of further inflaming this debate, here is something I have written recently which may help
from a definitional perspective:</span><o:p></o:p></p>
<p><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">The proportionality principle is fundamental to the interpretation of European data protection law, although it does not appear in the Directive itself. The usual four part test is:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-CA">there must be a legitimate aim for a measure</span><o:p></o:p></li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-CA">the measure must be suitable to achieve the aim (potentially with a requirement of evidence to show it will have that effect)</span><o:p></o:p></li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-CA">the measure must be necessary to achieve the aim, that there cannot be any less onerous way of doing it</span><o:p></o:p></li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-CA">the measure must be reasonable, considering the competing interests of different groups at hand (</span><span class="reference-text">P Craig and G de Burca,
</span><a href="https://en.wikipedia.org/wiki/EU_Law" title="EU Law"><i>EU Law</i></a><span class="reference-text"> (5th edn OUP 2011) 526).</span><o:p></o:p></li></ul>
<p class="MsoNormal">The concept usually appears in some form in most other data protection law or the interpretation thereof. In Canada, it is expressed in the reasonable person test 5(3) in
<i>The Personal Information Protection and Electronic Documents Act</i> (PIPEDA), which states:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">The purpose of this Part [of the Act] is to establish, in an era in which technology increasingly facilitates the circulation and exchange of information, rules to govern the collection, use and disclosure of personal
information in a manner that recognizes the rights of privacy of individuals with respect to their personal information and the need of organizations to collect, use or disclose personal information
<b>for purposes that a reasonable person would consider appropriate in the circumstances.
</b>[emphasis added] <o:p></o:p></p>
<p class="MsoNormal">The Article 29 group issued a number of recent opinions elaborating on some of the principles in the Directive, and their collective interpretation of them, for the purpose of illuminating the negotiations over the new Regulation on Data
Protection. Of particular interest is their <i>Opinion 06/2014 on the notion of legitimate interest of the data controller under Article 7 of Directive 95/46/EC</i> wherein they explain in some detail how a balancing test can be applied in interpreting the
legitimate interests of the data controller, and the rights of the data subject. In particular they point out that the text of 7(f) means that all relevant interests of the data subject should be taken into account, including but not limited to their fundamental
rights. The following paragraphs underscore the importance of this section, and are particularly applicable to the WHOIS service:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">At a time when increasing imbalance in ‘informational power’, when governments and business organizations alike amass hitherto unprecedented amounts of data about individuals, and are increasingly in the position
to compile detailed profiles that will predict their behavior (reinforcing informational imbalance and reducing their autonomy), it is ever more important to ensure that the interests of the individuals to preserve their privacy and autonomy be protected.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Finally, it is important to note that unlike the case of the controller’s interests, the adjective ‘legitimate’ is not used here to precede the ‘interests’ of the data subjects. This implies a wider scope to the
protection of individuals’ interests and rights. Even individuals engaged in illegal activities should not be subject to disproportionate interference with their rights and interests. For example, an individual who may have perpetrated theft in a supermarket
could still see his interests prevailing against the publication of his picture and private address on the walls of the supermarket and/or on the Internet by the owner of the shop. (p.30)<o:p></o:p></p>
<p><o:p> </o:p></p>
<p class="MsoNormal" style="line-height:normal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:normal"><span style="mso-fareast-language:EN-US">On 2017-05-31 13:45, Gomes, Chuck wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext">Stephanie,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext">Do you consider any of the thin data elements as we have defined them so far to be ‘personal data’?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext">Chuck</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext"> </span><o:p></o:p></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;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif;color:windowtext">
<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Stephanie Perrin<br>
<b>Sent:</b> Wednesday, May 31, 2017 12:45 PM<br>
<b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande ,serif",serif">I think it is a very good summary. One issue which we do not discuss very often is the fact that end users who register a domain name do not understand very well (if at all) what the
implications for their privacy are. A requirement of most data protection law is to provide transparency with respect to what happens to personal data. This job, in my view, has not been tackled by ICANN in the required way. So while I agree with the summary,
it raises the issue, for those of us who do not understand what an SOA record is, what thin data is, how the DNS operates, etc. there is an obligation on ICANN, through its contractual control of the registries and registrars, to provide greater clarity about
how personal data is managed, and what the risks might be for the individual. Simply saying "</span>Let's remember we are talking about the public, open Internet here. Nobody has to participate that doesn't want to, just like if I don't want anyone to see
my license plate number on the road, I don't have to drive a car either. " <span style="font-size:13.5pt">
is not adequate. (Licence registries, by the way, have become private in most jurisdictions because of the risk to registrants, so the chances of being stalked by some nut with road rage have mercifully decreased).
</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;line-height:150%"> Stephanie Perrin<br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On 2017-05-31 11:07, Gomes, Chuck via gnso-rds-pdp-wg wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif">I am open to disagreement, but it seems to me that Jonathan provides a good summary and maybe even a fair conclusion of the extensive discussion that has occurred
on this thread since Tuesday. Rather than continuing the extensive back and forth, which in my assessment is mostly repeating things that have already been said several times, I request that anyone who disagrees with Jonathan’s conclusions to identify what
you disagree with and provide your reasoning.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif">Chuck</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;line-height:150%;font-family:"Calibri",sans-serif">
<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>jonathan matkowsky<br>
<b>Sent:</b> Wednesday, May 31, 2017 10:52 AM<br>
<b>To:</b> Dotzero <a href="mailto:dotzero@gmail.com"><dotzero@gmail.com></a>; Volker Greimann
<a href="mailto:vgreimann@key-systems.net"><vgreimann@key-systems.net></a><br>
<b>Cc:</b> RDS PDP WG <a href="mailto:gnso-rds-pdp-wg@icann.org"><gnso-rds-pdp-wg@icann.org></a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">I think the discussion here reflects confusion between what's available in DNS based on the domain name alone, and Thin Whois data. The fact of whether SOA records or A records may contain PII is a totally separate issue than Thin Whois
data elements.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Based on a domain name alone, one can use it to query DNS for record elements that may contain PII or when combined with other data, can be used to obtain PII. But all of this PII is in the public domain voluntarily by their owners, and
more importantly, is outside the framework of discussion, which is limited to Whois database--not DNS. They are simply not the same.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So the fact that you can get SOA records from the domain name alone begs the question of whether the domain name needs to be protected because when combined with other data elements, can be used to obtain PII.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">But the domain names are publicly available on the internet by virtue of being in the zone files. So the fact you can obtain the domain from thin Whois doesn't make it any more available than it is from the zone files. It is outside the
framework of discussion.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The thin Whois database is not what is making domain names available--so the SOA records for the domain is not a good example, even if someone put PII in that field--as that is an issue of domain names being publicly available together
with DNS. Totally outside the framework of discussion.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The creation date of a domain, the NS records, when the domain was last updated, and the registrar of record are simply not by any stretch of the imagination arguably PII by virtue of Whois. This is information that was voluntarily made
public by virtue of using the public Internet which relies on DNS. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Privacy enthusiasts can use .Onion if they want to. But if they want to use the open Internet, that means some basic data by definition is publicly available in the DNS. If they want to protect their privacy, then they need to use common
sense and not put information they dont want to be made public into the public. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The creation date is as a matter of fact, used as one of several indicators to show a domain engaged in malicious activity was unlikely a victim of being compromised. It is a critical piece of data but also not by any stretch of the wildest
imagination PII. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The principle of proportionality doesn't apply to thin data unless you want to argue it applies to the very fact a domain name record was created in the public Internet. By creating the record, a user has chosen to make that record's existence
public--regardless of whether they use privacy protection or not. If I register my name and birthday as a domain name, it is PII, but PII that I chose to be made publicly available by virtue of creating the domain and putting it into the zone. Does that mean
I am somehow entitled to have all the RFCs re-written for me and for the public Internet to be made private? Of course not. So when people make things public voluntarily by virtue of participating in society, the principles of data protection apply differently.
Let's remember we are talking about the public, open Internet here. Nobody has to participate that doesn't want to, just like if I don't want anyone to see my license plate number on the road, I don't have to drive a car either. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, 31 May 2017 at 16:50 Dotzero <<a href="mailto:dotzero@gmail.com">dotzero@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Translation (per Google translate) of what Volker posted:<br>
<br>
<span class="m-377313414510063557gmail-"><span lang="EN">"On the basis of the ECJ ruling, the factual feature" personal data "of § 12 (1) and (2) TMG in conjunction with § 3 (1) BDSG must be interpreted in accordance with the guidelines: a dynamic IP address
provided by a provider of online media services In the case of access by a person to a website, which is made generally accessible by the provider, constitutes a (protected) personal date for the provider.</span></span><span lang="EN"><br>
<br>
<span class="m-377313414510063557gmail-">The IP address can only be stored as a personal date under the prerequisites of § 15 (1) TMG. This provision is to be applied in accordance with the provisions of Article 7 (f) of Directive 95/46 EC, as interpreted by
the Court of Justice, to the effect that a provider of on-line media services may collect personal data of a user without the consent of the user of the services To the extent that their collection and use is necessary to ensure the general functioning of
the services. However, there is a need to balance the interests and the basic rights and freedoms of the users. "</span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Wed, May 31, 2017 at 9:47 AM, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p>Why, just this month the German Bundesgerichtshof confirmed this in a review of a decision of the state court Berlin ( Az. VI ZR 135/13):<o:p></o:p></p>
<p><a href="http://juris.bundesgerichtshof.de/cgi-bin/rechtsprechung/document.py?Gericht=bgh&Art=pm&Datum=2017&Sort=3&nr=78289&pos=0&anz=74" target="_blank">http://juris.bundesgerichtshof.de/cgi-bin/rechtsprechung/document.py?Gericht=bgh&Art=pm&Datum=2017&Sort=3&nr=78289&pos=0&anz=74</a><o:p></o:p></p>
<p>It followed the decision of the European Court from October last year:<o:p></o:p></p>
<p>C-582/14, NJW 2016, 3579<o:p></o:p></p>
<p>The German explanation:<o:p></o:p></p>
<p><i>"Auf der Grundlage des EuGH-Urteils ist das Tatbestandsmerkmal "personenbezogene Daten" des § 12 Abs. 1 und 2 TMG in Verbindung mit § 3 Abs. 1 BDSG richtlinienkonform auszulegen: Eine dynamische IP-Adresse, die von einem Anbieter von Online-Mediendiensten
beim Zugriff einer Person auf eine Internetseite, die dieser Anbieter allgemein zugänglich macht, gespeichert wird, stellt für den Anbieter ein (geschütztes) personenbezogenes Datum dar.
</i><o:p></o:p></p>
<p><i>Als personenbezogenes Datum darf die IP-Adresse nur unter den Voraussetzungen des § 15 Abs. 1 TMG gespeichert werden. Diese Vorschrift ist richtlinienkonform entsprechend Art. 7 Buchst. f der Richtlinie 95/46 EG – in der Auslegung durch den EuGH – dahin
anzuwenden, dass ein Anbieter von Online-Mediendiensten personenbezogene Daten eines Nutzers dieser Dienste ohne dessen Einwilligung auch über das Ende eines Nutzungsvorgangs hinaus dann erheben und verwenden darf, soweit ihre Erhebung und ihre Verwendung
erforderlich sind, um die generelle Funktionsfähigkeit der Dienste zu gewährleisten. Dabei bedarf es allerdings einer Abwägung mit dem Interesse und den Grundrechten und -freiheiten der Nutzer."</i><o:p></o:p></p>
<p>Hope this helps.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">Am 31.05.2017 um 15:38 schrieb Paul Keating:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>See: recent Europrean court decisions on IP addresses as PII.<o:p></o:p></p>
</blockquote>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Can you please provide the citations? I a-m not aware of any court decision issuingsuch a broad ruling. <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">Paul <br>
<br>
Sent from my iPad<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 31 May 2017, at 12:20, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p>In some cases the ability to use data set A in combination with data set B to enable one to identify an individual turns data set A into PII.
<o:p></o:p></p>
<p>See: recent Europrean court decisions on IP addresses as PII.<o:p></o:p></p>
<p>I am with you in viewing thin data as rather unlikely to be defined as PII, but depending on how this data is used it is not inconceivable that it may be found to contain PII depending on the use. Unlikely, but not impossible.<o:p></o:p></p>
<p>Volker<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">Am 30.05.2017 um 23:40 schrieb Paul Keating:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Im sorry but i don't see the logic here (or the legal constraint)<o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">Privacy laws protect personal data of INDIVIDUALS. They do t protect non-personal data or data from non-individuals.<o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">Nothing on the list below is personal data. And no e of the principles given by Natalie apply.<o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">The fact that i could use the data to obtain other data is irrelevant. I can use a car to rob a bank but that itself is not a reason to restrict access to automobiles.<o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151AppleMailSignature">
<p class="MsoNormal">Me thinks you are trying to create a scarcity for some reason.<br>
<br>
Sent from my iPad<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 30 May 2017, at 23:22, Chris Pelling <<a href="mailto:chris@netearth.net" target="_blank">chris@netearth.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">ok - a thought :</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Thin data includes nameservers, being able to
<strong><u><span style="font-family:"Arial",sans-serif">mass</span></u></strong> collect thin data gaining NS information then allows you to do a DIG of a SOA record on the DNS service to gain the email address of the hostmaster :
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Some examples (radomly picked from the list) :</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><a href="http://gmail.com" target="_blank">gmail.com</a> :</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">SOA <a href="http://ns1.google.com" target="_blank">
ns1.google.com</a>. <a href="http://dns-admin.google.com" target="_blank">dns-admin.google.com</a>. 157458041 900 900 1800 60<br>
<a href="http://netearthone.com" target="_blank">netearthone.com</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">SOA <a href="http://ns1.netearth.net" target="_blank">
ns1.netearth.net</a>. <a href="http://root.netearthone.com" target="_blank">root.netearthone.com</a>.
<a href="tel:%28201%29%20609-0201" target="_blank">2016090201</a> 14400 3600 1209600 86400</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><a href="http://law.es" target="_blank">law.es</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">SOA <a href="http://ns1.eurodns.com" target="_blank">
ns1.eurodns.com</a>. <a href="http://hostmaster.eurodns.com" target="_blank">hostmaster.eurodns.com</a>.
<a href="tel:%28201%29%20606-1402" target="_blank">2016061402</a> 43200 7200 1209600 86400</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><a href="http://riskiq.net" target="_blank">riskiq.net</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">SOA <a href="http://ns-1754.awsdns-27.co.uk" target="_blank">
ns-1754.awsdns-27.co.uk</a>. <a href="http://awsdns-hostmaster.amazon.com" target="_blank">
awsdns-hostmaster.amazon.com</a>. 1 7200 900 1209600 86400</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Now as you can see - those above examples allow you to get (or build) an email list. Most will normally point to the providers service, but, some that are DIY'ing their hosting, it might not
be.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Kind regards,<br>
<br>
Chris</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Arial",sans-serif">
<hr size="3" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif">From: </span>
</b><span style="font-family:"Arial",sans-serif">"allison nixon" <<a href="mailto:elsakoo@gmail.com" target="_blank">elsakoo@gmail.com</a>><br>
<b>To: </b>"nathalie coupet" <<a href="mailto:nathaliecoupet@yahoo.com" target="_blank">nathaliecoupet@yahoo.com</a>><br>
<b>Cc: </b>"gnso-rds-pdp-wg" <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Sent: </b>Tuesday, 30 May, 2017 21:52:32<br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">so can you name one specific example of how someone could abuse thin data?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">On Tue, May 30, 2017 at 4:50 PM, nathalie coupet via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>> wrote:</span><o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Abuse</span></b><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222"> is the
improper usage or treatment of an </span><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""><a href="https://en.wikipedia.org/wiki/Entity" target="_blank" title="Entity"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#0B0080;background:white">entity</span></a></span><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">,
often to </span><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""><a href="https://en.wikipedia.org/wiki/Distributive_justice" target="_blank" title="Distributive justice"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#0B0080;background:white">unfairly</span></a></span><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222"> or
improperly gain benefit. In our context, abuse is the improper usage of WHOIS/RDS to unfairly or improperly gain access to information or to game the system. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Here are some of the overarching principles which should guide us when building RDS: </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287894">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">DATA LIFECYCLE PRIVACY PRINCIPLE PROTECTION MEASURE</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287897">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Collection Proportionality and purpose specification Data minimisation, Data
quality</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287900">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Storage Accountability, Security measures, Sensitive data Confidentiality, Encryption,
Pseudonomisation</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287903">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Sharing and processing Lawfulness and fairness, Consent, Right of access Data access control, Data leakage prevention</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Deletion Openness, Right to erasure Retention, Archival,
Erasure</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">If such principles are not respected, ICANN will be liable. Consumers don't need to have all the thin data when making
a query. This could protect them and enable them to have access to the RDS without raising much opposition. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906">
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:"Arial",sans-serif;color:#222222">Now, we could discuss the possibility for broader query types. These principles would still apply, but would be contextualized
in order to take into account new sets of parameters for each broader query. By increasing granularity as much as possible, while applying these aformentioned principles, we just might find a way to accomodate everyone. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287435">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287433">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue"">Nathalie </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif">On Tuesday, May 30, 2017 4:00 PM, John Horton <<a href="mailto:john.horton@legitscript.com" target="_blank">john.horton@legitscript.com</a>> wrote:</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
<div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093">
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#444444">I was going to reply to Natalie's email as well, but Paul's comments capture my thoughts, so:
<b>+1. </b></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"><br clear="all">
</span><o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#073763">John Horton<br>
President and CEO, LegitScript</span><span style="font-family:HelveticaNeue"> </span>
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif;color:#444444">Follow</span></b><b><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif;color:#0B5394">
</span></b><b><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif">Legit</span></b><b><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif;color:#0B5394">Script</span></b><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif">:
<a href="http://www.linkedin.com/company/legitscript-com" target="_blank"><span style="color:#CC0000">LinkedIn</span></a> | <a href="https://www.facebook.com/LegitScript" target="_blank"><span style="color:#6AA84F">Facebook</span></a> | <a href="https://twitter.com/legitscript" target="_blank"><span style="color:#674EA7">Twitter</span></a>
| </span><u><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif;color:#FF9900"><a href="http://blog.legitscript.com/" target="_blank">Blog</a></span></u><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif">
|</span><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif;color:#FF9900"> <a href="https://plus.google.com/112436813474708014933/posts" target="_blank">Google+</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;line-height:150%;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">On Tue, May 30, 2017 at 12:57 PM, Paul Keating <<a href="mailto:paul@law.es" target="_blank">paul@law.es</a>> wrote:</span><o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093yqt77589">
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">Natalie,</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">Thank you for the email. Im copying the list because i see others have replied to your comment.</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">I strenuously object to the concept. We are discussing THIN DATA ONLY HERE. Unless someone can explain to me why any of this data set has privacy concerns this is a non-issue.
I would certainly appreciate someone explaining what, if any, privacy issues are perceived to be at issue here.</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">Moreover, while you suggest that the idea escapes the need to declare a purpose, it does nothing but reinforce a subjective criteria based system in which the declared purpose
is used to somehow limit the data being retrieved.</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">If i am missing something please let me know. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"><br>
Paul</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"><br>
Sent from my iPad</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:HelveticaNeue"><br>
On 30 May 2017, at 21:08, nathalie coupet via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>> wrote:</span><o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue"">Hi Paul,</span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue"">In the context of thin data, in view of the opposition of some to allow unauthenticated access to all the thin data, the principle of
proportionality serves as an over-arching principle at this particular phase in our work in order to protect data from abuse while not restricting access. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue"">Thin data must be proportionate to the query, be useful for that particular query. All and any other thin data foreign to this query should
not be shared. This principle potentially avoids having to resort to 'legitimate purposes' which cannot be verified for unauthenticated access. </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239558">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239560">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue"">Nathalie </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-size:10.0pt;line-height:150%;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif">On Tuesday, May 30, 2017 2:44 PM, "Gomes, Chuck via gnso-rds-pdp-wg" <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>> wrote:</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
<div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320">
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue">Because Nathalie was the originator and was unable to speak on the call, I encourage her to describe the nature of the issue on this thread.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue">Chuck</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue"> </span><a name="m_-377313414510063557_m_-798267218685221"></a><o:p></o:p></p>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320yqt95202">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue">From:</span></b><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue">
<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann. org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg- bounces@icann.org</a>]
<b>On Behalf Of </b>Paul Keating<br>
<b>Sent:</b> Tuesday, May 30, 2017 2:17 PM<br>
<b>To:</b> Lisa Phifer <<a href="mailto:lisa@corecom.com" target="_blank">lisa@corecom.com</a>>; RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">Im sorry to have missed the call but had a client engagement.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">Can someone briefly describe the nature of the issue?</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">Thanks</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">Paul</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue">From:
</span></b><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue"><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@ icann.org</a>> on behalf of Lisa Phifer <<a href="mailto:lisa@corecom.com" target="_blank">lisa@corecom.com</a>><br>
<b>Date: </b>Tuesday, May 30, 2017 at 7:52 PM<br>
<b>To: </b>RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>[gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">All, per today's call action item:<br>
<br>
<b>Action Item: Nathalie Coupet and any other WG members who wish to do so to propose to the WG list a new principle on proportionality for "thin data." All WG members to comment on that proposed principle in advance of next call.<br>
<br>
</b>we are starting a new thread here which anyone may reply to if they wish to propose (or respond to) a new principle on proportionality for "thin data" access.<br>
<br>
Best, Lisa</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;line-height:150%;font-family:HelveticaNeue">______________________________ _________________ gnso-rds-pdp-wg mailing list
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/ listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<div id="m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yqt24053">
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">______________________________ _________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/ listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue">______________________________ _________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/ listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"><br>
______________________________ _________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/ listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:HelveticaNeue"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><br>
<br clear="all">
<br>
-- </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">_________________________________<br>
Note to self: Pillage BEFORE burning.</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</div>
</blockquote>
</blockquote>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">jonathan matkowsky, vp - ip & head of global brand threat mitigation<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"> <o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="line-height:normal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>