<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:"Adobe Clean";
panose-1:2 11 5 3 2 4 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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:"Adobe Clean";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean"">Greg:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean"">No one is mandating which version the sub team works with initially. I, for one, thought it was obvious that you all (if you have volunteered for the sub team) would begin with the
document as edited by Jon and Susan.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean"">J. Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean""><o:p> </o:p></span></p>
<div>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border:none;border-top:solid #6A737B 1.0pt">
<tbody>
<tr>
<td width="43" style="width:32.25pt;border:none;padding:0in 15.75pt 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><img width="44" height="73" id="_x0000_i1025" src="cid:image001.gif@01D2DECD.426D7FA0" alt="ttps://inside.corp.adobe.com/content/dam/brandcenter/images/image002.gif"></span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
</td>
<td width="580" valign="bottom" style="width:435.0pt;border:none;padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="767" style="width:575.25pt">
<tbody>
<tr>
<td width="239" valign="bottom" style="width:179.25pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:Calibri">J. Scott Evans</span></b><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
</td>
<td width="204" valign="bottom" style="width:153.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">408.536.5336 (tel)<o:p></o:p></span></p>
</td>
<td width="324" valign="bottom" style="width:243.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">345 Park Avenue, Mail Stop W11-544<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="239" valign="bottom" style="width:179.25pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Director, Associate General Counsel<o:p></o:p></span></p>
</td>
<td width="204" valign="bottom" style="width:153.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">408.709.6162 (cell)<o:p></o:p></span></p>
</td>
<td width="324" valign="bottom" style="width:243.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">San Jose, CA, 95110, USA<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="239" valign="bottom" style="width:179.25pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Adobe. Make It an Experience.<o:p></o:p></span></p>
</td>
<td width="204" valign="bottom" style="width:153.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">jsevans@adobe.com<o:p></o:p></span></p>
</td>
<td width="324" valign="bottom" style="width:243.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">www.adobe.com<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
<td valign="bottom" style="border:none;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> <o:p></o:p></span></p>
</td>
</tr>
<tr>
<td colspan="3" style="border:none;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Adobe Clean""><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-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black"><gnso-rpm-wg-bounces@icann.org> on behalf of Greg Shatan <gregshatanipc@gmail.com><br>
<b>Date: </b>Tuesday, June 6, 2017 at 1:49 PM<br>
<b>To: </b>Amr Elsadr <amr.elsadr@icann.org><br>
<b>Cc: </b>"gnso-rpm-wg@icann.org" <gnso-rpm-wg@icann.org><br>
<b>Subject: </b>Re: [gnso-rpm-wg] Co-Chair Statement on Refinement of Draft Questions for Private Protections Sub team<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:Verdana">The risk of a debate about scope matters that would "inordinately delay" the work of the WG seems to be very small, considering that there was no support on the list for the chairs' strawman and a significant
number of consistent criticisms and edits revising that strawman. At the least, that would seem to indicate that the subgroup should start with Jon's edited version. At the risk of being blunt, there seems to be a bit too much "pride of authorship" on display
here.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Verdana"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jun 6, 2017 at 3:53 PM, Amr Elsadr <<a href="mailto:amr.elsadr@icann.org" target="_blank">amr.elsadr@icann.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Dear Working Group Members,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">On behalf of the Co-Chairs of the GNSO Review of all RPMs in all gTLDs PDP Working Group, please find a statement below prepared by the Co-Chairs
on the proposed questions, which will be considered by the Private Protections Sub Team.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Thanks.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Amr</span><o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">The co-chairs are aware that questions have been raised by some WG members in regard to whether some of the questions proposed in the document titled
“DRAFT QUESTIONS FOR PRIVATE PROTECTIONS SUB TEAM 28 May 2017” exceed the scope of the Charter for this WG. In preparing this draft document the co-chairs expected that any relevant issues, including Charter scope issues, would be fully explored by the subteam
that will be refining the questions and identifying related data needs. We continue to believe that would be the most efficient way to proceed and that debating scope matters at the full WG level in regard to questions that may be deleted or substantially
modified by the subteam would not be an efficient procedure for the full WG; and would inordinately delay our ongoing work on the TMCH, Sunrise Registrations, and Trademark Claims matters. At least 16 WG members have already indicated that they wish to participate
in the subteam, which should ensure a robust discussion and diversity of viewpoints.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">WG members who have concerns about whether some proposed questions go beyond the scope of the WG Charter will have full opportunity to make their
case within the subteam, and to continue to raise those concerns if the subteam recommends that the full WG consider questions that they object to on scope grounds. In other words, the subteam’s conclusion on scope matters will be a preliminary recommendation
subject to further review by the full WG prior to initiating full WG discussion of the refined questions. Likewise, if any WG members believe that a question rejected for scope reasons is an important one that should be explored by this WG, they shall have
the opportunity to make the case for seeking a Charter amendment from Council.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">The bottom line is that we expect and shall seek to fully address and resolve any and all scope issues before the full WG engages in discussions concerning
the final list of refined questions relating to this subject. It is also worth noting the Guidelines for GNSO WGs make it clear that: <i>“Decisions made by sub-teams should always be shared with the larger working group and a call for consensus must be made
by the entire WG.”</i></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt">Therefore, our recommendation to the full WG is that, for the sake of procedural efficiency, and with assurance that the rights and perspectives
of all WG members will be taken into account at every stage of our process, we should launch the new subteam tasked with refining these questions at the conclusion of this week’s WG call and delegate the near term consideration of Charter scope matters to
that subteam.</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">In the interim period while the subteam is deliberating, given the possibility that one or more of the refined questions returned by it to the WG
may still raise Charter scope concerns, we shall consult with supporting policy staff in regard to precedent and advisable procedure for resolving such concerns within a policy WG.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">As a final safeguard for all WG members, we note that the Guidelines also state: <i>“Any WG member that believes that his/her contributions are being
systematically ignored or discounted or wants to appeal a decision of the WG … should first discuss the circumstances with the WG Chair. In the event that the matter cannot be resolved satisfactorily, the WG member should request an opportunity to discuss
the situation with the Chair of the Chartering Organization or their designated representative.”</i> The co-chairs are always ready and willing to engage with any aggrieved member, but believe it would be premature to do so prior to subteam deliberations,
and hope that all views on scope and other relevant matters can be resolved via amicable consensus and thereby avoid any need for involving Council.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">We hope this recommendation will be acceptable to the WG and welcome further discussion of proper procedure on this week’s full WG call.</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-rpm-wg&data=02%7C01%7C%7C5bfdebd7ece74a1daf5008d4ad1d827e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636323789632106357&sdata=Unz88%2BJFFny8sKnJ2g8OO56%2FbZUS0T1%2FyGe6gfeS%2FiQ%3D&reserved=0" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>