<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>On our last two BC calls, we asked for volunteers to respond to questions from a PDP working group on issues for the Accreditation of Privacy & Proxy services under the new RAA. (<a href="https://community.icann.org/pages/viewpage.action?pageId=43983094">wiki</a>) </div>
<div><br>
</div>
<div>No volunteers came forward, and the deadline was today. So I responded for the BC, using previously approved BC statements and several questions (not positions) for consideration. </div>
<div><br>
</div>
<div>See my response below, and please think about volunteering for this working group. If nothing else, please attend their session in Singapore on this issue that’s always been vital to BC member interests.</div>
<div><br>
</div>
<div>—Steve</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<span style="font-weight:bold">Date: </span>Friday, February 28, 2014 at 7:01 PM<br>
<span style="font-weight:bold">To: </span>Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>><br>
<span style="font-weight:bold">Cc: </span>Glen de Saint Géry <<a href="mailto:Glen@icann.org">Glen@icann.org</a>>, BC Executive Committee <<a href="mailto:bc-excomm@icann.org">bc-excomm@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Request for input: GNSO's Working Group on Privacy & Proxy Services Accreditation<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Mary,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Thanks for talking today about BC input on privacy/proxy accreditation. Here’s a follow-up for your notes:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">First, we hope you can find a place for these 4 points the BC adopted regarding the 2013 RAA last May (<a href="http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20final%202013%20RAA%20[FINAL].pdf">link</a>):</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<blockquote style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><span style="font-family: Calibri;">The BC notes that the specification only requires that registrars require P/P Providers to post their privacy-proxy terms and conditions on their websites and does not require specific content of what those terms and
conditions must entail. The BC would like to see specific content requirements of the terms and conditions as to the following issues:</span></div>
</blockquote>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>
<div class="page" title="Page 4">
<div class="layoutArea">
<div class="column">
<div>
<ul>
<li><span style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-style: normal; font-weight: normal; text-decoration: none;"><span style="font-family: Calibri;">Specify under what circumstances, pursuant to section 2.4.3, the P/P Provider will relay
communications from third parties to the P/P Customer. The BC recommends that the P/P Provider be required at a minimum to relay any communications alleging illegal conduct or consumer fraud (e.g., infringement of intellectual property rights).
</span></span></li></ul>
</div>
<ul>
<li>
<p><span style="font-family: Calibri;">Specify under what circumstances and which time frame, pursuant to section 2.4.5, the P/P Provider will be required to reveal the Whois information of the P/P Customer. The BC recommends that if illegal activity is alleged,
that the P/P Provider be required to reveal the Whois information and that this revelation occurs within seven (7) business days to conform to section.
</span></p>
</li><li>
<div><span style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-style: normal; font-weight: normal; text-decoration: none;"><span style="font-family: Calibri;">The BC recommends that the P/P Provider be required to relay any covered communication
within three (3) business days to the P/P Customer. In addition, the BC requests that the specification require that the P/P Provider confirm such relay within 24 hours to the person submitting the report of abuse.</span></span></div>
</li></ul>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</span><span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>
<div class="page" title="Page 4">
<div class="layoutArea">
<div class="column">
<ul>
<li>
<div><span style="font-family: Calibri;">The BC is concerned that there is no means by which to amend the P/P specification. It could be several years before this specification is replaced by a Privacy and Proxy Accreditation Program. Therefore, the BC recommends
there be a mechanism to amend the P/P specification as may be considered necessary by the parties and stakeholders. </span></div>
</li></ul>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</span><span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div>Second, here are some high-level questions (not official positions) the BC offers the WG:</div>
</div>
</span>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><b>ICANN enforcement: </b>Can we create an Accreditation system where ICANN compliance has legal power and leverage to enforce against accredited P/P providers who don’t follow the required
RELAY and REVEAL procedures? It’s far better for ICANN Compliance to have direct relationship with P/P Providers, than to rely only upon implied liability for failures to RELAY/REVEAL.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div><font face="Calibri,sans-serif" style="font-weight: bold;">Must both Resellers
</font><u style="font-weight: bold; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">and Registrars</u><font face="Calibri,sans-serif"><b> use accredited P/P providers?
</b>As we discussed tonight, the 2013 RAA (l<a href="https://community.icann.org/download/attachments/43984221/2013%20RAA.pdf?version=1&modificationDate=1384877800000&api=v2">ink</a>) has strong requirements for Resellers to use Accredited P/P providers, but
where’s the requirement for Registrars? (see comparison below)</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><font face="Calibri,sans-serif">3.12.4 … the Proxy Accreditation Program may require that: (i) proxy and privacy registration services may only be provided in respect of domain name registrations by individuals or entities Accredited by ICANN pursuant
to such Proxy Accreditation Program; and (ii) <font color="#ff0000">Registrar shall prohibit Resellers from knowingly accepting registrations from any provider of proxy and privacy registration services that is not Accredited by ICANN</font> pursuant the Proxy
Accreditation Program. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">3.14 Obligations Related to Proxy and Privacy Services. Registrar agrees to comply with any ICANN-adopted Specification or Policy that establishes a Proxy Accreditation Program. Registrar also agrees to reasonably cooperate
with ICANN in the development of such program. </font></div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div><font face="Calibri,sans-serif"><b>Lets plan now for the transition to Accredited P/P providers: </b>Can we have a communications plan to alert registrants, registrars, and P/P providers in advance of the date the Accreditation System becomes effective,
such that all parties have time and incentive to convert to use only Accredited services?</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif"><b>What about Registrars who don’t use the 2013 RAA?</b> Seems that a registrant could avoid the requirement to use only Accredited P/P providers, by sticking with a registrar who has
<u>not</u> adopted the 2013 RAA. Any registrar who serves only legacy TLDs could avoid signing the 2013 RAA, right? Must all registrars must convert to 2013 RAA at their next renewal? What is the schedule for expiration of legacy RAA contracts?</font></div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Thanks again for handling this via phone. We look forward to participating in your WG session in Singapore.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Best,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Steve</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Steve DelBianco</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Vice Chair for Policy Coordination</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">Business Constituency</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, February 27, 2014 at 5:06 PM<br>
<span style="font-weight:bold">To: </span>Glen de Saint Géry <<a href="mailto:Glen@icann.org">Glen@icann.org</a>>, Elisa Cooper <<a href="mailto:Elisa.Cooper@markmonitor.com">Elisa.Cooper@markmonitor.com</a>><br>
<span style="font-weight:bold">Cc: </span>Benedetta Rossi <<a href="mailto:bc-secretariat@icann.org">bc-secretariat@icann.org</a>>, Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>>, "<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>"
<<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: Reminder: Request for input: GNSO's Working Group on Privacy & Proxy Services Accreditation<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Yes, thanks very much, Elisa and Steve! If you are still planning to provide feedback, I am sure the WG will be happy to receive it even after tomorrow. Perhaps the Singapore meeting could be a date to aim for, since the WG will be having a face to face
meeting there and community members are of course welcome to attend it, so having community feedback sent in by then might be helpful.</div>
<div><br>
</div>
<div>I hope this helps, and thank you!</div>
<div><br>
</div>
<div>Cheers</div>
<div>Mary</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Mary Wong</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Senior Policy Director</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Internet Corporation for Assigned Names & Numbers (ICANN)</font></font></div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</span></div>
</span></div>
</span><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></div>
</div>
</span>
</body>
</html>