<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;">I wanted to share the email exchange below with the ICG. Mohamed, Patrick and I were under the impression that the email we received from Jonathan and Byron was private correspondence, and I responded privately on behalf of the three of us accordingly, but it seems that the original message has been made public <<a href="https://community.icann.org/display/gnsocwgdtstwrdshp/Letter+to+ICG+--+24+September+2014">https://community.icann.org/display/gnsocwgdtstwrdshp/Letter+to+ICG+--+24+September+2014</a>> so we wanted to make sure the ICG was aware of the full exchange. <div><br></div><div>I will follow up with Jonathan and Byron so that we make sure to have clarity in the future about when communications are intended for the full ICG and when not.</div><div><br></div><div>Alissa<br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica';">Alissa Cooper <<a href="mailto:alissa@cooperw.in">alissa@cooperw.in</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica';"><b>Re: CWG to develop an IANA Stewardship Transition proposal on naming related functions and the work of the ICG</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica';">September 25, 2014 at 10:17:35 AM PDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica';">Jonathan Robinson <<a href="mailto:jonathan.robinson@ipracon.com">jonathan.robinson@ipracon.com</a>>, <<a href="mailto:mbashir@mbash.net">mbashir@mbash.net</a>>, 'Patrik Falstrom -' <<a href="mailto:paf@frobbit.se">paf@frobbit.se</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Cc: </b></span><span style="font-family:'Helvetica';">Byron Holland <<a href="mailto:byron.holland@cira.ca">byron.holland@cira.ca</a>>, <<a href="mailto:wolf-ulrich.knoben@t-online.de">wolf-ulrich.knoben@t-online.de</a>>, 'Milton Mueller -' <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>>, 'James Bladel -' <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, 'Keith Drazek -' <<a href="mailto:kdrazek@verisign.com">kdrazek@verisign.com</a>>, 'Jon Nevett -' <<a href="mailto:jon@donuts.co">jon@donuts.co</a>>, <<a href="mailto:mnuduma@yahoo.com">mnuduma@yahoo.com</a>>, Martin Boyle <<a href="mailto:martin.boyle@nominet.org.uk">martin.boyle@nominet.org.uk</a>>, "'Xiaodong Lee:'" <<a href="mailto:xl@cnnic.cn">xl@cnnic.cn</a>>, <<a href="mailto:keith@internetnz.net.nz">keith@internetnz.net.nz</a>><br></span></div><br><div><div style="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; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;"><div><div>Jonathan, Byron,</div><div><br></div><div>Thank you for the update. I realize that there have been extensive efforts put into developing a somewhat novel process on short order for the purposes of developing a transition proposal, and I very much appreciate the effort that you and your colleagues in the other constituencies have put into this.</div><div><br></div><div>Regarding the timeline, we did designate January 15 (and all of the other milestones) as a “target” so as to acknowledge the potential need for some wiggle room on either side to accommodate unforeseen circumstances that may arise in the various communities. With that said, the January 15 target was deliberately chosen with the rest of the consultation and coordination steps in mind, and with a very strong emphasis on completion of the transition by September 30, 2015. As I noted at the first ICG meeting, I think the political likelihood of getting a second chance to transition after that date are extremely slim, and the ICG as a whole seems quite motivated to have the transition completed next year.</div><div><br></div><div>As such, while small delays can probably accommodated, delays on the order of one month or more (e.g., from mid-January to mid-February) will present difficulties for the rest of the coordination process that the ICG has committed to, and could put a timely completion of the full transition at risk. I realize that face-to-face meetings have been a key mode of doing business in the past, but I would urge you to consider alternative methods for completing a transition proposal for names that would not require postponement until ICANN 52 if at all possible. If the processes in the operational communities get too far out of sync, the ICG may need to proceed with its coordination with only a subset of proposals to assemble and finalize. That would be far from an ideal situation.</div><div><br></div><div>In any event, I’m very glad to hear that the CWG is getting started. Feel free to send RFP questions if you have them.</div><div><br></div><div>Thanks,</div><div>Alissa</div></div><div><br></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div>On 9/24/14, 7:00 AM, "Jonathan Robinson" <<a href="mailto:jonathan.robinson@ipracon.com" style="color: purple; text-decoration: underline;">jonathan.robinson@ipracon.com</a>> wrote:</div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border-left-color: rgb(181, 196, 223); border-left-width: 5px; border-left-style: solid; padding: 0px 0px 0px 5px; margin: 0px 0px 0px 5px;"><div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><div lang="EN-GB" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Dear Alissa, Patrik, Mohamed,</span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">We are taking this opportunity to write you, given our previous roles as co-chairs of the of the drafting team that prepared the charter for the Cross Community Working Group (CWG) to develop an IANA Stewardship Transition proposal on naming related functions. We want to update you on the progress we have made and make one important comment on the timelines set out in the IANA Stewardship Transition Coordination Group Request for Proposals (RFP) published on September 8 2014.</span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">We in the naming community have followed the historic IANA transition process very closely. Mindful of the challenging timelines inherent in the process, we have moved very quickly to come together as a naming community. At ICANN 50 in London in June 2014, the GNSO, ccNSO, ALAC and the SSAC came together to establish a drafting team to prepare a charter for what will become the CWG. Through frequent meetings, we were pleased to be able to finalise a charter for the CWG by mid-August 2014. The charter has been approved by the GNSO, ccNSO, ALAC and SSAC, each in accordance with its own rules and procedures, and we are now calling for volunteers as members and observers, again according to each SO and AC’s rules and procedures. In addition, the GAC has been invited to participate in the CWG and is actively considering the invitation. With the establishment of the CWG, we expect to be able to provide a proposal from the naming community.</span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style=""><o:p> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">While we believe that we have made a good start, ensuring the engagement of such a broad community in such an important and overarching exercise is necessarily time consuming. Even though many of the chartering SO/AC’s have yet to complete their procedures for selecting working group members, we have nevertheless decided to move forward and schedule our first CWG meeting right before (as well as a second meeting during) ICANN 51 in Los Angeles. After this initial F2F meeting, we may not have another opportunity to meet face to face until ICANN 52 in February. We would not anticipate that the CWG itself could approve a transition proposal without at least one such face to face meeting and potentially a public consultation of the community. Please also be aware that before a proposal could be formally transmitted to the ICG, it will also be necessary for the chartering SO/AC’s to approve it through their respective processes. <o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Therefore, while we intend to urge that the CWG devote considerable time and energy to developing a proposal, it will be quite challenging, some would say impossible, to meet the January 15, 2015 target deadline for formal proposals set out in the ICG’s RFP. We do hope that shortly upon formation of the CWG we will be able to come back to you with a proposed timetable. It follows that the CWG will not be in a position to review the RFP or request any clarifications by the deadline of 24 September, but hopefully you are willing to accommodate any questions that the CWG may have following its formation.</span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style=""><o:p> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">The CWG’s charter provides for a very open process, including no limitations on observers (regardless of affiliation) at any of our meetings. We have no doubt that the naming community members on the ICG will actively monitor the work of our CWG and provide the ICG with regular updates on our progress. Should you have any questions or require further clarification, we would be pleased hear from you and to respond accordingly. </span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Sincerely,</span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;"> </span><span style=""><o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Jonathan Robinson & Byron Holland<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Co-Chairs<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">Drafting Team of the Charter for a CWG to develop an IANA stewardship transition proposal</span></div></div></div></div></blockquote></span></div></div></blockquote></div><br></div></body></html>