<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Thank you Kathy for this text. The questions I will be asking the group are:</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<ol>
<li> Are there elements of the Predictability Model that can be used or modifications we can make to the model to handle the issues raised?</li><li>If we do not use the Predictability model, then what do we use? </li></ol>
<div>Although we appreciate comments of opposition and need to consider them, we also need real solutions to the very real issues that have been identified by the community. Much of the community has responded to the comments stating that the existing procedures
contained in the Guidebook as well as the current GNSO processes are not sufficient to handle all of the issues (especially after the launch of the application window). The Board has acknowledged this as well in their comments (eg., that a process is needed
so that it is not the Board resolving every issue in a top-down manner).</div>
<div><br>
</div>
<div>So, please be ready to discuss solutions.</div>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">Jeff Neuman</span></b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black"></span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">Senior Vice President </span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black"></span></b></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">Com Laude | Valideus<br>
</span></b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">1751 Pinnacle Drive
</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">Suite 600, McLean</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">VA 22102, USA</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black"><br>
M: +1.202.549.5079</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">D: +1.703.635.7514</span></p>
<p style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">E: </span>
<u><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#0563C1"><a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a></span></u><span 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 style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#0563C1"></span></u></p>
<img class="EmojiInsert" style="max-width:100%" data-outlook-trace="F:1|T:1" src="cid:fb2d33e2-0c9e-49f4-839f-65d57978997e"><br>
</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> on behalf of Kathy Kleiman <kathy@kathykleiman.com><br>
<b>Sent:</b> Monday, April 29, 2019 10:05 PM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Tuesday, 30 April 2019 at 03:00 UTC</font>
<div> </div>
</div>
<div style="background-color:#FFFFFF">
<p>Hi All,</p>
<p>The meeting coming up in an hour will be discussing the Predictability Framework. In preparation, I would like to share the full text of the NCSG comment on this matter, since I expect we will be discussing it at some length. Having the full text (not long,
approx 500 words) will hopefully provide valuable background as to the nature and basis of our concerns.</p>
<p>Best, Kathy</p>
<p>---------------------<br>
</p>
<p><u>NCSG Comment</u><u><br>
</u></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPS-BoldMT"><font size="3"><b>"2.2.2 The Predictability Framework Proposal is Not Fair, Balanced, or Consistent with our Policy Development Process</b></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">The Predictability Frame is concerning to the NCSG because it gives inordinate and</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">unprecedented power to the Implementation Review Team (IRT) of the Subsequent</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">Procedures Policy Development Process Working Group. The proposal creates a Super-IRT</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">not just to roll-out the details of the implementation — but to judge and rule on all issues that</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPS-BoldMT"><font size="2"><font face="TimesNewRomanPSMT, serif"><font size="3">arise. To quote the Initial Report,
</font></font><font face="TimesNewRomanPS-ItalicMT, cursive"><font size="3"><i>“as part of the Predictability Framework, a Standing</i></font></font></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPS-ItalicMT, cursive"><font size="3"><i>Implementation Review Team (IRS) should be constituted after the publication of the</i></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPS-ItalicMT, cursive"><font size="3"><i>Applicant Guidebook to consider changes in the implementation, execution and/or operations</i></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPS-ItalicMT, cursive"><font size="3"><i>of the new gTLD program after its launch, and the introduction of any further evaluation</i></font></font></p>
<p style="margin-bottom:0in"><font face="TimesNewRomanPS-ItalicMT,
cursive"><font size="3"><i>guidelines not available to applicants when applications were submitted.”</i></font></font></p>
<p style="margin-bottom:0in"><font face="TimesNewRomanPS-BoldMT"><font size="3"><b><br>
</b></font></font></p>
<p style="margin-bottom:0in"><font face="TimesNewRomanPS-BoldMT"><font size="3"><b>"Disproportionate representation in IRTs</b></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">We note that IRTs are mostly small groups, disproportionately represented by registries and</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">registrars — those knowledgeable and concerned about the technicalities of the technical</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">policy we have created at ICANN. Rarely does the NCSG, for example, have the ability or</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">bandwidth to serve on an IRT — and such service should not be needed if the IRT remains to</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">be the technical implementation arm of a community-driven, community-consensus policy</font></font></p>
<p style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">development process.</font></font></p>
<p style="margin-bottom:0in"><br>
</p>
<p style="margin-bottom:0in"><font face="TimesNewRomanPS-BoldMT"><font size="3"><b>"IRT cannot be used as a tool for bypassing GNSO PDPs</b></font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">As highlighted above, such groups are often composed by members of the technical</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">community - or people who are expert in the technical implementation details of the field -</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">and lack a more proportional representation of the ICANN Community. Their job is to</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">execute what the Community as a whole (or a Supporting Organization such as the GNSO)</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">have adopted in time-consuming Policy Development Processes that often take years, and to</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">assess any technical barriers offered to the implementation of such policies. Unfortunately,</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">IRTs have already massively overreached in other areas, and engaged in policy changes and</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">policy interpretation. For instance, the original Rights Protection Mechanisms IRT for the</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">first Applicant Guidebook has been severely criticized in the current Review of All Rights</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">Protections Mechanisms PDP Working Group for its overreach in this area.</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">Once a policy hits a post-launch problem, it is not a matter for any Implementation Review</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">Team (IRT) to resolve, even this Super-IRT, because that would be highly unfair.</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">Implementation Review Teams “implement” — they absolutely don’t create new policies or</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">even interpretations with overwhelmingly policy-oriented interpretations. That’s simply not</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">their mandate, goal, or expertise</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><br>
</p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">"This attempt to create this “third element,” this Predictability Framework, is and will become</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">a policy bypass and overreach mechanism. It is created as such to handle newly-arising issues</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">in the New gTLD Program — and ones, as noted above, likely to involve far-reaching or</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">international policy issues. it is not for the industry to resolve (or likely remove) the issue by</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">seeking to set it aside, or interpreting it away, under the guise of “operations and execution.”</font></font><font face="TimesNewRomanPSMT, serif"><font size="3"><br>
</font></font></p>
<p align="LEFT" style="margin-bottom:0in"><font face="TimesNewRomanPSMT, serif"><font size="3">"For all the reasons above, the
</font></font><font face="TimesNewRomanPS-BoldMT"><font size="3"><b>NCSG strongly rejects the proposal of a Framework and the massive expansion of the scope and breadth of the Subsequent Procedures Implementation Review Team
</b></font></font><font face="TimesNewRomanPSMT, serif"><font size="3">. IRTs should retain their limited mandate and not be given super powers to change policies through process innovation, and especially not in the midst of new rounds of gTLDs."</font></font>
</p>
<div class="x_moz-cite-prefix"><br>
</div>
<div class="x_moz-cite-prefix">-----------------------------------------------------------------------------------------------<br>
</div>
<div class="x_moz-cite-prefix">On 4/26/2019 8:27 PM, Steve Chan wrote:<br>
</div>
<blockquote type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="x_WordSection1">
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="color:black">Dear WG members,</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">Please find below the proposed agenda for the upcoming call on Tuesday, 30<span class="x_apple-converted-space"> </span>April 2019 at 03:00 UTC for 90 minutes:</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">Draft Agenda:</span></p>
<ol start="1" type="1" style="margin-bottom: 0in;margin-top:0in">
<li class="x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: Calibri, sans-serif;color:black; margin-left:0in">
Welcome/Review of the Agenda/Updates to Statements of Interest (SOIs)</li><li class="x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: Calibri, sans-serif;color:black; margin-left:0in">
Review of Summary Documents – (see: <a href="https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing">
https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing</a>)</li><ol start="1" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: Calibri, sans-serif;color:black; margin-left:0in">
2.2.1 Continuing Subsequent Procedures</li><li class="x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: Calibri, sans-serif;color:black; margin-left:0in">
2.2.2 Predictability / 2.2.2.2 Clarity of Application Process</li></ol>
<li class="x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: Calibri, sans-serif;color:black; margin-left:0in">
AOB</li></ol>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">Note, in relation to agenda item 2, WG leadership and staff have tried to prepare summary documents for each topic that seeks to help you review some of the background material, consider a high-level summary of what we believe the
WG is seeking to accomplish for the topic, a high-level summary of public comment received, and finally, a sort of catch all at the end of each section (e.g., follow-up, parking lot, next steps).</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">If you need a dial out or would like to send an apology for this call, please email<span class="x_apple-converted-space"> </span><a href="mailto:gnso-secs@icann.org"><span style="color:#954F72">gnso-secs@icann.org</span></a>. </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="color:black">Best,</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="color:black">Steve</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<b><span style="font-size:10.0pt; font-family:"Arial",sans-serif">Steven Chan</span></b><b><span style="font-size:10.0pt; font-family:"MS Mincho"">
</span></b><b><span style="font-size:10.0pt; font-family:"Arial",sans-serif"></span></b></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Policy Director, GNSO Support</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<b><span style="font-size:10.0pt; font-family:"Arial",sans-serif"> </span></b></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<b><span style="font-size:10.0pt; font-family:"Arial",sans-serif">ICANN</span></b></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">12025 Waterfront Drive, Suite 300</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Los Angeles, CA 90094-2536</span><span style="font-size:10.0pt; font-family:"MS Mincho"">
</span><span style="font-size:10.0pt; font-family:"Arial",sans-serif"></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Mobile: +1.310.339.4410</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Office Telephone: +1.310.301.5800</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Office Fax: +1.310.823.8649</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Find out more about the GNSO by taking our
<a href="https://learn.icann.org/"><span style="color:#0563C1">interactive courses</span></a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span style="color:#0563C1">GNSO Newcomer
pages</span></a>.</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Follow @GNSO on Twitter: <a href="https://twitter.com/ICANN_GNSO"><span style="color:#0563C1">https://twitter.com/ICANN_GNSO</span></a></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif">Follow the GNSO on Facebook: <a href="https://www.facebook.com/icanngnso/"><span style="color:#0563C1">https://www.facebook.com/icanngnso/</span></a></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Arial",sans-serif"><a href="http://gnso.icann.org/en/"><span style="color:#0563C1">http://gnso.icann.org/en/</span></a></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
</p>
</div>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset>
<pre class="x_moz-quote-pre">_______________________________________________
Gnso-newgtld-wg mailing list
<a class="x_moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a>
<a class="x_moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a></pre>
</blockquote>
<div id="x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #D3D4DE">
<tbody>
<tr>
<td style="width:55px; padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img alt="" width="46" height="29" style="width:46px; height:29px" src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"></a></td>
<td style="width:470px; padding-top:12px; color:#41424e; font-size:13px; font-family:Arial,Helvetica,sans-serif; line-height:18px">
Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color:#4453ea">
www.avast.com</a> </td>
</tr>
</tbody>
</table>
<a href="#x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>
</div>
</div>
</div>
<hr>
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the
sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this
email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company
registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30
Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus
USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see
<a href="https://comlaude.com" target="_blank">www.comlaude.com</a>
</body>
</html>