<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I support expanding the clause as well to include malware, phishing, etc. <br><br><div><hr id="stopSpelling">From: bill.smith@paypal-inc.com<br>To: abrams@google.com<br>CC: sdelbianco@netchoice.org; bc-gnso@icann.org<br>Subject: Re: [bc-gnso] FOR REVIEW: Latest draft of BC comments on Expert Working Group (EWG) for directory services (Whois)<br>Date: Tue, 3 Sep 2013 21:19:36 +0000<br><br>
<div>I'm all for expanding the clause to include non-IP abuse.</div>
<div><br>
On Sep 3, 2013, at 1:08 PM, "Andy Abrams" <<a href="mailto:abrams@google.com">abrams@google.com</a>> wrote:<br>
<br>
</div>
<blockquote>
<div>
<div dir="ltr">Hi Steve,
<div><br>
</div>
<div>We really appreciate your work on this document and your efforts to capture the discussions from last week. Our only minor follow-up comment relates to the use of the term <span style="font-family:arial,sans-serif;font-size:13px;">"donations" in the first
sentence of "Eligibility for Protected Registration." Per our previous comment, I think there are some issues with including "donations" as a
<i>per se</i> reason to disqualify one from taking advantage of privacy/proxy services, given the frequent connection between donations and political or other free speech. With that said, I recognize that there is value in preventing a specific abuse relating
to donations, namely, charity scams that solicit money. Perhaps we can reach a compromise by removing the term from the sentence, but by broadening the second clause in the sentence to include other abuses beyond IP infringement, including phishing, malware,
financial scams, etc. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;">We'd love to hear others' views on this point. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;">Best,</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;">Andy and Aparna</span></div>
<div><br>
</div>
<div>
<div class="ecxgmail_extra"><br>
<div class="ecxgmail_quote">On Mon, Sep 2, 2013 at 8:49 AM, Steve DelBianco <span dir="ltr">
<<a href="mailto:sdelbianco@netchoice.org" target="_blank">sdelbianco@netchoice.org</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div>As a follow-up to Thursday's BC call, here's a new draft for member review. </div>
</div>
</div>
<span>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;"><br>
</div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">First thing I did was re-read the EWG report on which we are commenting. (<a href="http://www.icann.org/en/groups/other/gtld-directory-services/initial-report-24jun13-en.pdf" target="_blank">link</a>)
It's also helpful to review FAQs published by the EWG (<a href="http://www.icann.org/en/groups/other/gtld-directory-services/faqs" target="_blank">link</a>)</div>
<div style="font-size:16px;font-family:Calibri,sans-serif;"><br>
</div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">Second thing I did was review
<u>prior</u> BC positions on this, starting with our Jul-2011 "Response to WHOIS Policy Review Team Discussion Paper" (<a href="http://www.bizconst.org/Positions-Statements/BC_on_WHOIS_Review_Questions.pdf" target="_blank">link</a>) where the BC said: "ICANN
should also consider mechanisms to create and maintain a <font color="#ff0000">centralized WHOIS database</font>."</div>
<div><br>
</div>
<div>Also see Jun-2012 BC comment on WHOIS Affirmation Review (<a href="http://www.bizconst.org/Positions-Statements/BC%20on%20WHOIS%20RT%20Final%20Report.pdf" target="_blank">link</a>), where we endorsed privacy/proxy obligations:</div>
<blockquote style="border:none;padding:0px;">
<div>
<div><font face="Calibri,sans-serif">• Adopting agreed standardized relay and reveal processes and timeframes</font></div>
<div>• Conducting periodic due diligence checks on customer contact <span style="font-family:Calibri,sans-serif;">information;</span></div>
<div><span style="font-family:Calibri,sans-serif;">• Providing clear and unambiguous guidance on the rights and </span><span style="font-family:Calibri,sans-serif;">responsibilities of registered name holders, and how those should be managed in the Privacy /
Proxy environment.</span></div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>And see our May-2013 comments on the new RAA (<a href="http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20final%202013%20RAA%20%5bFINAL%5d.pdf" target="_blank">link</a>), where we proposed Relay and Reveal obligations and timelines for privacy/proxy
services.</div>
<span>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;"><br>
</div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">Then I started with our 9-Aug draft comments and added discussion from 29-Aug BC member call. </div>
<div style="font-size:16px;font-family:Calibri,sans-serif;"><br>
</div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">Attached is my 2-Sep draft, plus a redline comparing with the previous draft distributed (9-Aug).</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">
<div>Please REPLY ALL with objections or comments before Thursday 5-Sep so we can meet the EWG deadline of 6-Sep.</div>
<span>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;"><br>
</div>
</div>
</div>
</div>
</div>
</span></div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">Looking forward to an informed and respectful discussions, so we can get our thoughts to the EWG while they are working on their final report for October publication.</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word;">
<div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;">
<div>-- </div>
<div>Steve DelBianco</div>
<div>Executive Director</div>
<div>NetChoice</div>
<div><a href="http://www.NetChoice.org" target="_blank">http://www.NetChoice.org</a> and
<a href="http://blog.netchoice.org" target="_blank">http://blog.netchoice.org</a>
</div>
<div><a target="_blank">+1.202.420.7482</a>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<span style="color:rgb(51,51,51);font-family:arial,sans-serif;font-size:13px;"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;">Andy Abrams | Trademark Counsel<br>
<span style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,0);"><b><span style="color:rgb(51,51,255);">G</span><span style="color:rgb(255,0,0);">o</span><span style="color:rgb(255,204,0);">o</span><span style="color:rgb(51,51,255);">g</span><span style="color:rgb(51,204,0);">l</span><span style="color:rgb(255,0,0);">e</span></b></span> |
1600 Amphitheatre Parkway, Mountain View, CA 94043</span>
<div><span style="font-family:Arial,sans-serif;border-collapse:separate;color:rgb(0,0,0);"><a title="Go to phones" href="https://www.google.com/voice#phones" style="color:rgb(0,0,0);text-decoration:none;" target="_blank">(650) 669-8752</a></span></div>
</span></div>
</div>
</div>
</div>
</blockquote></div> </div></body>
</html>