<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Briefly --</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Thank you to Andrew Sullivan (in particular) for reminding us that an essential purpose of this data is the operability of the Internet. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If court decisions seem to (or can be used to) interfere with that operability, we need to look for technical, legal and/or policy methods to overcome that interference. Unquestioning submission to the most oppressive interpretation of a law or a court decision is bad law/business/policy.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">We're not trying to design a privacy-prioritized RDS (much less DNS, much less Internet). We're trying to design (or protect) an operabiliity-prioritized Internet and one that prioritizes security, stability, resiliency and trust. Some privacy concepts are consistent with those goals, others are anathema to them. Following applicable laws is also a basic concept, but over-adherence to the law makes about as much sense as avoiding skin cancer by hiding under your bedcovers.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I think an attempt to import the principle of proportionality and apply it to thin data falls into the anathema column. Or as Jonathan said more simply "<span style="font-size:12.8px;font-family:arial,sans-serif">The principle of proportionality doesn't apply to thin data.</span>"</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 31, 2017 at 10:51 AM, jonathan matkowsky <span dir="ltr"><<a href="mailto:jonathan.matkowsky@riskiq.net" target="_blank">jonathan.matkowsky@riskiq.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><div class="h5"><div><br></div><div><br></div><div><br></div><div><div class="gmail_quote"><div>On Wed, 31 May 2017 at 16:50 Dotzero <<a href="mailto:dotzero@gmail.com" target="_blank">dotzero@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Translation (per Google translate) of what Volker posted:<br><br><span id="m_-8160100562555508135m_-377313414510063557gmail-result_box" class="m_-8160100562555508135m_-377313414510063557gmail-" lang="en"><span title=""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">"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 </span><span title="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.">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.<br><br></span><span title="Als personenbezogenes Datum darf die IP-Adresse nur unter den Voraussetzungen des § 15 Abs. 1 TMG gespeichert werden.">The IP address can only be stored as a personal date under the prerequisites of § 15 (1) TMG. </span><span title="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">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 </span><span title="hinaus dann erheben und verwenden darf, soweit ihre Erhebung und ihre Verwendung erforderlich sind, um die generelle Funktionsfähigkeit der Dienste zu gewährleisten.">To the extent that their collection and use is necessary to ensure the general functioning of the services. </span><span title="Dabei bedarf es allerdings einer Abwägung mit dem Interesse und den Grundrechten und -freiheiten der Nutzer."">However, there is a need to balance the interests and the basic rights and freedoms of the users. "</span></span></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 31, 2017 at 9:47 AM, Volker Greimann <span><<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<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):</p>
<p><a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-freetext" 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.<wbr>bundesgerichtshof.de/cgi-bin/<wbr>rechtsprechung/document.py?<wbr>Gericht=bgh&Art=pm&Datum=2017&<wbr>Sort=3&nr=78289&pos=0&anz=74</a><br>
</p>
<p>It followed the decision of the European Court from October last
year:</p>
<p>C-582/14, NJW 2016, 3579</p>
<p>The German explanation:</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><i><br>
</i></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></p>
<p>Hope this helps.<br>
</p><div><div class="m_-8160100562555508135m_-377313414510063557h5">
<br>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-cite-prefix">Am 31.05.2017 um 15:38 schrieb Paul
Keating:<br>
</div>
<blockquote type="cite">
<div>
<blockquote type="cite">
<p><font color="#000000"><span style="background-color:rgba(255,255,255,0)">See: recent Europrean court
decisions on IP addresses as PII.</span></font></p>
</blockquote>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
Can you please provide the citations? I a-m not aware of any
court decision issuingsuch a broad ruling. </div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">Thanks,</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">Paul <br>
<br>
Sent from my iPad</div>
<div><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:<br>
<br>
</div>
<blockquote type="cite">
<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. <br>
</p>
<p>See: recent Europrean court decisions on IP addresses as
PII.</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.</p>
<p>Volker<br>
</p>
<br>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-cite-prefix">Am 30.05.2017 um 23:40 schrieb
Paul Keating:<br>
</div>
<blockquote type="cite">
<div>Im sorry but i don't see the logic here (or the legal
constraint)</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">Privacy laws protect personal
data of INDIVIDUALS. They do t protect non-personal data
or data from non-individuals.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">Nothing on the list below is
personal data. And no e of the principles given by
Natalie apply.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">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.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature"><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151AppleMailSignature">Me thinks you are trying to
create a scarcity for some reason.<br>
<br>
Sent from my iPad</div>
<div><br>
On 30 May 2017, at 23:22, Chris Pelling <<a href="mailto:chris@netearth.net" target="_blank">chris@netearth.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div style="font-family:Arial;font-size:12pt;color:#000000">
<div>ok - a thought :<br>
</div>
<div><br>
</div>
<div>Thin data includes nameservers, being able to <strong><u>mass</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 : <br>
</div>
<div><br>
</div>
<div>Some examples (radomly picked from the list) :<br>
</div>
<div><a href="http://gmail.com" target="_blank">gmail.com</a>
:<br>
</div>
<div>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><br>
</div>
<div>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:(201)%20609-0201" value="+12016090201" target="_blank">2016090201</a> 14400 3600 1209600 86400<br>
</div>
<div><a href="http://law.es" target="_blank">law.es</a><br>
</div>
<div>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:(201)%20606-1402" value="+12016061402" target="_blank">2016061402</a> 43200 7200 1209600 86400<br>
</div>
<div><a href="http://riskiq.net" target="_blank">riskiq.net</a><br>
</div>
<div>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<br>
</div>
<div><br>
</div>
<div>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.<br>
</div>
<div><br>
</div>
<div>Kind regards,<br>
<br>
Chris</div>
<div><br>
</div>
<hr id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151zwchr">
<div><b>From: </b>"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<br>
</div>
<div><br>
</div>
<div>
<div>so can you name one specific example
of how someone could abuse thin data?</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 30, 2017 at
4:50 PM, nathalie coupet via gnso-rds-pdp-wg <span><<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="color:#000;background-color:#fff;font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px">
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><b style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287679">Abuse</b><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287680"> is
the improper usage or treatment of an </span><a href="https://en.wikipedia.org/wiki/Entity" title="Entity" style="text-decoration-line:none;color:rgb(11,0,128);background-image:none;background-color:rgb(255,255,255);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287681" target="_blank">entity</a><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287682">,
often to </span><a href="https://en.wikipedia.org/wiki/Distributive_justice" title="Distributive justice" style="text-decoration-line:none;color:rgb(11,0,128);background-image:none;background-color:rgb(255,255,255);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287683" target="_blank">unfairly</a><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287684"> 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></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px"><br>
</span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px">Here
are some of the overarching principles
which should guide us when building
RDS: </span><br>
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px"><br>
</span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287894"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287895" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287896">DATA
LIFECYCLE
PRIVACY PRINCIPLE
PROTECTION
MEASURE</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287897"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287898" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287899">Collection
Proportionality and purpose
specification
Data minimisation, Data quality</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287900"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287901" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287902">Storage
Accountability,
Security measures, Sensitive data
Confidentiality,
Encryption, Pseudonomisation</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287903"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287904" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287905">Sharing
and processing Lawfulness and
fairness, Consent, Right of access
Data access control, Data leakage
prevention</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287907" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287908">Deletion
Openness, Right to erasure
Retention, Archival, Erasure</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px"><br>
</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px"><br>
</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_291686" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_291685">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></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px"><br>
</span></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287906"><span id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_292975" style="color:#222222;font-family:sans-serif" face="sans-serif" color="#222222"><span style="font-size:14px" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_292974">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></span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><span><br>
</span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287437"><span><br>
</span></div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287435"> </div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687signature" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yui_3_16_0_ym19_1_1496151286812_287433">Nathalie </div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687qtdSeparateBR"><br>
<br>
</div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yahoo_quoted" style="display:block">
<div style="font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px">
<div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><span>
<div><span style="font-family:Arial;font-size:small" size="2" face="Arial"> 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:<br>
</span></div>
<br>
<br>
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687y_msg_container">
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093">
<div><span>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093gmail_default" style="font-family:arial,helvetica,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></div>
</div>
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093gmail_extra"><span><br clear="all">
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093gmail_signature">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><span style="color:#073763;font-family:arial,helvetica,sans-serif" face="arial,
helvetica,
sans-serif" color="#073763">John
Horton<br clear="none">
President and
CEO,
LegitScript</span>
<div><img height="36" width="96"><br clear="none">
<div>
<div>
<div style="margin:0.0px 0.0px 0.0px 0.0px;font:12.0px Helvetica"><br clear="none">
</div>
<div style="margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><b><span style="color:#444444" color="#444444">Follow</span><span style="color:#0b5394" color="#0b5394">
</span><span style="color:#000000" color="#000000">Legit</span><span style="color:#0b5394" color="#0b5394">Script</span></b>:
<a rel="nofollow" shape="rect" href="http://www.linkedin.com/company/legitscript-com" style="font-weight:normal" target="_blank"><span style="color:#cc0000" color="#cc0000">LinkedIn</span></a>
| <a rel="nofollow" shape="rect" href="https://www.facebook.com/LegitScript" style="font-weight:normal" target="_blank"><span style="color:#6aa84f" color="#6aa84f">Facebook</span></a>
| <a rel="nofollow" shape="rect" href="https://twitter.com/legitscript" style="font-weight:normal" target="_blank"><span style="color:#674ea7" color="#674ea7">Twitter</span></a>
| <span style="color:#ff9900" color="#ff9900"><span style="text-decoration:underline"><a rel="nofollow" shape="rect" href="http://blog.legitscript.com/" target="_blank">Blog</a></span></span> |<span style="color:#ff9900" color="#ff9900">
<span style="font-weight:normal"><a rel="nofollow" shape="rect" href="https://plus.google.com/112436813474708014933/posts" target="_blank">Google+</a></span></span><br>
</div>
<div style="margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span style="color:#ff9900" color="#ff9900"><br clear="none">
</span></div>
<div style="text-align:left;margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><span style="color:#ff9900" color="#ff9900"><img height="96" width="46"><img height="96" width="47"><br clear="none">
</span></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>
<br clear="none">
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093gmail_quote"><span>On Tue, May 30,
2017 at 12:57 PM, Paul
Keating <span><<a rel="nofollow" shape="rect" href="mailto:paul@law.es" target="_blank">paul@law.es</a>></span>
wrote:<br clear="none">
</span>
<blockquote class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093yqt3775885078" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093yqt77589">
<div><span>
<div>Natalie,</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">Thank
you for the
email. Im
copying the list
because i see
others have
replied to your
comment.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">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.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">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.</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature">If
i am missing
something please
let me know. </div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
Paul</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945AppleMailSignature"><br clear="none">
Sent from my
iPad</div>
</span>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093h5"><span>
<div><br clear="none">
On 30 May
2017, at
21:08,
nathalie
coupet via
gnso-rds-pdp-wg
<<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>>
wrote:<br clear="none">
<br clear="none">
</div>
</span>
<blockquote>
<div>
<div style="color:#000;background-color:#fff;font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px"><span>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">Hi
Paul,</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556"><br clear="none">
</div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">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. </div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556">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. </div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239556"> </div>
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239558"> </div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945signature" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yui_3_16_0_ym19_1_1496151286812_239560">Nathalie </div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945qtdSeparateBR"><br clear="none">
<br clear="none">
</div>
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yahoo_quoted" style="display:block">
<div style="font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px">
<div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><span>
<div><span style="font-family:Arial;font-size:small" size="2" face="Arial">
On Tuesday,
May 30, 2017
2:44 PM,
"Gomes, Chuck
via
gnso-rds-pdp-wg"
<<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>>
wrote:<br clear="none">
</span></div>
<br clear="none">
<br clear="none">
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945y_msg_container">
<div id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320">
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320WordSection1"><span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:11.0pt">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></div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:11.0pt"> </span></div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:11.0pt">Chuck</span></div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><a rel="nofollow" shape="rect" name="m_-8160100562555508135_m_-377313414510063557_m_-7982672186852212151_m_-1108286820301507687_m_-2551964071040587945__MailEndCompose"><span style="font-size:11.0pt"> </span></a><br>
</div>
<span></span>
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320yqt1472831610" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320yqt95202">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt">
<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.
org</a> [<a rel="nofollow" shape="rect" 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<span><br clear="none">
<b>Sent:</b>
Tuesday, May
30, 2017 2:17
PM<br clear="none">
<b>To:</b>
Lisa Phifer
<<a rel="nofollow" shape="rect" href="mailto:lisa@corecom.com" target="_blank">lisa@corecom.com</a>>; RDS PDP
WG <<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br clear="none">
<b>Subject:</b>
[EXTERNAL] Re:
[gnso-rds-pdp-wg] Principle on Proportionality for "Thin Data"access</span></span></div>
</div>
</div>
<span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal">
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">Im sorry to have missed the call but had a
client
engagement.</span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt"> </span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">Can someone briefly describe the nature of the
issue?</span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt"> </span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">Thanks</span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">Paul</span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt"> </span></div>
</div>
</span>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><b><span style="font-size:11.0pt">From: </span></b><span style="font-size:11.0pt"><<a rel="nofollow" shape="rect" 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 rel="nofollow" shape="rect" href="mailto:lisa@corecom.com" target="_blank">lisa@corecom.com</a>><span><br clear="none">
<b>Date: </b>Tuesday,
May 30, 2017
at 7:52 PM<br clear="none">
<b>To: </b>RDS
PDP WG <<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br clear="none">
<b>Subject: </b>[gnso-rds-pdp-wg]
Principle on
Proportionality
for "Thin
Data"access</span></span></div>
</div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt"> </span></div>
</div>
<blockquote id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border:none;border-left:solid #b5c4df 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in"><span>
<div>
<div>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">All, per today's call action item:<br clear="none">
<br clear="none">
<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 clear="none">
<br clear="none">
</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 clear="none">
<br clear="none">
Best, Lisa</span></div>
</div>
</div>
</span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yiv0605036320MsoNormal"><span style="font-size:10.5pt">______________________________
_________________
gnso-rds-pdp-wg mailing list <a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a> <a rel="nofollow" shape="rect" 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><br>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<span>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yqt1472831610" id="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151m_-1108286820301507687yiv8771876093m_-2551964071040587945yqt24053">______________________________
_________________<br clear="none">
gnso-rds-pdp-wg mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/
listinfo/gnso-rds-pdp-wg</a><br>
</div>
<br clear="none">
<br clear="none">
</span></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<span>
<blockquote>
<div><span>______________________________
_________________</span><br clear="none">
<span>gnso-rds-pdp-wg
mailing list</span><br clear="none">
<span><a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br clear="none">
<span><a rel="nofollow" shape="rect" 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><br>
</div>
</blockquote>
</span></div>
</div>
</div>
</div>
<span><br clear="none">
______________________________ _________________<br clear="none">
gnso-rds-pdp-wg
mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/
listinfo/gnso-rds-pdp-wg</a><br clear="none">
</span></blockquote>
</div>
<br clear="none">
</div>
</div>
</div>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151gmail_signature">______________________________<wbr>___<br>
Note to self: Pillage BEFORE burning.</div>
</div>
<br>
______________________________<wbr>_________________<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/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>______________________________<wbr>_________________</span><br>
<span>gnso-rds-pdp-wg mailing list</span><br>
<span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
<br>
<fieldset class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.
------------------------------<wbr>--------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.
</pre>
</div>
</blockquote>
<blockquote type="cite">
<div><span>______________________________<wbr>_________________</span><br>
<span>gnso-rds-pdp-wg mailing list</span><br>
<span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</blockquote>
<br>
<pre class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.
------------------------------<wbr>--------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="m_-8160100562555508135m_-377313414510063557m_-7982672186852212151moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.
</pre>
</div></div></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br></div>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></blockquote></div></div><div dir="ltr">-- <br></div></div></div><div data-smartmail="gmail_signature">jonathan matkowsky, vp - ip & head of global brand threat mitigation</div>
<br>______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br></div>