<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1276714527;
mso-list-template-ids:1797808942;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1938245469;
mso-list-type:hybrid;
mso-list-template-ids:-54373230 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D;mso-fareast-language:EN-US">Dear Co-chairs<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D;mso-fareast-language:EN-US">On the last call I proposed that we allow for a proposal to be presented for discussion by an alternate, if the circumstances are such that the proposer cannot make
any of the proposed dates but they are able to find someone else willing to shepherd the proposal on their behalf. I note that the intention is to give a proposer flexibility to request a meeting slot that suits them, and so it is to be hoped that a proposer
would rarely, if ever, need to take advantage of an alternate, but it would really unfortunate to exclude a proposal which someone else was willing to support because, for circumstances which might be beyond their control, a suitable slot cannot be found for
the proposer. This would probably fit within the document within the first bullet of section 6.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D;mso-fareast-language:EN-US">This did not seem to be viewed as controversial when I raised it on the call, and indeed there was some support. Can you please explain why this has not been included?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#76923C">Susan Payne<br>
Head of Legal Policy</span></b><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D">
</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D">|
</span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#C39209">Valideus Ltd<br>
</span></b><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#76923C"><br>
</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D">E:
</span><span style="color:#1F497D"><a href="mailto:susan.payne@valideus.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#76923C">susan.payne@valideus.com</span></a></span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D">
</span><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#76923C"><br>
</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D">D: +44 20 7421 8255<b><br>
</b>T: +44 20 7421 8299<b><br>
<br>
</b><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> gnso-rpm-wg [mailto:gnso-rpm-wg-bounces@icann.org]
<b>On Behalf Of </b>Julie Hedlund<br>
<b>Sent:</b> 29 August 2018 00:13<br>
<b>To:</b> gnso-rpm-wg@icann.org<br>
<b>Subject:</b> [gnso-rpm-wg] Revised Proposed Procedures for URS Policy and Operational Recommendations<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Dear RPM PDP Working Group members<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">On behalf of the Co-Chairs, please see the attached revised Proposed Procedures for URS Policy and Operational Recommendations. As noted previously, the Co-Chairs believe that these procedures
will efficiently and fairly facilitate the RPM PDP Working Group discussion and development of URS policy and operational recommendations over the course of the upcoming Working Group meetings in September, beginning with our next meeting.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">Please note that the deadline for submission of member proposals for URS operational and policy modifications has been extended to COB on Thursday, September 6th.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The Co-Chairs have fully discussed and considered the comments on the initial version of the Proposed Procedures. As a result, the attached revised document, with changes in redline, includes
the following changes from the version initially sent on 21 August, and revised per the Working Group discussion at the meeting on 22 August:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 1, bullet 1: Add the sentence, “The WG will be working off from the “Super Consolidated URS Topics Table” for the review of the URS Sub Teams’ operational
and policy proposals.”<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 1, bullet 2: Date for commencement of staff presentations of Sub Team proposals changed to August 29.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 2, bullet 1: Clarification that the WG will be addressing Sub team “operational and policy” proposals.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 2, bullet 6: Change the deadline for proposal submissions from COB Friday, 31 August to COB Thursday, 06 September so that the Co-Chairs will begin to
consider proposals at their weekly meeting on Friday, 07 September.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 3, new bullet 4: Added a procedure to address Phase 2 proposals.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 6:
<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Change “significant support” to “adequate” (meaning support from Working Group members that in the Co-Chairs’ judgment is of a level for which public comments
should be sought via the Initial Report) throughout.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Under the heading “During the presentation”:
<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Bullet 3: add “However, if there is exceptionally high interest in a topic, the Co-Chairs would have discretion to increase the discussion time.”<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Bullet 4: change “two (2) minutes” to “four (4) minutes” to allow individual proposers more time to respond to comments.<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">Section 7:<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Change “significant support” to “adequate support” throughout.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Bullet 1: add “the Co-Chairs may suggest for WG consideration a consolidated proposal that includes elements of the multiple related proposals.”<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:11.0pt">Bullet 2: change “substantial opposition” to “substantial material opposition” and after “Initial Report” add, “for the purpose of soliciting public comment thereon.”
Additional language also clarifies that Sub Team proposals only enjoy a rebuttable presumption of adequate support for inclusion in the Initial Report to solicit community input, but no advantage over individual proposals for inclusion as Final Report recommendations.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The Co-Chairs would like to re-emphasize that the Working Group faces a significant challenge in adhering to its current timeline and completing its URS work for the Initial Report by the end
of September. It is therefore imperative that the Working Group agrees on tight procedures that provide a fair opportunity for all members to propose operational and policy modifications to the URS. In addition, the procedures should facilitate identification
of those proposals that lack an adequate level of support as well as those that may be deferred to Phase Two of the Working Group’s efforts because they are substantially intertwined with UDRP issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The Co-Chairs note that there have been questions raised as to the role of Sub Teams vis-à-vis that of the full Working Group, particularly in relation to the treatment of Sub Team proposals.
Under the GNSO Working Group Guidelines, Sub Teams may be used “as an efficient means of delegating topics or assignments to be completed [and] sub-teams report their results to the whole Working Group for review and approval” (Section 2.3). The three URS
Sub Teams have spent a considerable amount of time and conducted extensive deliberations that have resulted in their various reports to the full Working Group and the findings and proposals now reflected in the Super Consolidated URS Topics Table. As highlighted
during the last Working Group call, the full Working Group is now being requested to carefully review and discuss those proposals. It is also important to note that the Working Group Guidelines “encourage representational balance [on Sub Teams] to the degree
possible. However, it should be understood that there will not always be volunteers from every interest group and that it is often acceptable to have a small sub-team that is not totally representational perform an initial role that will later be reviewed
by a broader more representational group” (Section 2.2.). In any event, the revised Procedures make clear that Sub Team recommendations only have a rebuttable presumption, subject to Working Group feedback, of enjoying an adequate level of support to be included
in the Initial Report for the purpose of soliciting community input; and that Sub Team proposals, like those from individuals, will only become Final Report recommendations if they achieve Full Consensus or Consensus.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Unless Working Group members have specific objections to the revisions or wish to raise concerns that have not been voiced to date, these Proposed Procedures will go into effect as of the next
Working Group meeting on Wednesday, 05 September, during which the Working Group will use the “Super Consolidated URS Topics Table” (as updated by staff following the last Sub Team calls) for the review of the URS Sub Teams’ proposals. A new version of that
document will be sent shortly and Working Group members are requested to be prepared to discuss the Sub Teams’ proposals for policy or operational changes. For those instances where Sub Teams have agreed that no additional policy work is required, WG members
can propose otherwise.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Mary, Julie, Ariel & Berry<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">On behalf of the RPM PDP Working Group Co-Chairs<o:p></o:p></span></p>
</div>
</body>
</html>