<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#444444">+1 (Tim)</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font color="#073763" face="arial, helvetica, sans-serif">John Horton<br>President and CEO, LegitScript</font><div><img src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJRXE5UTAtclVxdTg&revid=0B13GfLt8zwZJSG9zOUVwN1lFKzFrRVlnaWU0NGZ4RmdkUjg4PQ" width="96" height="36"><br><div><div><p style="margin:0.0px 0.0px 0.0px 0.0px;font:12.0px Helvetica"><br></p><p style="margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><b><font color="#444444">Follow</font><font color="#0b5394"> </font><font color="#000000">Legit</font><font color="#0b5394">Script</font></b>: <a href="http://www.linkedin.com/company/legitscript-com" style="font-weight:normal" target="_blank"><font color="#cc0000">LinkedIn</font></a> | <a href="https://www.facebook.com/LegitScript" style="font-weight:normal" target="_blank"><font color="#6aa84f">Facebook</font></a> | <a href="https://twitter.com/legitscript" style="font-weight:normal" target="_blank"><font color="#674ea7">Twitter</font></a> | <font color="#ff9900"><u><a href="http://blog.legitscript.com" target="_blank">Blog</a></u></font> |<font color="#ff9900"> <font style="font-weight:normal"><a href="https://plus.google.com/112436813474708014933/posts" target="_blank">Google+</a></font></font></p><p style="margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><font color="#ff9900"><br></font></p><p style="text-align:left;margin:0px;font-style:normal;font-variant:normal;font-size:12px;line-height:normal;font-family:Helvetica"><font color="#ff9900"><img src="https://www.legitscript.com/wp-content/uploads/2015/09/LegitScript-Workplace.png" width="46" height="96"><img src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJTmNWbmcwOTVJMXc&revid=0B13GfLt8zwZJQlZWOXVGbG9acC9nRGhzdEkxclFJVytCWVNjPQ" width="47" height="96"><br></font></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>
<br><div class="gmail_quote">On Wed, May 17, 2017 at 1:41 PM, Chen, Tim <span dir="ltr"><<a href="mailto:tim@domaintools.com" target="_blank">tim@domaintools.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">since this is the ICANN RDS PDP we will obviously have to spend a few weeks defining "legitimate" before I can respond to your question :)<div><br></div><div>I'm going to agree to disagree with Chris and Volker on this.</div><div><br></div><div>Having the whois data sets together can specifically be used to help combat spam, phishing, malware and other forms of abuse. Many people in this forum have pointed out real-life examples of how they do that so I won't repeat those here.</div><div><br></div><div>These are the same benefits to having a "parallel database" where in fact no such database actually exists today bc each individual registrar and registry is in possession of only a small fraction of the data (Verisign and GoDaddy possibly excepted here). DomainTools makes no claim to 'be right', that is what your customer said. Our data is accurate to the data that was at the registry or registrar at the time the record was seen. Basically the same language here that we all agreed on for 'authoritative' last night. RDS is going to have the exact same issue. Right? Right.</div><div><br></div><div>Which leaves the resale argument among the four that Volker stated. I doubt this is the venue to debate the merits of business models based on DNS data (of which there are more than I can count), but I am not opposed to having that discussion in the right forum. </div><div><br></div><div>Another +1 to Michael P's statement.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Wed, May 17, 2017 at 10:46 AM, Jeremy Malcolm <span dir="ltr"><<a href="mailto:jmalcolm@eff.org" target="_blank">jmalcolm@eff.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">On 17/5/17 9:40 am, Michael Peddemors wrote:<br>
> 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>
<br>
So to reverse this, what are the *legitimate* purposes of harvesting?<br>
<br>
--<br>
Jeremy Malcolm<br>
Senior Global Policy Analyst<br>
Electronic Frontier Foundation<br>
<a href="https://eff.org" rel="noreferrer" target="_blank">https://eff.org</a><br>
<a href="mailto:jmalcolm@eff.org" target="_blank">jmalcolm@eff.org</a><br>
<br>
Tel: <a href="tel:415.436.9333%20ext%20161" value="+14154369333" target="_blank">415.436.9333 ext 161</a><br>
<br>
:: Defending Your Rights in the Digital World ::<br>
<br>
Public key: <a href="https://www.eff.org/files/2016/11/27/key_jmalcolm.txt" rel="noreferrer" target="_blank">https://www.eff.org/files/2016<wbr>/11/27/key_jmalcolm.txt</a><br>
PGP fingerprint: 75D2 4C0D 35EA EA2F 8CA8 8F79 4911 EC4A EDDF 1122<br>
<br>
<br>
<br></div></div><span class="">______________________________<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/l<wbr>istinfo/gnso-rds-pdp-wg</a><br></span></blockquote></div><br></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>