<html 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="Title" content="">
<meta name="Keywords" content="">
<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:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:Calibri;}
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;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:Calibri;
        color:windowtext;}
span.msoIns
        {mso-style-type:export-only;
        mso-style-name:"";
        text-decoration:underline;
        color:teal;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:Calibri;}
@page WordSection1
        {size:595.0pt 842.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear WT 1 members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As discussed on yesterday’s call, the New gTLD Program Implementation Review provides several recommendations that the group may want to consider in developing implementation guidance on Systems and Communications.
The following text is excerpted directly from the report (available at <a href="https://www.icann.org/en/system/files/files/program-review-29jan16-en.pdf">
https://www.icann.org/en/system/files/files/program-review-29jan16-en.pdf</a>): <o:p>
</o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Systems </span></b><span style="font-size:11.0pt">(see page 174)<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">…there are additional considerations from this round that can be used to inform the next round. In particular, the system development process many have benefited from leveraging industry standard best practices
for product development. In this round, there was limited time available between the finalization of system requirements and the launch of the TLD Application System. In future application rounds, the Program timeline should provide additional time for system
development, including the definition of robust system requirements and appropriate testing. In summary:<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">8.1.a</span></b><span style="font-size:11.0pt"> In developing timelines for future application rounds, provide an appropriate amount of time to allow for the use of best practices in system development.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">8.1.b</span></b><span style="font-size:11.0pt"> Explore beta testing programs for systems to allow for lessons learned, to increase effectiveness of such systems, and to provide further transparency, clarity,
and opportunity for preparation to applicants.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Communications </span></b><span style="font-size:11.0pt">(see page 198)<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Although the success of Program Communications during this application round is difficult to assess because “success” was not defined within the Communications Plan, there are lessons learned that should be
taken into consideration for future rounds. In the 2012 application round, the New gTLD microsite was developed to house all New gTLD Program information. To increase accessibility and usability for future rounds, Program information should be consolidated
into a single site with other ICANN information. Another consideration for future rounds is that ICANN’s Global Stakeholder Engagement team is much larger than it was before the 2012 application round, and this team should be leveraged to help promote awareness
of the New gTLD Program within their respective regions/constituencies. In summary:<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">8.4.a</span></b><span style="font-size:11.0pt"> Consolidate all next round program information into a single site and make information as accessible as possible.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">8.4.b </span></b><span style="font-size:11.0pt">Leverage ICANN’s Global Stakeholder Engagement team to promote awareness of the New gTLD Program within their regions/constituencies.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Emily<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:11.0pt">Emily Barabas
</span></b><span style="font-size:11.0pt">| Policy Specialist<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">ICANN</span></b><span style="font-size:11.0pt"> | Internet Corporation for Assigned Names and Numbers<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>