<html 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"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-IE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> soac-infoalert-bounces@icann.org [mailto:soac-infoalert-bounces@icann.org] <b>On Behalf Of </b>David Olive<br><b>Sent:</b> 23 September 2015 02:02<br><b>To:</b> soac-infoalert@icann.org<br><b>Subject:</b> [Soac-infoalert] IANA Stewardship Transition: Full Steam Ahead - ICANN<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><br><a href="https://www.icann.org/news/blog/iana-stewardship-transition-full-steam-ahead">https://www.icann.org/news/blog/iana-stewardship-transition-full-steam-ahead</a> <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>Last week the IANA Stewardship Transition Coordination Group (ICG) met in Los Angeles to review and discuss public comments concerning the <a href="https://www.ianacg.org/icg-files/documents/IANA-stewardship-transition-proposal-EN.pdf"><span style='text-decoration:none'>Proposal to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions</span></a> [PDF, 2.07 MB]. Upon review of the comments received, the ICGdecided to continue advancing the proposal as planned, aiming to make <a href="http://t.co/rTV6179hO0"><span style='text-decoration:none'>as much progress as possible</span></a>by the time of ICANN 54, scheduled for <a href="x-apple-data-detectors://2">October 19-22.</a><o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>During its <a href="https://www.ianacg.org/calls-for-input/combined-proposal-public-comment-period/"><span style='text-decoration:none'>public comment period</span></a> that concluded on September 8, the ICGreceived more than 150 comments from a wide variety of stakeholders all over the world. The majority of the comments expressed support for the proposal. In some cases that support was qualified by suggestions, questions, and criticism that the ICG is working hard to synthesize and address as appropriate.<o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'><span style='color:black'>ICG members worked diligently before and during the Los Angeles meeting to assess the comments. The ICG divided the comments into categories (for example, those related to the Post-Transition IANA, the Root ZoneMaintainer, etc.) and for each category the ICG is examining whether the comments have already been addressed in the proposal development process, whether clarifications are needed from the ICG, or whether the ICG will pose questions or request clarifications from the operational communities. That work is ongoing and is expected to be finalized this week. ICG communications to the communities will request responses by mid-October to allow the ICG to prepare in advance of ICANN54.</span><o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>The ICG's decision to adhere to its planned timeline as much as possible without sacrificing quality for speed is notable in light of indications that the work in Work Stream 1 of the Cross-Community Working Group on Enhancing ICANN's Accountability (CCWG) is likely to be delayed. The ICGis closely following the work of the CCWG and expects to have more clarity about the trajectory of the CCWG's work after that group meets at the end of this week.<o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>The ICG's aggressive work schedule will be carried out via <a href="https://www.ianacg.org/calendar/icg-events/"><span style='text-decoration:none'>phone conferences and meetings</span></a> which, as always, will be open to silent observers. The next ICGconference call is scheduled for <a href="https://www.ianacg.org/icg-announces-upcoming-conference-calls-2/"><span style='text-decoration:none'>23 September at 11:00 UTC</span></a>.<o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>Finally, we chairs want to recognize in these busy days the hard work not only done by the communities, but our ICGmembers, our secretariat and ICANNstaff helping to ensure that we can move forward as effectively as we are.<o:p></o:p></p><p style='widows: auto;box-sizing: border-box;margin:1.25rem'>For more information, see <a href="https://www.ianacg.org/"><span style='text-decoration:none'>ianacg.org</span></a>.<o:p></o:p></p><div><p class=MsoNormal><strong>Alissa Cooper, Patrik Fältström, Mohamed El Bashir</strong><o:p></o:p></p></div><div><p class=MsoNormal><strong>ICG chair and vice-chairs</strong><b><o:p></o:p></b></p></div></div><div><p class=MsoNormal><br><br>Sent from my iPhone <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>David A. Olive<o:p></o:p></p></div><div><div><p class=MsoNormal>Vice President, Policy Development Support<br>General Manager, ICANN Regional Headquarters –Istanbul<o:p></o:p></p></div><div><p class=MsoNormal>Hakki Yeten Cad. Selenium Plaza No:10/C K:<a href="tel:10%2034349">10 34349</a> Fulya, Besiktas, Istanbul<o:p></o:p></p></div><div><p class=MsoNormal>Internet Corporation for Assigned Names and Numbers (ICANN)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Direct Line: <a href="tel:+90.212.999.6212">+90.212.999.6212</a> <o:p></o:p></p></div><div><p class=MsoNormal>Mobile: <a href="tel:+%201.%20202.341.3611">+ 1. 202.341.3611</a><o:p></o:p></p></div></div><div><p class=MsoNormal>Mobile: <a href="tel:+90.533.341.6550">+90.533.341.6550</a> <o:p></o:p></p></div><div><p class=MsoNormal>Email: <a href="mailto:david.olive@icann.org">david.olive@icann.org</a><o:p></o:p></p></div><div><p class=MsoNormal><a href="http://www.icann.org/">www.icann.org</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>