<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;">First -a big thanks to Kathy for the comments. Next, a big thanks to Steve and Graeme for the paper. Between both inputs, there is both plenty to discuss, but possible avenues for ways forward in what are thorny issues for all of us<div><br></div><div>Holly<br><div><div>On 3 Mar 2015, at 9:59 am, Kathy Kleiman <<a href="mailto:Kathy@kathykleiman.com">Kathy@kathykleiman.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000" style="font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Hi All,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">First, thank you, Steve, Graeme and All. I know a lot of people have spent a lot of time in the IP and Registrar Communities working on this draft. Tx you – and appreciate your invitation to comments and concerns!<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">I have reviewed the Draft carefully and have some initial comments to share.<span> <span class="Apple-converted-space"> </span></span>Although I spoke with people in the WG while preparing them, these comments are my own.(If there is problem with the formatting below, please let me know.)<o:p></o:p></div><p class="MsoListParagraphCxSpFirst" style="text-indent: -0.25in;"><span><span>1.<span> <span class="Apple-converted-space"> </span></span></span></span>General Comments<o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1in; text-indent: -0.25in;"><span><span>a.<span> <span class="Apple-converted-space"> </span></span></span></span>`Let’s make the wording more neutral. Let’s add “alleged” or “claimed” in all references of infringement (e.g., trademarks, copyrights of domain names/websites. Another good term would be “claimed infringement” -- which is the one used in similar sections of the Digital Millennium Copyright Act to the sections we are working on here.<span> </span><o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in;"><o:p> </o:p></p><p class="MsoListParagraphCxSpMiddle" style="text-indent: -0.25in;"><span><span>2.<span> <span class="Apple-converted-space"> </span></span></span></span>More substantive comments<o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1in; text-indent: -0.25in;"><span><span>a.<span> <span class="Apple-converted-space"> </span></span></span></span>Are we missing levels of protections for the Customer/Registrant?<span> <span class="Apple-converted-space"> </span></span>In the Digital Millennium Copyright Act (DMCA), there were two levels of protections for the “users.”<span> </span><o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; text-indent: -1.5in;"><span><span><span> <span class="Apple-converted-space"> </span></span>i.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span>The first was sanctions for misrepresentation. Basically, any company which knowingly materially misrepresents that material or activity is infringing is liable for damages, including costs and attorney fees caused from injury resulting from the misrepresentation. Don’t we need similar sanctions here?<o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in;"><o:p> </o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; text-indent: -1.5in;"><span><span><span> <span class="Apple-converted-space"> </span></span>ii.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span>A much higher bar for revealing the identity of the alleged infringer. The DMCA allows rapid takedown based on statements very similar to the one we proposing, but Reveal is a whole different story.<span> <span class="Apple-converted-space"> </span></span>The standard is much higher and goes through Court. Thus US Copyright Code, Sec 512(h), requires a subpoena to reveal data:<o:p></o:p></p><div style="margin: 0in 0in 0.0001pt 2.5in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>a.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">[Section 512] “(h) SUBPOENA TO IDENTIFY INFRINGER-<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2.5in; line-height: normal;"><span style="font-size: 12pt;">`(1) REQUEST- A copyright owner or a person authorized to act on the owner's behalf may request the clerk of any United States district court to issue a subpoena to a service provider for identification of an alleged infringer in accordance with this subsection…<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 1.5in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 1.5in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;">Shouldn’t we have a higher standard too?<span> <span class="Apple-converted-space"> </span></span>It seems important to balance the rights of both sides, including whether the Allegation of Illegality sufficiently outweighs the Privacy Interests and Rights of the Battered Women’s Shelter, Online Magazine or Bloggers posting unpopular views of corruption.<span> </span><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 1.5in; text-indent: -1.5in; line-height: normal;"><span style="font-size: 12pt;"><span><span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span>iii.<span> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">A deep concern about default. As I read the rules, if you don’t respond, you lose and your data is revealed.<span> </span>But this is a problem because we can think of many reasons why Customers/Registrants would not respond. For example:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2.5in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>a.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">Request came at the beginning of August,<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2.5in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>b.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">Request disappeared into spam;<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2.5in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>c.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">Registrant/Customer is unable to respond (perhaps language barriers); and/or<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2.5in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>d.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">Registrant/Customer is scared to respond.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 2in; text-indent: -0.25in; line-height: normal;"><span style="font-size: 12pt;"><span>2.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 12pt;">I would submit that in something as important as revealing identity and physical locations, there should be no automatic default. It is completely possible that a) the allegations are incorrect on their face (no jurisdictional overlap, for example), or b) that there are clear defenses on “its face,” e.g., on the website.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;">Thus, an anti-bullying group may post the copyrighted logo of a gang engaging in bullying (or worse) in a local school or neighborhood; is so, the gang’s allegation of copyright infringement could be clearly weighed against the “safe neighborhoods for all” activity taking place on the website.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;">Similarly, an online publication in Europe may have every right to use the logo and trademark of a large multinational it is criticizing, or the image of Mohammed, without having its identity and address revealed without due process.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 2in; line-height: normal;"><span style="font-size: 12pt;">Ditto for a battered women’s shelter posting a copyright logo, motto or design and urging women to watch for it and those bearing it.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;"> </span></div><div style="margin: 0in 0in 0.0001pt 2in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;">Due process is not automatic default, but a full and fair review of the website and other reachable information, even if the Customer/Registrant is unable to respond for herself or himself.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 2in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: normal;"><span style="font-size: 12pt;"> </span></div><p class="MsoListParagraphCxSpFirst" style="margin-left: 2in; text-indent: -0.25in;"><span><span>3.<span> <span class="Apple-converted-space"> </span></span></span></span>Option: we might consider Third Party or Independent Review. This is something that Steve and Graeme’s draft have already suggested for rejections of IP Owner Requests. It could serve Customers too by creating a review of default situations – or perhaps an independent forum for Service Providers who choose to outsource this difficult evaluation.<span class="Apple-converted-space"> </span><span> </span><o:p></o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 2in;"><o:p> </o:p></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; text-indent: -1.5in;"><span><span><span> <span class="Apple-converted-space"> </span></span>iv.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';"> <span class="Apple-converted-space"> </span></span></span></span>Privacy of communication between Customers and their Providers . The rules of Section III(A) seem to bar private communication with your Provider. Everything a Customer/Registrant might write to their Provider must be passed on verbatim (if I read this correctly).<span> <span class="Apple-converted-space"> </span></span>But that’s a problem for those with English as a second language (or third) or those without lawyers, and those simply trying to explain in clear and informal language to explain this situation. 0<o:p></o:p><o:p></o:p>What will happen, I am concerned, is that whatever informal response a Customer provides to its Provider will operate (unintended) as an Admission Against Interest or an unintended Waiver.<span> <span class="Apple-converted-space"> </span></span><o:p></o:p><o:p> </o:p></p><p class="MsoListParagraphCxSpLast" style="margin-left: 1.5in;">Further, the Customer/Registrant might inadvertently reveal a bit about their identity or even location – trying to explain their position clearly to the Provider – and this should not be passed on to the Requester automatically either. <span class="Apple-converted-space"> </span><o:p></o:p><o:p></o:p>I am not sure of th answer here as IP Owners should know something about the response, but not necessarily the full communication of the Customer (e.g., he is stalking me).<span class="Apple-converted-space"> </span><br></p><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Thanks for reading!<span> </span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Best,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Kathy</div><br><br><div class="moz-cite-prefix">On 3/2/2015 9:54 AM, Metalitz, Steven wrote:<br></div><blockquote cite="mid:E5B4A2ED43DFAE4F9E710FA54FEF8F6229B33059@LAEX02.MSK.local" type="cite"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">PPSAI WG members,<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><Metalitz>, Steven <<a moz-do-not-send="true" href="mailto:met@msk.com" style="color: purple; text-decoration: underline;">met@msk.com</a>><br><b>Date:<span class="Apple-converted-space"> </span></b>Monday, February 23, 2015 at 11:57<br><b>To:<span class="Apple-converted-space"> </span></b>"'PPSAI (<a moz-do-not-send="true" href="mailto:gnso-ppsai-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>)'" <<a moz-do-not-send="true" href="mailto:gnso-ppsai-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>><br><b>Subject:<span class="Apple-converted-space"> </span></b>Re: [Gnso-ppsai-pdp-wg] Category F -- updated status report and text for discussion<o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"> </span></div></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border-style: none none none solid; border-left-color: rgb(181, 196, 223); border-left-width: 4.5pt; padding: 0in 0in 0in 4pt; margin: 5pt 0in 5pt 3.75pt;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">PPSAI WG members,</span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Graeme Bunton</span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz</span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><span class="Apple-converted-space"> </span>Metalitz, Steven<span class="Apple-converted-space"> </span><br><b>Sent:</b><span class="Apple-converted-space"> </span>Tuesday, February 03, 2015 3:57 PM<br><b>To:</b><span class="Apple-converted-space"> </span>PPSAI (<a moz-do-not-send="true" href="mailto:gnso-ppsai-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>)<br><b>Subject:</b><span class="Apple-converted-space"> </span>Category F -- status report</span><span style=""><o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style=""> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Dear WG colleagues, </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><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=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Graeme Bunton</span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz</span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style=""><o:p></o:p></span></div></blockquote></div><br><fieldset class="mimeAttachmentHeader"></fieldset><br><pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre></blockquote><br>_______________________________________________<br>Gnso-ppsai-pdp-wg mailing list<br><a href="mailto:Gnso-ppsai-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">Gnso-ppsai-pdp-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></div></blockquote></div><br></div></body></html>