<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Em 1 de fev de 2017, à(s) 13:40:000, Emily Barabas <<a href="mailto:emily.barabas@icann.org" class="">emily.barabas@icann.org</a>> escreveu:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><span style="font-size: 11pt;" class="">Dear WT 1 members,<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><span style="font-size: 11pt;" class="">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<span class="Apple-converted-space"> </span><a href="https://www.icann.org/en/system/files/files/program-review-29jan16-en.pdf" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://www.icann.org/en/system/files/files/program-review-29jan16-en.pdf</a>):<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></b></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class="">Systems<span class="Apple-converted-space"> </span></span></b><span style="font-size: 11pt;" class="">(see page 174)<b class=""><o:p class=""></o:p></b></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></b></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><span style="font-size: 11pt;" class="">…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 class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></b></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class="">8.1.a</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>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 class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class="">8.1.b</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>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 class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri;" class=""><b class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></b></div></div></div></blockquote><div><br class=""></div>Note that this is one way of seeing it. The other, which is shared among many technical people working for 2012 applicants, is that the system was made too complex, so it was inevitable that it would either have flaws or require skilled construction and more time to test. For instance, instead of a web interface, the system could accept a simple "tarball" (an archive of some sort, of which .zip is the mostly known although .tar more used at back-end systems) and process it. A web interface could be available to show what the system has received, so applicants could verify integrity and completeness, but it would be an easier interface to build securely. </div><div><br class=""></div><div>So, more time and more skilled artisans are one of doing it; the other is doing it simple. </div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div><div><br class=""></div></body></html>