<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><div><div>Bret,</div></div></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">Thanks, great question and hopefully the information below is beneficial to the Council’s consideration of the 3 day hold, as well as the discussion around the extended public comment period. Regarding next steps and timing, here is the relevant language from the PDP Manual:</div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><div><i>The Staff Manager is responsible for drafting a summary and analysis of the public comments received on </i><i>the Issue Report and producing a Final Issue Report based upon the comments received. The Staff </i><i>Manager should forward the Final Issue Report, along with any summary and analysis of the public </i><i>comments received, to the Chair of the GNSO Council for consideration for initiation of a PDP.</i></div><div><i><br></i></div><div><i><b>The summary and analysis and the Final Issue Report are expected to be delivered to the Chair of the </b></i><i><b>GNSO Council within 30 days of the closing of the public comment forum, though the Staff Manager </b></i><i><b>may request an extension of that 30-day time for delivery.</b></i></div><div><i><b><br></b></i></div></blockquote><div>Without knowledge of the level of public comment that will be received, it is difficult to estimate how long the summary and analysis and Final Issue Report will take to prepare. However, assuming 30 days, here are the three timelines expanded to include the next GNSO Council meeting, as long as the document and motion deadline is met. I would note, these are are the first, and not only, opportunities for the Council to consider the initiation of a PDP:</div></div><div><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><ul style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><li>Publish 31 August -> 40 Day Public Comment -> Close 10 October -> <b>9 November PC Analysis & Final Report -> 9 November Documents & Motions Deadline -> 19 November GNSO Council Meeting</b></li><li>Publish 3 September -> 40 Day Public Comment -> <span class="">Close 13 October -> <b>12 November <b>PC Analysis & </b>Final Report -> 7 December </b></span><b>Documents & Motions Deadline -> 17 December GNSO Council Meeting</b></li><li>Publish 3 September -> 60 Day (for instance) Public Comment -> Close 2 November -><b> 2 December <b>PC Analysis & </b>Final Report -> </b><span class=""><b>7 December</b> </span><b>Documents & Motions Deadline -> 17 December GNSO Council Meeting</b></li></ul><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">These are all estimates of course, and in the case of the first bullet, dependent on everything executing according to plan to be able to precisely hit the documents & motions deadline. Substantial public comment and substantive changes to the Final Report could ultimately derail these timelines.</div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div><font face="Calibri,sans-serif">Apologies for the lengthy response, but I</font> hope this answers your questions.</div><div><i style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></i></div><div><font face="Calibri,sans-serif">Best,</font></div><div><font face="Calibri,sans-serif">Steve</font></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div></div></div></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Bret Fausett <<a href="mailto:bret@uniregistry.link">bret@uniregistry.link</a>><br><span style="font-weight:bold">Date: </span> Tuesday, August 18, 2015 at 2:22 PM<br><span style="font-weight:bold">To: </span> Steve Chan <<a href="mailto:steve.chan@icann.org">steve.chan@icann.org</a>>, "<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>" <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [council] - Preliminary Issue Report - New gTLD Subsequent Procedures<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thanks Steve. Great news on the progress. </div><div class=""><br class=""></div><div class="">On the timelines, can you remind me what happens after the close of the comment deadline? How do we get from the close of the public comment period to Day 1 of the PDP working group? How many Council meetings/votes between close of comment period
and starting the hard policy work?</div><div class=""><br class=""></div><div class=""> Bret</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 18, 2015, at 1:26 PM, Steve Chan <<a href="mailto:steve.chan@icann.org" class="">steve.chan@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><div class="">Dear Councilors,</div><div class=""><br class=""></div><div class="">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 class=""><li class="">Publish 31 August -> 40 Day Public Comment -> Close 10 October (note that this is a Saturday)</li><li class="">Publish 3 September -> 40 Day Public Comment -> <b class="">Close 13 October</b></li><li class="">Publish 3 September -> 60 Day (for instance) Public Comment -> Close 2 November </li></ul><div class="">Staff is leaning towards waiting the three days and <u class="">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 class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;" class=""><b class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Steven Chan</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif;" class=""><br class="">
Sr. Policy Manager<br class=""><br class=""><b class="">ICANN<br class=""></b>12025 Waterfront Drive, Suite 300</span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Los Angeles, CA 90094-2536<br class=""><a href="mailto:steve.chan@icann.org" title="blocked::mailto:karen.lettner@icann.org" style="color: blue;" class="">steve.chan@icann.org<br class=""></a><br class="">
direct: +1.310.301.3886<br class="">
mobile: +1.310.339.4410</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">tel: +1.310.301.5800<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">fax: +1.310.823.8649</span></div></div></div></div></blockquote></div><br class=""></div></div></span></body></html>