<html><head></head><body 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>Dear all,</div><div><br></div><div>Following from Steve’s email, here is the proposed agenda for the WG call on Tuesday 3 March; please also note the attached revised Work Plan for this WG, which takes into account recent discussions and updates our timeline for publication of our Initial Report and delivery of a Final Report to the GNSO Council:</div><ol><li>Roll call/updates to SOI</li><li>Finalize discussion on draft document on discussion standards</li><li>Discuss remaining questions concerning Category F (Reveal) - see below</li><li>Discuss proposed WG face-to-face facilitated meeting at ICANN53</li><li>Next steps/next meeting</li></ol><div>To assist with the WG’s discussion of agenda item #3, here are the outstanding questions for Category F, as phrased in the draft Initial Report under discussion (they can be found in Section 1.3.2 of the Executive Summary):</div><div><br></div><div><ul type="disc" style="margin-bottom: 0in; margin-top: 0in;"><li class="MsoNormal" style="line-height: 24px; font-family: Garamond;"><span lang="EN-GB" style="font-family: Calibri;"><font size="3">Should there be uniform minimum standards for accredited P/P providers to apply in determining when to Disclose or Publish, or in verifying a requestor’s identity?<o:p></o:p></font></span></li><li class="MsoNormal" style="line-height: 24px; font-family: Garamond;"><span lang="EN-GB" style="font-family: Calibri;"><font size="3">Should it be mandatory for accredited P/P providers to comply with express requests from LEA in the provider’s jurisdiction not to notify a customer? Should there be mandatory Publication for certain types of activity e.g. malware/viruses or violation of terms of service relating to illegal activity? What (if any) should the remedies be for unwarranted Publication?<o:p></o:p></font></span></li><li class="MsoNormal" style="line-height: 24px; font-family: Garamond;"><span lang="EN-GB" style="font-family: Calibri;"><font size="3">Should it be mandatory for accredited P/P providers to comply with express requests for Disclosure for the purpose of sending cease and desist letters or notices of formal legal proceedings against the customer? Should customer notification in such cases be mandatory?</font></span></li></ul><div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-style: normal; font-weight: normal; text-decoration: none;"><br></span></div></div><div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-style: normal; font-weight: normal; text-decoration: none;">Cheers</span></div><div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-style: normal; font-weight: normal; text-decoration: none;">Mary</span></div><div><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 14px; font-style: normal; font-weight: normal; text-decoration: none;"><br></span></div><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><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Telephone: +1 603 574 4892</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Email: mary.wong@icann.org</font></font></div><div><br></div></div></div><div><br></div></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> <Metalitz>, Steven <<a href="mailto:met@msk.com">met@msk.com</a>><br><span style="font-weight:bold">Date: </span> Monday, March 2, 2015 at 09:54<br><span style="font-weight:bold">To: </span> "'PPSAI (<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>)'" <<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br><span style="font-weight:bold">Subject: </span> [Gnso-ppsai-pdp-wg] Updated document re disclosure standards<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div 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"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><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: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;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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;}
.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]--><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">PPSAI WG members,
<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Attached please find an updated version of the document Graeme and I circulated prior to last week’s meeting. This updated version includes three or four wording
tweaks, intended to reflect the discussion on last week’s call. Looking forward to further discussion on tomorrow’s call.
<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz
<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: black;">From:
</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: black;"><Metalitz>, Steven <<a href="mailto:met@msk.com">met@msk.com</a>><br><b>Date: </b>Monday, February 23, 2015 at 11:57<br><b>To: </b>"'PPSAI (<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>)'" <<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br><b>Subject: </b>Re: [Gnso-ppsai-pdp-wg] Category F -- updated status report and text for discussion<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p></div><blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"><div><div><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">PPSAI WG members,
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">This follows up on our note of Feb. 3 providing a status report on subgroup discussions among some IP interests and p/p service providers regarding p/p disclosure
standards. To reiterate, the group’s work is not meant to obviate or displace the work of the larger PPSAI WG on this issue – rather, it is meant to constructively contribute to the discussion by producing one proposal on this issue for the larger group’s
consideration. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In light of further consideration and of the need to move forward the WG discussion on Category F, we present the attached document that we hope will help provide
a framework for discussion of the disclosure issue in the WG. We emphasize that this is not a proposal from IPC, the Registrar Stakeholder Group, or any subset of either, and that we fully anticipate the text to be modified and improved through further discussion
at the WG level. (We also acknowledge that the WG may find the proposal wholly unsatisfactory but hope that it will at least help advance debate.)
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">The attached is put forward as a starting point, to use intellectual property infringement complaints as one illustrative example of minimum disclosure standards,
in a framework that addresses (1) a service provider process for intake of requests; (2) general templates that requests would have to meet in order to trigger service provider action; and (3) principles governing service provider action in response to a
conforming request. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">We look forward to the discussion of this document among WG members.
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Graeme Bunton</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="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: 10pt; font-family: Tahoma, sans-serif; color: black;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: black;"> Metalitz, Steven
<br><b>Sent:</b> Tuesday, February 03, 2015 3:57 PM<br><b>To:</b> PPSAI (<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>)<br><b>Subject:</b> Category F -- status report</span><span style="color:black"><o:p></o:p></span></p></div></div><p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Dear WG colleagues,
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">As you know, several PPSAI Working Group members, including representatives of the IPC and privacy and proxy service providers, have endeavored to develop a
collaborative proposal on the minimum standards for disclosure (Category F). The group’s work is not meant to obviate or displace the work of the larger group on this issue – rather, it is meant to constructively contribute to the discussion by producing one
proposal on this issue for the larger group’s consideration. This is an update on this sub-group’s progress.</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">But first, a little background: At the face-to-face meeting of the PPSAI Working Group in Los Angeles on October 10, 2014, one important topic was minimum standards
for disclosure of contact information of customers of privacy/proxy services who may or may not be using their private domain name registrations to carry out infringing or other abusive activities.
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Prior to the face-to-face meeting, IPC participants in the Working Group circulated a proposal on this topic. A responsive redline was circulated to the WG
by Volker Greimann. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Following extensive discussion of these proposals and of the topic in general at the face-to-face meeting, a sub-group of WG participants have continued this
discussion. The sub-group includes participants from the IPC and privacy/proxy service providers. Meeting by teleconference and working over e-mail, the sub-group has sought to develop a text that could be jointly presented to the PPSAI Working Group as a
framework for further discussion on the issue of standards for disclosure. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Some progress has been made, and the sub-group is continuing its efforts with the goal of producing a document for presentation to the PPSAI Working Group as
soon after the Singapore ICANN meeting as feasible. If such a document is completed, it is hoped that it would be a constructive contribution to eventual WG approval of a set of recommendations on “Category F” for inclusion in the Draft Report of the WG.
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Unlike the documents discussed by the full WG last October, the framework under discussion does not purport to establish a single general policy for when disclosure
of contact information in cases of alleged abusive activities would be available. Instead, it seeks to focus more narrowly on intellectual property infringement complaints as one illustrative example of minimum disclosure standards. The framework would describe
(1) a service provider process for intake of requests; (2) general templates that requests would have to meet in order to trigger service provider action; and (3) principles governing service provider action in response to a conforming request. While considerable
progress has been made in the first two areas, a number of critical issues remain to be resolved in the third area, and discussion has not been concluded on any of the areas.
</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">The expressed common goal of the discussion group participants is a framework that would give requestors a higher degree of certainty and predictability as
to if, when and how they could obtain what level of disclosure; that would preserve for service providers a sufficient degree of flexibility and discretion in acting upon requests for disclosure; and that would include reasonable safeguards and procedures
to protect the legitimate interests of customers of accredited proxy/privacy service providers. Of course, balancing these interests is the difficult task before our working group. As stated, participants in the discussion group hope to be able to make a
constructive contribution to the WG’s efforts to do so. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Graeme Bunton</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="color:black"><o:p></o:p></span></p></div></div></blockquote></div></div></div></blockquote></span></body></html>