<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;"><div></div><br><div><div>On Feb 2, 2015, at 4:30 PM, Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">It’s a reasonable projection, Alissa. CWG finishing by June is indeed “best case”<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><a name="_MailEndCompose"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></a></div><div style="border-style: none none none solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;"><div><div style="border-style: solid none none; border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><span class="Apple-converted-space"> </span><a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> [<a href="mailto:internal-cg-bounces@icann.org">mailto:internal-cg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Alissa Cooper<br><b>Sent:</b><span class="Apple-converted-space"> </span>Monday, February 2, 2015 3:15 PM<br><b>To:</b><span class="Apple-converted-space"> </span>ICG<br><b>Subject:</b><span class="Apple-converted-space"> </span>[Internal-cg] Revised ICG timeline<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Hi all,<o:p></o:p></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">I’ve taken a first stab at revising the ICG timeline (attached and in Dropbox at <<a href="https://www.dropbox.com/s/99nrslw6czblvio/TimelineGraphic-v6.xlsx?dl=0" style="color: purple; text-decoration: underline;">https://www.dropbox.com/s/99nrslw6czblvio/TimelineGraphic-v6.xlsx?dl=0</a>>). Inspired by the timetable we received from the CWG <<a href="http://mm.icann.org/pipermail/internal-cg/2015-January/002784.html" style="color: purple; text-decoration: underline;">http://mm.icann.org/pipermail/internal-cg/2015-January/002784.html</a>>, I’ve called it “Best Case Timeline.” The portion showing CWG proposal development is aligned with what we received from the CWG, and the steps after that are contingent upon when we received the names proposal from them. Our current timeline graphic is available at <<a href="https://www.icann.org/en/system/files/files/icg-process-timeline-graphic-10sep14-en.xlsx" style="color: purple; text-decoration: underline;">https://www.icann.org/en/system/files/files/icg-process-timeline-graphic-10sep14-en.xlsx</a>>.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Couple of overall comments:<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">(1) The timeline envisions that the bulk of our ICG time between now and June will be spent getting the IETF and RIR proposal components as final as possible in advance of our receipt of the names proposal from the CWG.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">(2) All of the engagement of the operational communities in reaction to our Step I and Step II assessment processes are listed with the “if necessary” caveat. We need to build in time in case we have questions we need to send back to the communities, and we need to give them time to address those questions, but it’s also possible that we will not have questions and therefore the built-in time will not be necessary.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">(3) In our proposal assembly and finalization process, we envisioned running two public comment periods after having assembled a complete proposal. This timeline suggests running a single public comment process instead. Given that the CWG will have run multiple public comment periods on the names piece of the proposal, and the IETF and RIR proposal components will have been quite stable and thoroughly vetted for many months by the time we can run a public comment process on the complete proposal, I think a single public comment process should be sufficient. This will also allow us to complete our work within two ICANN meeting cycles after our receipt of the names proposal.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">(4) I’ve tried to take into account the timing of future ICANN meetings as well as the impact of holiday periods in putting this together.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">(5) The timeline envisions us transmitting the final proposal to the ICANN Board for submission to NTIA in March 2016. This assumes that the current NTIA contract will have been sufficiently extended beyond September 2015. If it does not get extended, of course we will have to re-evaluate not just the timeline but our work on the transition more broadly at that time.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">It would be great to discussion about this going on the mailing list this week. I think we should reserve 90 minutes to discuss at our face-to-face meeting, with another 45 minutes or so of parking lot time in case we want to come back to it after the initial discussion.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Thanks,<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Alissa</div></div></div></div></div></blockquote></div><br></body></html>