<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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><!--[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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks Anne for the comments. We will discuss further on the call on Monday. I do agree that Consensus Calls are from the full Working Group deliberations and not the Work
Tracks. But the discussions of the Work Track along with the public comments are all relevant for discussion points and for assisting with Consensus Determinations. We don’t just throw all of that out and start over.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With respect to guidelines as to how Cheryl and I will determine consensus, we will give this some more thought, but for anyone that thinks that we are going to come up with
a solid formula or objective test, I don’t want to set expectations. It is a qualitative analysis and the only guidelines we have are those cited below by Anne. If Cheryl or I were to add any requirements, then that would get criticized for being inconsistent
with the guidelines. At the end of the day, this is a subjective call by Cheryl and I which we will review with the group and for which the Working Group has the ability to question. We are going to do our best, but at the end of the day, we are humans and
by our very nature are not infallible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Jeff Neuman</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Senior Vice President <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Com Laude | Valideus<br>
</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">1751 Pinnacle Drive
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Suite 600, McLean<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">VA 22102, USA<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><br>
M: +1.202.549.5079<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">D: +1.703.635.7514<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">E:
</span><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1">jeff.neuman@comlaude.com</span></u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><br>
<a href="http://www.comlaude.com/">www.comlaude.com</a></span><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1"><o:p></o:p></span></u></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><br>
Liability cannot be accepted for statements made which are clearly the sender’s own and not made on behalf of Com Laude USA or Valideus USA. This message is intended solely for the addressee and may contain confidential information. If you have received this
message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment.Com Laude USA and Valideus are trading names of Consonum, Inc.</span><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1"><o:p></o:p></span></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Aikman-Scalese, Anne<br>
<b>Sent:</b> Tuesday, March 19, 2019 6:43 PM<br>
<b>To:</b> Rubens Kuhl <rubensk@nic.br>; gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 13 March 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I agree that public comment is not the measure of Consensus under WG Guidelines. However, neither is the strict counting of the “majority”. As Jeff has pointed out many times, Consensus is measured qualitatively,
not quantitatively. The Guidelines (pasted below) are NOT a matter of getting “hung up on terminology used in the triage”. Our goal is Consensus Call in about three months, so we had better have a good understanding as to how these recommendations are currently
being characterized in relation to consensus – since Leadership has the ultimate responsibility of designating the level of Consensus (or Consensus against), which is then put out to the full WG for feedback as to whether the WG members agree with the Consensus
level designations pursuant to 3.6 of the WG Guidelines. In fact, that is the very purpose for which we are reviewing these summaries, in preparation for the formal determination of Consensus. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In the example of our “test case” from the third F2F in Kobe re “autofill”, we can move the ball forward by gauging how the WG can get to Full Consensus rather than repeatedly arguing the position that the divergent
comments made “don’t make sense”. (For example, the way to get to Full Consensus might be to carve out the questions related to mission and purpose when it comes to “autofill”. Again, this is not a “new idea” to be delayed to some later policy-making effort.
) Other WG members, including Leadership, may have other “third alternatives’ to get to Full Consensus, which is where we want to be if at all possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In this regard, it is inappropriate to site to Work Track determinations (“without any dissent”) when in fact WG Members were told (when agreeing to an Initial Report with no Consensus Call) that the Work Track
recommendations, which did not include full WG participation, would not have any conclusive effect on Consensus determinations. (There would be way too much “bootstrapping” going on if this were the method of proceeding.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">The present full WG deliberations are the relevant deliberations for determining Consensus pursuant to GNSO Working Group Guidelines. The goal in the WG deliberations should be to get to Full Consensus wherever
possible. (That means compromise.) Guidelines are pasted below for reference. The levels are: Full Consensus, Unanimous Consensus, Consensus, Strong support but significant opposition, and Divergence (No Consensus). At this point, it seems pretty clear
that each recommendation is going to require a Consensus Designation. And it is definitely not too soon to have a preliminary discussion about those designations.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><img border="0" width="934" height="545" style="width:9.7291in;height:5.677in" id="Picture_x0020_1" src="cid:image001.png@01D4DEFC.4FEE7720"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><img border="0" width="865" height="864" style="width:9.0104in;height:9.0in" id="Picture_x0020_2" src="cid:image002.png@01D4DEFC.4FEE7720"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gnso-newgtld-wg [<a href="mailto:gnso-newgtld-wg-bounces@icann.org">mailto:gnso-newgtld-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Rubens Kuhl<br>
<b>Sent:</b> Tuesday, March 19, 2019 2:43 PM<br>
<b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 13 March 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;background:white"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;background:white">As Chair, for the record, this concept was supported by the Work Track that made this recommendation without any dissent prior to the Initial Report. As far
as the comments we got back, ICANN agreed with the recommendation, but expressed concern as to the complexity of implementing this. The only comment that disagreed was from the BC. Neustar, Lemarit, Fairwinds and the BRG supported the recommendation.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would like to highlight this point from Jeff but generalize it: I noticed some remarks in the list and in our meetings mentioning that recommendation X got Y comments against ; the point is that those recommendations have either no or
little dissent to be put out as general agreements, while the ones with some dissent were made as questions in the initial report. So saying that a majority/all commenters were against makes for a bit of dissent, not for a majority, since that point already
had significant support in the respective WTs. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And while we did have some agreeing comments, people are more likely to express themselves in disagreement... so it's not surprising that the overall trend of comments would be against. If those dissents convince the WG to change those
recommendations it will be exactly because the WG has then moved its position, not because the share of the comments. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Rubens<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<hr size="4" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</body>
</html>