<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:"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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></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="MsoNormal"><a name="_MailEndCompose">Paul:<o:p></o:p></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">The co-chairs already promulgated and the WG already accepted the standard that any individual WG member that demonstrated “adequate support” would be include in the IR for the purpose of soliciting
public WG. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">What I stated on the call you missed was a personal view that any proposal submitted by a trade association with broad breadth of membership – whether INTA or ICA – likely meets that standard.
Some agreed, others did not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">When we get to the Final Report only those proposals that demonstrate consensus support will be included as recommendations.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">Philip<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">Philip S. Corwin<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">Policy Counsel<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">VeriSign, Inc.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN" style="font-family:"Arial",sans-serif">12061 Bluemont Way<br>
Reston, VA 20190<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">703-948-4648/Direct<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">571-342-7489/Cell<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-family:"Arial",sans-serif">"Luck is the residue of design" -- Branch Rickey<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b>From:</b> gnso-rpm-wg [mailto:gnso-rpm-wg-bounces@icann.org]
<b>On Behalf Of </b>Paul Tattersfield<br>
<b>Sent:</b> Tuesday, October 09, 2018 7:01 AM<br>
<b>To:</b> gnso-rpm-wg <gnso-rpm-wg@icann.org><br>
<b>Subject:</b> [EXTERNAL] [gnso-rpm-wg] Dealing with unsatisfactory proposals<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">I was unable to attend last week’s call because a couple of other long standing Wednesday meeting commitments, unfortunately it looks increasingly likely I will
unavoidable need to be elsewhere this week too and I have serious concerns with some of the proposals. I reviewd the AC chat recording from last week and I was very concerned to hear one of the co-chairs say he [personally] believed a proposal from an Industry
Group should get an automatic entry into to initial report.<br>
<br>
If I remember correctly we had a similar problem with the IGO/INGO draft report where those driving the working group wouldn't listen and the resulting public comment period wasn't kind. The working group then had to waste a not inconsiderable amount of its
time redrafting its report to correct that fundamental error.<br>
<br>
So what is the best way to ensure fundamentally flawed proposals are considered more fully before there is any expectation they will meet the initial report?<br>
<br>
Yours sincerely,<br>
<br>
<br>
Paul.</span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>