<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;}
@font-face
{font-family:"Helvetica Neue";}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Oh, they post independent blogs on the CCWG blog page?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Will someone ask them to post this one:
<a href="http://www.internetgovernance.org/2015/08/29/gac-as-first-among-equals-the-danger-in-the-accountability-plan/">
http://www.internetgovernance.org/2015/08/29/gac-as-first-among-equals-the-danger-in-the-accountability-plan/</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It will be interesting to see their response.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> NCSG-Discuss [mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU]
<b>On Behalf Of </b>Rafik Dammak<br>
<b>Sent:</b> Monday, August 31, 2015 2:19 AM<br>
<b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> [NCSG-Discuss] [Info] Blog: The IANA Transition: The Work Ahead<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">please find below the blog post written by the NCSG member Matt Shears from CDT commenting the IANA contract extension and its impact of community work.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Rafik<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">---------- Forwarded message ----------<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">We’ll post this shortly on the
<a href="https://community.icann.org/display/acctcrosscomm/Blogs" target="_blank">
CCWG’s blog page</a>. Original link: <a href="https://cdt.org/blog/the-iana-transition-the-work-ahead/" target="_blank">https://cdt.org/blog/the-iana-transition-the-work-ahead/</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">On 17 August, Assistant Secretary for Communications and Information Lawrence Strickling <a href="http://www.ntia.doc.gov/blog/2015/update-iana-transition" target="_blank"><span style="color:#3F3F3F">announced</span></a> that
the US government would be extending the IANA contract with ICANN through 30 September 2016. This long anticipated extension reflects the community’s need for additional time to accomplish a number of important tasks, in order to bring about the IANA stewardship
transition. The extension does not mean that the community is not delivering on its commitments, but rather that the process of ensuring appropriate consultation, refining proposals, securing endorsement from the ICANN community, undergoing interagency review,
etc., is going to take more time.<o:p></o:p></span></p>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">The extension is a welcome, practical, and necessary step that provides the community with a realistic timeframe going forward while ensuring the stability
and continuity of the DNS. The extension reflects a “best case” timeline set out by the community in which it suggested that the accountability-related requirements for the transition would only likely be accomplished by July 2016 and that an extension to
September 2016 would be prudent. The work that needs to be accomplished between now and then is considerable, as is shown in <a href="https://www.icann.org/sites/default/files/assets/iana-stewardship-implementation-phases-19aug15-en.pdf" target="_blank"><span style="color:#3F3F3F">this
timeline</span></a>.<o:p></o:p></span></p>
<blockquote style="margin-left:0in;margin-top:.5in;margin-right:0in;margin-bottom:.5in;quotes:“">
<p align="center" style="margin:0in;margin-bottom:.0001pt;text-align:center;mso-line-height-alt:15.25pt;background:white">
<i><span style="font-size:25.5pt;font-family:"Georgia",serif;color:#3F3F3F">The extension is a welcome, practical, and necessary step that provides the community with a realistic timeframe going forward while ensuring the stability and continuity of the DNS.<o:p></o:p></span></i></p>
</blockquote>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">By the time of the ICANN meeting in Dublin in mid-October, the transition and accountability proposals that are currently out for <a href="https://cdt.org/blog/speak-up-on-the-iana-transition-and-icann-accountability/" target="_blank"><span style="color:#3F3F3F">public
comment</span></a> need to be finalized. Any substantive issues raised in the consultations will need to be addressed by the community prior to the Dublin meeting. Assuming that these and other issues can be resolved, the names community will (hopefully) endorse
the accountability proposal at the ICANN meeting and the IANA Stewardship Transition Coordination Group (ICG) will produce the final version of its transition proposal. Once the two proposals are ready, it is expected that the ICANN Board will forward them
to NTIA, at the end of October or early November.<o:p></o:p></span></p>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">While the proposal package – both transition and accountability enhancements – undergoes scrutiny in the interagency and Congressional review processes,
the community cannot afford to rest. The Cross Community Working Group (CCWG) Accountability <a href="https://community.icann.org/download/attachments/53783460/Section%2010_Implementation_FINAL.pdf?version=2&modificationDate=1438541030000&api=v2" target="_blank"><span style="color:#3F3F3F">proposal
section on implementation and timing</span></a> outlines the work that needs to be done and highlights the process that has been initiated for drafting the bylaws that will be required to be in place for the transition. Beyond this, however, there are no specific
implementation plans in place. Given the limited timeframe within which to accomplish the work, a determination needs to be made quickly as to whether the existing transition and accountability working groups will be addressing implementation issues or if
other working groups or mechanisms will need to be established.<o:p></o:p></span></p>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">Work will also have to start addressing those accountability enhancements that do not necessarily have to be in place for the transition, but that are important
to the increased accountability of the ICANN post-transition. These issues – also <a href="https://community.icann.org/download/attachments/53783460/Section%209_Work%20Stream%202_FINAL.pdf?version=2&modificationDate=1438540962000&api=v2" target="_blank"><span style="color:#3F3F3F">outlined
towards the end of the CCWG Accountability proposal</span></a> – include refining operational aspects of the proposals that need to be in place for the transition, looking at government participation in ICANN and jurisdiction, as well as community accountability,
transparency, diversity, and human rights, among others. Issues such as government participation and jurisdiction are complex and politically charged, and will no doubt engender considerable debate. The resulting proposal will also go through an iterative
drafting process as well as rounds of public comment.<o:p></o:p></span></p>
<p style="line-height:20.25pt;background:white"><span style="font-family:"Helvetica Neue";color:#3F3F3F">Throughout the next year the community will need a lot of resolve and stamina. The extension does not mean that there can be a let-up in effort – there
is still much to be accomplished for the transition to occur by 30 September 2016.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>