<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">My apologies again for not being there, but I support this message<div><br></div><div>Holly<br><div><div>On 26 Aug 2015, at 9:09 am, Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com">ocl@gih.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
<div bgcolor="#FFFFFF" text="#000000">
Dear ALAC members,<br>
<br>
as per the consensus call please find my message to the GNSO Council
mailing list below.<br>
Kind regards,<br>
<br>
Olivier<br>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Re: [council] - Preliminary Issue Report - New gTLD
Subsequent Procedures</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Wed, 26 Aug 2015 00:42:01 +0200</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Olivier MJ Crepin-Leblond <a class="moz-txt-link-rfc2396E" href="mailto:ocl@gih.com"><ocl@gih.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td>Steve Chan <a class="moz-txt-link-rfc2396E" href="mailto:steve.chan@icann.org"><steve.chan@icann.org></a>,
<a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
Dear Councillors,<br>
<br>
this is to let you know that I have brought up the question on
today's ALAC call and with 10 ALAC members present (quorum
achieved) the Chair conducted a <b>consensus call</b> on the
topic.<br>
<br>
Due to the importance of the Topic, the ALAC would prefer a longer
Public Comment that would respect the customary blackout periods
before, during and after an ICANN meeting. <br>
As the topic is of interest to many of ICANN's communities
including end users, the ALAC would welcome being able to discuss
the topic in Dublin - perhaps as a High Interest Community Topic,
as part of the Public Forum or at some point on Constituency Day.<br>
The work process is likely to take years - from the ALAC's
perspective, it would be imprudent to try to rush it through
consultation phases.<br>
<br>
Warm regards,<br>
<br>
Olivier MJ Crépin-Leblond<br>
ALAC Liaison to the GNSO Council<br>
<br>
<div class="moz-cite-prefix">On 18/08/2015 22:26, Steve Chan
wrote:<br>
</div>
<blockquote cite="mid:D1F8E317.1EB1F%25steve.chan@icann.org" type="cite">
<div>Dear Councilors,</div>
<div><br>
</div>
<div>Staff is on track to be able to deliver the Preliminary
Issue Report on New gTLD Subsequent Procedures for public
comment by the end of August, as discussed on the previous
GNSO Council meeting. However, I wanted to note that during
the meeting, the possibility of providing for an extended
public comment period was also discussed, which would keep it
open through the ICANN54 meeting. This topic is expected to be
on the agenda for the next Council meeting, scheduled for 03
September and as such, it may make sense to delay the
publication of the report by approximately 3 days to allow for
discussion during the meeting and a decision to be made, to
avoid confusion from possibly amending the comment close date.
The impact appears to be minimal:</div>
<ul>
<li>Publish 31 August -> 40 Day Public Comment -> Close
10 October (note that this is a Saturday)</li>
<li>Publish 3 September -> 40 Day Public Comment -> <b>Close
13 October</b></li>
<li>Publish 3 September -> 60 Day (for instance) Public
Comment -> Close 2 November </li>
</ul>
<div>Staff is leaning towards waiting the three days and <u>immediately</u>
putting in the request to publish the Preliminary Issue Report
after a decision is made, but wanted to be sure there were no
strong objections to this approach.</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><b><span style="font-size: 10pt;
font-family: Arial, sans-serif;">Steven Chan</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif;"><br>
Sr. Policy Manager<br>
<br>
<b>ICANN<br>
</b>12025 Waterfront Drive, Suite 300</span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family:
Arial, sans-serif;">Los Angeles, CA 90094-2536<br>
<a moz-do-not-send="true" href="mailto:steve.chan@icann.org" title="blocked::mailto:karen.lettner@icann.org" style="color: blue;">steve.chan@icann.org<br>
</a><br>
direct: +1.310.301.3886<br>
mobile: +1.310.339.4410</span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family:
Arial, sans-serif;">tel: +1.310.301.5800<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family:
Arial, sans-serif;">fax: +1.310.823.8649</span></div>
</div>
</blockquote>
<br>
<br>
</div>
<br>
</div>
_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>https://atlarge-lists.icann.org/mailman/listinfo/alac<br><br>At-Large Online: http://www.atlarge.icann.org<br>ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</blockquote></div><br></div></body></html>