<div dir="ltr">Thanks Laura, Marilyn, Steve and Bill for the further comments. I don't think we disagree in principle, just in which term should be used (donations v. financial scams). To clarify, I'm certainly not advocating that we recommend privacy protections for every site that solicits donations - rather, I'm simply proposing that we refrain from referencing it as one of the automatically prohibited category of sites, which would then just comprise of (1) sales and (2) payments. This would have the effect of ensuring that we are not preventing <u>all</u> sites that receive donations from having a privacy/proxy service, because I think some legitimately merit such services (e.g., political blogs that require donations to stay afloat) while others obviously don't (e.g., charity scams). In order to catch the latter sites, I'm proposing we expand the prohibited actions to include (1) IP infringement, (2) <span style="font-family:arial,sans-serif;font-size:13px">phishing, (3) malware, and (4) financial scams.</span><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">Best,</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Andy</font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 3, 2013 at 3:37 PM, Laura Covington <span dir="ltr"><<a href="mailto:lhc@yahoo-inc.com" target="_blank">lhc@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Arial,sans-serif;word-wrap:break-word">
<div>
<div>
<div>Certainly willing to hear more from others who may disagree but I think text is appropriate as is (sites seeking donations do not get privacy/proxy services); I have work experience relating to trying to deal with potentially scam fund raisers after 9/11.
</div>
<div><br>
</div>
<div> </div>
<div>
<div>
<div>Laura Covington</div>
<div>VP, Intellectual Property Policy</div>
<div>Yahoo! Inc.</div>
<div><a href="mailto:lhc@yahoo-inc.com" target="_blank">lhc@yahoo-inc.com</a></div>
<div><a href="tel:408.349.5187" value="+14083495187" target="_blank">408.349.5187</a></div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span>
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org" target="_blank">sdelbianco@netchoice.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, September 3, 2013 3:02 PM<br>
<span style="font-weight:bold">To: </span>"Smith, Bill" <<a href="mailto:bill.smith@paypal-inc.com" target="_blank">bill.smith@paypal-inc.com</a>>, Andy Abrams <<a href="mailto:abrams@google.com" target="_blank">abrams@google.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:bc-gnso@icann.org" target="_blank">bc-gnso@icann.org</a> list" <<a href="mailto:bc-gnso@icann.org" target="_blank">bc-gnso@icann.org</a>><div><div class="h5">
<br>
<span style="font-weight:bold">Subject: </span>Re: [bc-gnso] FOR REVIEW: Latest draft of BC comments on Expert Working Group (EWG) for directory services (Whois)<br>
</div></div></div><div><div class="h5">
<div><br>
</div>
<div>
<div style="font-size:16px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>
<div>
<div>Yes, but that's not entirely Andy's point, Bill. Andy first suggested we allow privacy protections for a website that solicited donations. </div>
<div><br>
</div>
<div>Do BC members believe that donation-soliciting sites should be eligible for privacy/proxy services? </div>
<div><br>
</div>
<div>As Andy notes, donors are often fooled by sites that pretend to be a reputable group helping with an emergency. The Red Cross/Red Crescent has talked about this at ICANN before. Should we really be recommending that ICANN allow privacy/proxy services
for any site that solicits donations, as opposed to payments for services/goods/ads?</div>
</div>
</div>
<div><br>
</div>
<div>Please read (and react) to the text proposed for this section (page 2, re-attached for your convenience), because the discussion thread sometimes tells only half the story…</div>
<div><br>
</div>
<span>
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:10pt;border-bottom:medium none;font-family:Optima;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span><Smith>, Bill <<a href="mailto:bill.smith@paypal-inc.com" target="_blank">bill.smith@paypal-inc.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, September 3, 2013 5:19 PM<br>
<span style="font-weight:bold">To: </span>Andy Abrams <<a href="mailto:abrams@google.com" target="_blank">abrams@google.com</a>><br>
<span style="font-weight:bold">Cc: </span>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org" target="_blank">sdelbianco@netchoice.org</a>>, "<a href="mailto:bc-gnso@icann.org" target="_blank">bc-gnso@icann.org</a> list" <<a href="mailto:bc-gnso@icann.org" target="_blank">bc-gnso@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [bc-gnso] FOR REVIEW: Latest draft of BC comments on Expert Working Group (EWG) for directory services (Whois)<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<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" target="_blank">abrams@google.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<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-size:13px;font-family:arial,sans-serif">"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-size:13px;font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif">We'd love to hear others' views on this point. </span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif">Best,</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif">Andy and Aparna</span></div>
<div><br>
</div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_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="gmail_quote" style="margin:0px 0px 0px 0.8ex;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="margin:0px 0px 0px 40px;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 href="tel:%2B1.202.420.7482" value="+12024207482" 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-size:13px;border-collapse:collapse;font-family:arial,sans-serif">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="border-collapse:separate;color:rgb(0,0,0);font-family:Arial,sans-serif"><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>
</span></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>