<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:0in;
margin-bottom:.0001pt;
font-size:11.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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:882062658;
mso-list-type:hybrid;
mso-list-template-ids:-2076176028 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText"><a name="_MailEndCompose">George:<o:p></o:p></a></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">The proposed procedure is a work in progress and will not be made final until after WG discussion and feedback on tomorrow’s call, as well as on the email list for a day or two after – we want
WG members to understand and feel comfortable with this proposed procedural path forward before it is implemented.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Our intent is to have a fair, efficient and uniform procedure that provides the same format and structure for the consideration of all WG proposals, and the same criteria for inclusion in the
Initial report for public comment. We have no intent to discriminate against any specific proposal or WG member.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">This procedural proposal is biased toward the inclusion of proposals in the Initial Report (IR) for the purpose of soliciting public comment from the broader community. In other words, if a
proposal has substantial support within the WG it will be included in the IR even if it also elicits substantial opposition – all wisdom does not reside within our ranks, and a community commenter may well provide a suggestion for compromise that narrows the
gap in views. (On the other hand, the consensus call process for the Final Report will be quite different, as only proposals that have achieved Full Consensus, or Consensus, within the WG will go forward to Council, while those that continue to attract both
substantial support and opposition will be categorized as having divergence and will go by the wayside unless the opposing sides reach compromise.) <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Addressing your concerns (and the other co-chairs may well have additional views they wish to share):<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l0 level1 lfo1"><span style="mso-bookmark:_MailEndCompose">It is intended that, for those proposals for which a poll after WG call discussion is utilized to determine whether substantial support exists, the results shall
be transparent – that the names of participants and the position taken shall be published.<o:p></o:p></span></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo1"><span style="mso-bookmark:_MailEndCompose">There is a starting presumption that recommendations emerging from a sub-team already possess substantial support because they were collectively developed and
agreed upon by multiple WG members from varied interests and therefore should be included in the IR for comment, especially since the bias of this process is toward inclusion. My personal view is that a sub-team recommendation should be included even if there
is substantial opposition, and should be excluded and merely documented/referenced only if full WG discussion reveals that it enjoys no support outside the sub-team membership and also incites substantial opposition. In any event, when a sub-team recommendation
elicits substantial opposition it will be the subject of a poll to determine overall WG support/opposition.
<o:p></o:p></span></li></ul>
<p class="MsoPlainText" style="margin-left:.5in"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in"><span style="mso-bookmark:_MailEndCompose">There is no presumption that substantial support already exists for a new proposal coming from an individual WG member because it comes from a single person rather
than a team. That said, if it receives substantial support from other WG members it will be included in the IR for comment, even if it also generates substantial opposition.<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in"><span style="mso-bookmark:_MailEndCompose">So I personally believe that what you characterize as a “double standard” is actually just a recognition that sub-team recommendations have been collectively developed
and already achieved support from multiple members of the WG, while proposals from individual members have yet to be vetted. But this is open for discussion tomorrow.<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l0 level1 lfo1"><span style="mso-bookmark:_MailEndCompose">Finally, on the subject of setting an objective measure for the determination of whether substantial support or opposition exists for a particular proposal,
that is difficult to do in advance as different proposals may attract significantly varying volumes of oral comment or poll participation, as well as because the GNSO WG Guidelines do not permit voting. That said, the co-chairs are committed to acting in
a transparent and uniform manner in regard to all proposals, and to articulating the basis for any determination that a proposal does or does not have substantial support (which is the key criteria, given that once that exists a proposal will be included in
the IR for comment even if substantial opposition also exists).<o:p></o:p></span></li></ul>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">I hope that you and other members of the WG find my response to be helpful and I look forward to our discussion on tomorrow’s call.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Philip<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Philip S. Corwin<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Policy Counsel<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">VeriSign, Inc.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">12061 Bluemont Way<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Reston, VA 20190<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">703-948-4648/Direct<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">571-342-7489/Cell<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">"Luck is the residue of design" -- Branch Rickey<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoPlainText">-----Original Message-----<br>
From: gnso-rpm-wg [mailto:gnso-rpm-wg-bounces@icann.org] On Behalf Of George Kirikos<br>
Sent: Tuesday, August 21, 2018 2:51 PM<br>
To: gnso-rpm-wg@icann.org<br>
Subject: [EXTERNAL] Re: [gnso-rpm-wg] Proposed Procedures for URS Policy and Operational Recommendations; Draft Agenda for 22 Aug Call</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi folks,,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">At this time, I have 2 concerns with the Proposed Procedures for URS Policy and Operational Recommendations.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">1. On page 3, the use of a poll is mentioned. In keeping with ICANN's transparency requirements, that poll should not be an anonymous poll.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">2. On page 4, there's a double-standard in the default treatment of Sub Team Recommendations vs. Working Group member submissions, and that double-standard should be eliminated, as there was no deference to the work of the sub teams.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In particular, Sub Team recommendations are included by default "unless there is substantial opposition".<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On the other hand, Working Group member submissions are *excluded* by default, unless there is substantial support.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The standard for inclusion should be made identical for all proposals, regardless of where they originated.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Also, the standard should be objectively stated *prior* to measurement, to ensure that a "substantial support" or "substantial opposition" (whichever uniform standard ultimately applies) is not determined in an ad hoc manner.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Sincerely,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">George Kirikos<o:p></o:p></p>
<p class="MsoPlainText">416-588-0269<o:p></o:p></p>
<p class="MsoPlainText"><a href="http://www.leap.com/"><span style="color:windowtext;text-decoration:none">http://www.leap.com/</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On Tue, Aug 21, 2018 at 12:52 PM, Ariel Liang <<a href="mailto:ariel.liang@icann.org"><span style="color:windowtext;text-decoration:none">ariel.liang@icann.org</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> Dear RPM PDP Working Group members<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> On behalf of the Co-Chairs, the attached document is a proposal that
<o:p></o:p></p>
<p class="MsoPlainText">> the Co-Chairs hope will facilitate the RPM PDP Working Group
<o:p></o:p></p>
<p class="MsoPlainText">> discussion and development of URS policy and operational
<o:p></o:p></p>
<p class="MsoPlainText">> recommendations over the course of the upcoming Working Group meetings
<o:p></o:p></p>
<p class="MsoPlainText">> in August and September, beginning with our next meeting.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> The Working Group faces a significant challenge in adhering to its
<o:p></o:p></p>
<p class="MsoPlainText">> current timeline and completing its URS work for the Initial Report by
<o:p></o:p></p>
<p class="MsoPlainText">> the end of September. It is therefore imperative that the Working
<o:p></o:p></p>
<p class="MsoPlainText">> Group agrees on tight procedures that provide a fair opportunity for
<o:p></o:p></p>
<p class="MsoPlainText">> all members to propose operational and policy modifications to the
<o:p></o:p></p>
<p class="MsoPlainText">> URS. In addition, the procedures should facilitate identification of
<o:p></o:p></p>
<p class="MsoPlainText">> those proposals that lack significant support and thus may be deferred
<o:p></o:p></p>
<p class="MsoPlainText">> to the Initial Report for public comment, or to Phase Two of the WG’s
<o:p></o:p></p>
<p class="MsoPlainText">> efforts because they are substantially intertwined with UDRP issues.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> In addition to the proposal, please also review the online survey form
<o:p></o:p></p>
<p class="MsoPlainText">> for WG members to submit proposals. Upon request, staff can also
<o:p></o:p></p>
<p class="MsoPlainText">> provide a .doc version of the online survey form to WG members who
<o:p></o:p></p>
<p class="MsoPlainText">> have difficulty accessing the online survey.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Please review the proposal and come prepared to discuss them at the
<o:p></o:p></p>
<p class="MsoPlainText">> meeting on Wednesday, 22 August, at 17:00 UTC. Here also is a draft
<o:p></o:p></p>
<p class="MsoPlainText">> agenda for your<o:p></o:p></p>
<p class="MsoPlainText">> review:<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Draft Working Group Agenda:<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Review Agenda/SOIs<o:p></o:p></p>
<p class="MsoPlainText">> Discussion of Proposed Procedures for URS Policy and Operational
<o:p></o:p></p>
<p class="MsoPlainText">> Recommendations (see attached Proposed Procedures for URS Policy and
<o:p></o:p></p>
<p class="MsoPlainText">> Operational Recommendations) Begin consideration of the sub team
<o:p></o:p></p>
<p class="MsoPlainText">> recommendations, under the proposed framework (see attached Super
<o:p></o:p></p>
<p class="MsoPlainText">> Consolidated URS Topics Table – with Findings, Issues, and Suggestions
<o:p></o:p></p>
<p class="MsoPlainText">> from all Three URS Sub Teams for Working Group<o:p></o:p></p>
<p class="MsoPlainText">> Discussion)<o:p></o:p></p>
<p class="MsoPlainText">> AOB<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Best,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Mary, Julie, Ariel & Berry<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> On behalf of the RPM PDP Working Group Co-Chairs<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> gnso-rpm-wg mailing list<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:gnso-rpm-wg@icann.org"><span style="color:windowtext;text-decoration:none">gnso-rpm-wg@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">
<span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</span></a><o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">gnso-rpm-wg mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:gnso-rpm-wg@icann.org"><span style="color:windowtext;text-decoration:none">gnso-rpm-wg@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg"><span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</span></a><o:p></o:p></p>
</div>
</body>
</html>