<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Optima;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks Steve. I have no objections with the paragraph below. I would suggest that on page 6, if we accept that users should pay a fee for gated access that
we should qualify that by saying the fee should be limited to cost recovery. In fact, I question whether gated access shouldn’t be part of the cost of doing business for registrars. I would welcome thoughts from others. Thanks for all of your efforts in
coordinating these comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org]
<b>On Behalf Of </b>Steve DelBianco<br>
<b>Sent:</b> Friday, September 06, 2013 1:04 AM<br>
<b>To:</b> bc-gnso@icann.org list<br>
<b>Subject:</b> [bc-gnso] LAST CALL: BC comments on Expert Working Group (EWG) for directory services (Whois)<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">This is "Last Call" for members who would object to filing the attached comments by tomorrow's deadline.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Since I circulated a draft on Monday, we have seen no objections. But we did see some excellent debate about this paragraph:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in;border-width:initial;border-color:initial">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Eligibility for privacy/proxy protection should only be extended to registrants who promise not to solicit sales, payments, or donations, and promise not to facilitate infringement
of intellectual property rights. And the EWG’s “Maximum Protected Registration” should only be available to registrants who demonstrate a need for privacy to protect at-risk free-speech uses. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Google questioned the idea of
<i>per-se</i> restricting donation-seeking domains from using privacy/proxy services. Looks to me like the majority of subsequent comments were in favor of retaining the per-se restriction above. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">But as a by-product of that discussion, several of you wanted to add a few more offenses to the list of things that privacy/proxy eligible domains would promise
<u>not</u> to do. So I've revised that first sentence to read:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Eligibility for privacy/proxy protection should only be extended to registrants who promise not to solicit sales, payments, or donations, and promise not to facilitate infringement of intellectual
property rights, distribution of malware, phishing, or other fraud. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Unless more than 5 members object, I will file these comments by 3pm EST on Friday 6-Sep.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Optima","serif";color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Optima","serif";color:black">Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<b>Date: </b>Monday, September 2, 2013 11:45 AM<br>
<b>To: </b>"<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a> list" <<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a>><br>
<b>Subject: </b>FOR REVIEW: Latest draft of BC comments on Expert Working Group (EWG) for directory services (Whois)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">As a follow-up to Thursday's BC call, here's a new draft for member review. <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">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%20">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%20">link</a>)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">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%20">link</a>) where the BC said: "ICANN should also
consider mechanisms to create and maintain a </span><span style="font-family:"Calibri","sans-serif";color:red">centralized WHOIS database</span><span style="font-family:"Calibri","sans-serif";color:black">."<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">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%20">link</a>), where
we endorsed privacy/proxy obligations:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">• Adopting agreed standardized relay and reveal processes and timeframes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">• Conducting periodic due diligence checks on customer contact information;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">• Providing clear and unambiguous guidance on the rights and responsibilities of registered name holders, and how those should be managed in the Privacy / Proxy environment.<o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">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%20">link</a>), where
we proposed Relay and Reveal obligations and timelines for privacy/proxy services.<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Then I started with our 9-Aug draft comments and added discussion from 29-Aug BC member call. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Attached is my 2-Sep draft, plus a redline comparing with the previous draft distributed (9-Aug).<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Please REPLY ALL with objections or comments before Thursday 5-Sep so we can meet the EWG deadline of 6-Sep.<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">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.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">--
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Steve DelBianco<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Executive Director<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">NetChoice<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><a href="http://www.NetChoice.org">http://www.NetChoice.org</a> and
<a href="http://blog.netchoice.org">http://blog.netchoice.org</a> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">+1.202.420.7482
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br clear=all> This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee. If you are not the addressee indicated in this message (or responsible for delivery of the message to the addressee), you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments that does not relate to the official business of Twenty-First Century Fox, Inc. or its subsidiaries must be taken not to have been sent or endorsed by any of them. No representation is made that this email or its attachments are without defect.
</body>
</html>