<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
[ I've modified the distribution & added both new gTLD WG list
& ALAC list - when you reply, you might get a bounce from the
new gTLD list if you're not in the WG but staff will do the magic to
unlock you message ]<br>
<br>
Just a few notes:<br>
- the Preliminary Issues Report is long (147 pages) but needs to be
read thoroughly.<br>
- the draft ALAC Statement addresses only those points which Carlton
and I felt were important to address. If you see anything else in
the Preliminary Issues Report that requires our attention, please
flag it as soon as possible so we can add it.<br>
- I know that some in our community are saying: "no more new gTLDs /
ban on new gTLD rounds", or "no more new gTLDs until we see a
demonstration that the first round has served the public interest".
<br>
Please note that the current issues report says that the default is
that the program *will continue with a next round*. Having spent
time on the gNSO council participating in the discussions, it is
clear that there is a very strong pressure from Contracted Parties
and some parts of the Non-Contracted parties (some of whom might be
interested in being part of the next application round) that *want*
a next round to take place *as soon as possible*. Unless you are
ready to enter a trench war with the GNSO, I would not recommend
that we ask for an outright indefinite ban on new gTLDs -- because
since the working group will be a GNSO working group, we'll all end
up being completely ignored from day 1. Carlton and I have therefore
taken the stance that if there is going to be another round, *all*
the issues identified in the issues report, and other issues we have
pointed out, need to be both studied and resolved. Even that is
going to be a very hard point to defend, but it is absolutely worth
defending - if/when the working group gets under way, please take
part in the WG.<br>
- If the At-Large Community would like next round of new gTLDs
promoting applicants from developing economies, the ALAC might need
to support a next round sooner rather than later.<br>
<br>
Kind regards,<br>
<br>
Olivier<br>
<br>
<div class="moz-cite-prefix">On 23/09/2015 14:07, ICANN At-Large
Staff wrote:<br>
</div>
<blockquote cite="mid:D2281BB3.2D6D8%25ariel.liang@icann.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
Dear All, </div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
<br>
</div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
On behalf of the ALAC, Olivier Crepin-Leblond and Carlton
Samuels have developed the first draft ALAC Statement in
response to the Public Comment on the
<a moz-do-not-send="true"
href="https://community.icann.org/x/zIdYAw">Preliminary
Issue Report on New gTLD Subsequent Procedures</a>. The
draft, as well as pertinent resources for the Public Comment,
can be found in its wiki workspace here:
<a moz-do-not-send="true"
href="https://community.icann.org/x/zIdYAw">https://community.icann.org/x/zIdYAw</a>.
All At-Large members are welcome to comment on this draft. </div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
<br>
</div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
Please take a moment to review this draft and if you have
input, please submit it in the wiki workspace using the
comment function by
<b>30 September 2015</b>. You will need to log in to the wiki
to use the comment function. If you don’t have a login or have
other issue using the wiki, kindly contact <a
moz-do-not-send="true" href="mailto:staff@atlarge.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a></a>. </div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
<br>
</div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
Inputs submitted in this mailing list will be transferred to
the wiki workspace for the penholder(s) to keep track of the
community comments and take them into consideration when
finalizing the draft. </div>
</div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
<br>
</div>
<div style="font-family: calibri, arial, helvetica, sans-serif;
margin-top: 0px; margin-bottom: 0px;">
<div>
<div style="font-size: 16px;"><font
face="Calibri,Arial,Helvetica,sans-serif">
<div style="margin-top: 0px; margin-bottom: 0px;">
<div style="margin-top: 0px; margin-bottom: 0px;">Regards,</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><br>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;">Heidi
Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber,
Nathalie Peregrine and Terri Agnew</div>
<div style="margin-top: 0px; margin-bottom: 0px;">ICANN
Policy Staff in support of ALAC</div>
<div style="margin-top: 0px; margin-bottom: 0px;">E-mail: <a
moz-do-not-send="true"
href="mailto:staff@atlarge.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a></a></div>
<div style="margin-top: 0px; margin-bottom: 0px;">Facebook: <a
moz-do-not-send="true"
href="https://www.facebook.com/icannatlarge"><a class="moz-txt-link-abbreviated" href="http://www.facebook.com/icann">www.facebook.com/icann</a></a><a
moz-do-not-send="true"
href="https://www.facebook.com/icannatlarge">atlarge</a></div>
<div style="margin-top: 0px; margin-bottom: 0px;">Twitter: <a
moz-do-not-send="true"
href="https://twitter.com/ICANNAtLarge">@</a><a
moz-do-not-send="true"
href="https://twitter.com/ICANNAtLarge">ICANNAtLarge</a></div>
</div>
</font></div>
</div>
</div>
<div><br>
</div>
</blockquote>
<br>
</body>
</html>