<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)">
<!--[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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
line-height:115%;
font-size:10.0pt;
font-family:"Arial",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:10.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal-reply;
color:#1F497D;}
.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="color:#1F497D">Thanks Jeff. It’s very helpful to receive this in advance of the session. Just a few initial observations:<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">1. <b>Costs of Readiness for the Next Round.</b> Para 8.1 reiterates the assumption that the new gTLD program will operate on a cost recovery basis and will be funded from application fees collected. Para 7.4
says ICANN has insufficient staff to implement new policy and prepare to operate the next application round. Much of the rest of the document talks about what ICANN must do to “gear up” to run the program and implement policy changes. However, there is a
“chicken and egg” problem because one cannot “gear up” with sufficient staff when no application fees will have been received. So the topic of funding for “gearing up” will likely come up in the session. Has anyone identified possible sources to fund the
costs associated with “readiness” for the next round?<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">2. <b>Assumption of a Single Application Window to start the next round</b>. Para 2.6 assumes a “single application window” of one to three months. I don’t think this assumption is consistent with Sub Pro PDP
discussions to date. Since the document says it is based on the pre-existing Sub Pro PDP work (See Para. 3.1) , it seems odd that the assumption of one single application window for all types of applications is assumed. As you know, there have been multiple
scenarios put forward re successive windows, including, but not limited to the Neustar proposal, as well as discussion about “priority rounds” depending on gTLD “type”.<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">3. <b>Assumption that in Order to be “Ready”, ICANN should assume it needs to “staff up” for ongoing application rounds</b>. Para 4.1 states that “Operational infrastructure (people, processes, systems) will
be established to support subsequent application rounds for the long-term introduction of new gTLDs, not just a single round.” The WG has debated a number of scenarios in relation to “windows”. It seems the work in relation to “ongoing applications” has
not progressed sufficiently within the WG to support the conclusion that ICANN should gear up staffing and systems to sustain ongoing application rounds. We discussed this in the policy goals related to “Applications in Rounds”. <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">The concern is that until the Board gives final approval to proceed to the next round after reconciling GNSO Advice with GAC, ALAC, and SSAC advice, staffing up of ICANN org could result in a lot of people without
enough work to do. Thus, it may make sense to determine what readiness activities can be conducted without adding permanent staff. Paragraph 7.6 hints at this via a reference to “temporary resources” but that seems to be the “exception” based on this paper.
In this regard, it would be good for the PDP to talk about which functions can be addressed on a “temporary” or “independent contractor” basis.<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">Temporary and independent contractor resources might be the preferred interim step to “readiness” given that policy work and advice to the Board are not complete. Even “temporary resources” will of course still
implicate the question of “funding on a cost-recovery basis.” I know that the budget contains some funds that are not specifically designated. I believe Xavier said this number was $5M or so, some of which is already spoken for. Unfortunately I missed
this morning’s call re Operating Budget due to the conflict with Sub Pro but it would be good if additional info could be developed before the ICANN 65 discussion session.
<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">Anne <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><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>Jeff Neuman<br>
<b>Sent:</b> Monday, June 17, 2019 1:16 PM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> [Gnso-newgtld-wg] FW: ICANN org's preparation toward implementation of a new round of gTLDs<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;line-height:115%;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;line-height:115%;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>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Please find material from ICANN for the Subsequent Procedures PDP Session #3 (13:30 – 15:00 local time) as discussed on the call earlier today. I have not
yet gone through this document, but wanted to forward it on as soon as I got it,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:normal"><b><span lang="EN-GB" style="font-size:9.0pt;color:black">Jeffrey J. Neuman</span></b><span lang="EN-GB" style="font-size:9.0pt;color:black"><br>
Senior Vice President<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:normal"><b><span lang="EN-GB" style="font-size:9.0pt;color:black">Com Laude | Valideus<br>
</span></b><span lang="EN-GB" style="font-size:9.0pt;color:black">1751 Pinnacle Drive , Suite 600<br>
Mclean , VA 22102<br>
UNITED STATES<br>
<br>
T: +1.703.635.7514<br>
M: +1.202.549.5079<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-size:8.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-size:8.0pt">CONFIRMATION OF ORDERS: Please note that we always confirm receipt of orders. To assist us in identifying orders, please use the word ORDER in the subject line of your
email. If you have sent us an order and have not received confirmation on the same working day (PST) it is possible that your order has not been received or has been trapped by our spam filter. In this case, please contact your client manager or
<a href="mailto:admin@comlaude.com">admin@comlaude.com</a> for confirmation that the order has been received and is being processed. Thank you.
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;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" style="line-height:normal"><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"> Cyrus Namazi <<a href="mailto:cyrus.namazi@icann.org">cyrus.namazi@icann.org</a>>
<br>
<b>Sent:</b> Monday, June 17, 2019 1:33 PM<br>
<b>To:</b> Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a>>; Cheryl Langdon-Orr <<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a>><br>
<b>Cc:</b> Trang Nguyen <<a href="mailto:trang.nguyen@icann.org">trang.nguyen@icann.org</a>>; David Olive <<a href="mailto:david.olive@icann.org">david.olive@icann.org</a>>; Steve Chan <<a href="mailto:steve.chan@icann.org">steve.chan@icann.org</a>>; Marika
Konings <<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<b>Subject:</b> ICANN org's preparation toward implementation of a new round of gTLDs<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;line-height:115%">Dear Cheryl and Jeff;</span><span style="font-size:11.0pt;line-height:115%"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt;line-height:150%"><span lang="EN" style="font-size:11.0pt;line-height:150%">We understand that the Subsequent Procedures PDP Working Group expects to publish its final report with its recommendations by December
2019. As you likely know, these recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage.
</span><span style="font-size:11.0pt;line-height:150%"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt;line-height:150%"><span lang="EN" style="font-size:11.0pt;line-height:150%">In the course of our preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental
operationally focused assumptions to help with the preliminary planning and operational readiness of the organization. I have shared these assumptions with the ICANN Board, and am now sharing them with all ICANN constituencies in the briefing document attached.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt;line-height:150%"><span lang="EN" style="font-size:11.0pt;line-height:150%">If the PDP Working Group members are interested in further engagement and providing feedback and perspective on these assumptions please
let me know and we will be happy to arrange a mutually convenient time for a discussion. Ideally, we could leverage the time in Marrakech for a face-to-face meeting.</span><span style="font-size:11.0pt;line-height:150%"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt;line-height:150%"><span lang="EN" style="font-size:11.0pt;line-height:150%">For your information, this information will also be included in the ICANN Community Digest which is planned to be issued later this week.</span><span style="font-size:11.0pt;line-height:150%"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;line-height:115%"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">Sincerely,</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-family:"Verdana",sans-serif;color:black">Cyrus Namazi</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:black">Senior Vice President | Global Domains Division</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:black">Internet Corporation for Assigned Names and Numbers (ICANN)</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#3B3838">801 17th St NW, Suite 400 | Washington, DC 20006 USA</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="FR" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#3B3838"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="FR" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#3B3838">Office +1 202 249 7543 | Mobile +1 408 421 6894
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="FR" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#3B3838">Skype : cnamazi</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#3B3838"><a href="http://www.icann.org">www.icann.org</a></span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN" style="font-size:11.0pt"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span lang="EN" style="font-size:11.0pt"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;line-height:115%"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;line-height:normal">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">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> <o:p></o:p></span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><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.
<br>
</font>
</body>
</html>