<html><body><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>Got to agree with Andrew on this - my thoughts on thin is exactly what Verisign shows now which is basically domain name, dates, registrar, nameservers and status << That is the common term of "THIN DATA".</div><div><br></div><div>As I said, thin data I have no issues with, even data harvesting companies having it lawfully. </div><div><br data-mce-bogus="1"></div><div data-marker="__SIG_PRE__">Kind regards,<br><br>Chris</div><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Andrew Sullivan" <ajs@anvilwalrusden.com><br><b>To: </b>"Paul Keating" <paul@law.es><br><b>Cc: </b>"gnso-rds-pdp-wg" <gnso-rds-pdp-wg@icann.org><br><b>Sent: </b>Thursday, 18 May, 2017 00:52:33<br><b>Subject: </b>Re: [gnso-rds-pdp-wg] IMPROTANT - Action Items and Notes from Next-Generation RDS PDP Working Group Call - 17 May 2017<br></div><br><div data-marker="__QUOTED_TEXT__"><div>No, the data we are currently discussing is thin data. Among it, I believe only the domain name and maybe the name servers are entered by the registrant, and both of those are required if there is to be a domain name that works on the Internet. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I find it quite frustrating that we do not seem to be able, as a group, to keep these elementary distinctions before us during discussion. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">A<br><br>-- <div>Andrew Sullivan </div><div>Please excuse my clumbsy thums. </div></div><div><br>On May 17, 2017, at 18:06, Paul Keating <<a href="mailto:paul@law.es" target="_blank">paul@law.es</a>> wrote:<br><br></div><blockquote><div><div>Licensing what and from whom?</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">This is data entered by the registrant. Privacy issues apply only to the subset of individuals.<br><br>Sent from my iPad</div><div><br>On 17 May 2017, at 23:38, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>> wrote:<br><br></div><blockquote><div><div dir="ltr"><div class="gmail_default" style="font-family: verdana,sans-serif;" data-mce-style="font-family: verdana,sans-serif;">One way to deal with harvesters is through a licensing set-up. There are legitimate reasons to have the full dataset, and these should be accommodated in a controlled environment. Preventing bad harvesters is worthwhile, prevent all harvesting is another issue entirely....</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;" data-mce-style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"></p><div><p style="text-indent: 0in;" data-mce-style="text-indent: 0in;"><span style="font-size: 12.8px;" data-mce-style="font-size: 12.8px;"><a name="UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter__GoBack"></a></span><b style="font-size: 12.8px;" data-mce-style="font-size: 12.8px;"><span style="font-size: 10.0pt; font-family: 'Arial','sans-serif'; color: #002e62;" data-mce-style="font-size: 10.0pt; font-family: 'Arial','sans-serif'; color: #002e62;">Greg
Shatan<br>
</span></b><span style="font-size: 10pt; font-family: Arial,sans-serif; color: black;" data-mce-style="font-size: 10pt; font-family: Arial,sans-serif; color: black;">C: 917-816-6428<br>
S: gsshatan</span><span color="#000000" face="Arial, sans-serif" data-mce-style="color: #000000; font-family: Arial, sans-serif;" style="color: #000000; font-family: Arial, sans-serif;"><span style="font-size: 13.3333px;" data-mce-style="font-size: 13.3333px;"><br></span></span><a href="mailto:gregshatanipc@gmail.com" style="font-family: Arial,sans-serif; font-size: 10pt; text-indent: 0in;" target="_blank" data-mce-style="font-family: Arial,sans-serif; font-size: 10pt; text-indent: 0in;"><span style="color: #1155cc;" data-mce-style="color: #1155cc;">gregshatanipc@gmail.com</span></a></p><p style="font-size: 12.8px; text-indent: 0in;" data-mce-style="font-size: 12.8px; text-indent: 0in;"><span style="font-size: 10.0pt; font-family: 'Arial','sans-serif';" data-mce-style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"></span></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, May 17, 2017 at 3:00 PM, Michael Peddemors <span dir="ltr"><<a href="mailto:michael@linuxmagic.com" target="_blank">michael@linuxmagic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><span class="">On 17-05-17 10:46 AM, Jeremy Malcolm wrote:<br>
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
On 17/5/17 9:40 am, Michael Peddemors wrote:<br>
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
Yes, this is the common argument, however IMHO this is a red herring..<br>
There are more efficient ways for 'harvesters' to gain data, and<br>
others way to prevent such abuse..<br>
<br>
Again, IMHO this argument is another case of impacting the many<br>
legitimate users, for the sake of a few bad apples..<br>
<br>
And I havent' seen any arguments yet, of a case scenario which can't<br>
be addressed by other means..<br>
</blockquote>
<br>
So to reverse this, what are the *legitimate* purposes of harvesting?<br>
</blockquote>
<br></span>
Who said anything about arguing for 'harvesting' as a legitimate purpose? I didn't, and even pointed out that there are way(s) to target harvesters..<br>
<br>
I was pointing out the legitimate purposes of accessing the data..<br>
<br>
And many of those cases have already been stated, I could re-iterate those arguments, and give examples of why 'we' need to access the data, but again, 'harvesting' is different than access.<br>
<br>
Arguing that we 'have to stop harvesters' by denying access to the data for legitimate purposes was the original point. There are other means to target those perpetrators.. But it shouldn't be used as a 'scary boogeyman' exists, so everyone lock your doors.<br>
<br>
To paraphrase.. "Just because criminals exist, doesn't mean that civilians can't walk the street". That is a 'gut reaction' of fear, and not a solution. Better policing, targeting criminals, or carry a big stick solves that :)<br>
<br>
Nuff said.. as I said, lets' place case scenario's and argument each on their merits.. and not react to a 'undefinable' threat..<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
"Catch the Magic of Linux..."<br>
------------------------------------------------------------------------<br>
Michael Peddemors, President/CEO LinuxMagic Inc.<br>
Visit us at <a href="http://www.linuxmagic.com" rel="noreferrer" target="_blank">http://www.linuxmagic.com</a> @linuxmagic<br>
------------------------------------------------------------------------<br>
A Wizard IT Company - For More Info <a href="http://www.wizard.ca" rel="noreferrer" target="_blank">http://www.wizard.ca</a><br>
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.<br>
------------------------------------------------------------------------<br>
<a href="tel:604-682-0300" target="_blank">604-682-0300</a> Beautiful British Columbia, Canada<br>
<br>
This email and any electronic data contained are confidential and intended<br>
solely for the use of the individual or entity to which they are addressed.<br>
Please note that any views or opinions presented in this email are solely<br>
those of the author and are not intended to represent those of the company.<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote><div><span>_______________________________________________</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/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></div></blockquote><blockquote><div><span>_______________________________________________</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/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote><br>_______________________________________________<br>gnso-rds-pdp-wg mailing list<br>gnso-rds-pdp-wg@icann.org<br>https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg<br></div></div></body></html>