<p dir="ltr">Ah! Okay that's clear now.</p>
<p dir="ltr">Thanks!</p>
<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 21 May 2014 09:13, "Rafik Dammak" <<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><font face="arial, helvetica, sans-serif">Hi Seun,</font><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">there are no call for comments yet, I interpret it as a kind of heads-up of what we should expect. 4 tracks in parallel . which have dependencies, may mean a lot of work and coordination to have consistent outcome.</font></div>
<div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">regarding the update on transition process comments, there are some in the blog post :"<span style="color:rgb(17,17,17);line-height:21.993999481201172px">The next few weeks will be spent reading all of the input, analyzing it and ultimately producing a revised transition process framework before ICANN 50 in June 2014.</span>" . it seems that we have to wait for some time.</font></div>
<div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">Best Regards,</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">Rafik</font></div>
<div><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-05-21 16:48 GMT+09:00 Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Hello Rafik,</p>
<p dir="ltr">Are there general official call for comments for the last 2 tracks? My understanding is that some comments on IANA transition process suggested that those last 2 be addressed by their relevant stakeholder.</p>
<p dir="ltr">I think it will be good to have ICANN provide the final version of the transition process as all the tracks somehow depends on it.</p>
<p dir="ltr">Regards<br>
PS: I don't seem to have seen any update from ICANN on the process in response to comments made. </p>
<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.</p><div><div>
<div class="gmail_quote">On 21 May 2014 02:15, "Rafik Dammak" <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<p>Hi everyone,</p>
<p>below you will find a blog post from Fadi Chehade , the ICANN CEO, describing what he perceives as 4 tracks for the IANA transition, in particular the 2 last and new tracks. we may agree or disagree with this vision since ICANN is an interested party by the outcome of the transition. that is why we commented about the process for the IANA transition and working on commenting the ICANN accountability.</p>
<p>it also means for us 4 tracks to follow closely and comment in due time to represent non-commercial interests. it is a challenge if we add also the comment regarding the ICANN strategy plan and other important ongoing policies to comment e,g New directory service, DNS in developing countries.</p>
<p>it is important to have enough volunteers on those areas and share workload to be effective. I welcome any practical suggestion of how to cope with this flow of issues. I acknowledge that volunteering may need some learning curve, but volunteers will be supported and get help from "veterans" and NCSG officers. the drafting is also a collaborative work who need someone to take the led to initiate it and then bringing other to comments, ask questions and make edits. </p>
<p>Best Regards,</p>
<p>Rafik</p><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">David Olive</b> <span dir="ltr"><<a href="mailto:david.olive@icann.org" target="_blank">david.olive@icann.org</a>></span><br>
Date: 2014-05-21 6:18 GMT+09:00<br>Subject: [Soac-infoalert] Transition from U.S. Government has Four Work Tracks -Blog By Fadi Chehadé<br>To: "<a href="mailto:soac-infoalert@icann.org" target="_blank">soac-infoalert@icann.org</a>" <<a href="mailto:soac-infoalert@icann.org" target="_blank">soac-infoalert@icann.org</a>><br>
<br><br><div dir="auto"><div><br></div><blockquote type="cite"><span><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px"><div style="font-family:Calibri,sans-serif"><br></div><div style="font-family:Calibri,sans-serif">
<div style="font-family:Consolas;font-size:medium"><a href="http://blog.icann.org/" target="_blank">http://blog.icann.org/</a></div><div style="font-family:Consolas;font-size:medium"><a href="http://blog.icann.org/2014/05/transition-from-u-s-government-has-four-work-tracks/" target="_blank">http://blog.icann.org/2014/05/transition-from-u-s-government-has-four-work-tracks/</a></div>
</div><div style="font-size:medium"><br></div><div style="font-size:medium"><p class="MsoNormal"><b><span style="font-family:Arial">Transition from U.S. Government has Four Work Tracks
<u></u><u></u></span></b></p><p class="MsoNormal"><span style="font-family:Arial">By Fadi Chehadé<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">Nine weeks have passed since the U.S. government announced its intention to transition stewardship of the IANA functions to the global community. This landmark announcement requires a measured, thoughtful
approach for how we – the Internet community – will map a route to a successful transition. Together, we must pool our efforts with a goal of producing an acceptable and timely proposal for a smooth transition.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">What is most important is that our transition process is open and inclusive, while maintaining a discipline and focus that will ensure our success within a reasonable timeline. I see our work ahead as divided
into four concurrent tracks, and wanted to update you on where we are on each track.
<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><b><i><span style="font-family:Arial">1. Transition of U.S. government stewardship of IANA functions at ICANN<u></u><u></u></span></i></b></p>
<p style="margin-top:0in;margin-bottom:0.0001pt"><span style="font-size:12pt;font-family:Arial">By the end of Thursday, 8 May, the community submitted
</span><a href="http://mm.icann.org/pipermail/ianatransition/2014/date.html#start" target="_blank"><span style="font-size:12pt;font-family:Arial">more than 1,000 emails and comments</span></a><span style="font-size:12pt;font-family:Arial"> with feedback on the proposed
process framework for the U.S. government stewardship transition process, which ICANN is facilitating. Comments were received online, via social media, emails as well as through two public dialogues at ICANN 49 in Singapore and the NETmundial meeting in Brazil.
These </span><a href="http://mm.icann.org/pipermail/ianatransition/2014/date.html#start" target="_blank"><span style="font-size:12pt;font-family:Arial">comments</span></a><span style="font-size:12pt;font-family:Arial"> will lead to a revised transition process framework.
<u></u><u></u></span></p><p style="margin-top:0in;margin-bottom:0.0001pt"><span style="font-size:12pt;font-family:Arial"> </span></p><p style="margin-top:0in;margin-bottom:0.0001pt"><span style="font-size:12pt;font-family:Arial">The goal of the process is for the global community to produce a transition proposal to the U.S. government. According to the National Telecommunications
and Information Administration, this proposal </span><span style="font-size:12pt;font-family:Arial">must have broad community support and must not replace NTIA with a government-led or inter-governmental solution.</span><span style="font-family:Arial"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">The next few weeks will be spent reading all of the input, analyzing it and ultimately producing a revised transition process framework before ICANN 50 in June 2014.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><b><i><span style="font-family:Arial">2. Strengthen ICANN accountability<u></u><u></u></span></i></b></p><p class="MsoNormal"><span style="font-family:Arial">Two weeks ago we began a </span><a href="http://www.icann.org/en/news/public-comment/enhancing-accountability-06may14-en.htm" target="_blank"><span style="font-family:Arial">community discussion</span></a><span style="font-family:Arial"> on enhancement of ICANN’s accountability through the posting of a background
document and questions for input. This dialogue is open to all. Please provide your
</span><a href="http://www.icann.org/en/news/public-comment/enhancing-accountability-06may14-en.htm" target="_blank"><span style="font-family:Arial">comment</span></a><span><span style="font-family:Arial">s</span></span><span style="font-family:Arial">
until 27 May on how ICANN (the organization) should be accountable to you after the transition of the IANA stewardship. Your thoughts are welcome on how we can strengthen existing accountability mechanisms like the
</span><a href="http://www.icann.org/en/about/agreements/aoc/affirmation-of-commitments-30sep09-en.htm" target="_blank"><span style="font-family:Arial">Affirmation of Commitments</span></a><span style="font-family:Arial">. Additionally, your insights will help us assess ICANN’s
redress mechanisms, and explore new accountability mechanisms where necessary. We expect ICANN’s Supporting Organizations and Advisory Committees to finalize the participants in a new community Working Group that will guide this process, so that work can begin
during ICANN’s 50<sup>th</sup> Public Meeting in London in June.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><b><i><span style="font-family:Arial">3. Maintain security and stability of implementation of the root zone updates<u></u><u></u></span></i></b></p>
<p class="MsoNormal"><span style="font-family:Arial">Currently, the process flow for root zone management involves three roles that are performed by three different entities: NTIA as the Administrator, ICANN as the
</span><a href="http://www.ntia.doc.gov/page/iana-functions-purchase-order" target="_blank"><span style="font-family:Arial">Operator</span></a><span style="font-family:Arial">, and Verisign as the Maintainer. After the transition, the role of NTIA as the Administrator will
be replaced by mechanisms to be determined by you, the global community, to ensure ICANN’s accountability to the community on each request to update the root zone. ICANN will remain in its role as the Operator, and will establish a relationship directly with
the third-party Maintainer.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">As a means to help ensure stability, ICANN’s recommended implementation option is to have Verisign continue its role as the Maintainer. However, we will be working closely with all relevant parties including
the Root Zone Operators to ensure there are contingency options in place to meet our absolute commitment to the stability, security and resiliency of the Domain Name System.<u></u><u></u></span></p><p class="MsoNormal">
<span style="font-family:Arial"> </span></p><p class="MsoNormal"><b><i><span style="font-family:Arial">4. Strengthen bilateral relationships with policy bodies<u></u><u></u></span></i></b></p><p class="MsoNormal"><span style="font-family:Arial">ICANN staff has begun initial work to review and strengthen existing informal and formal commitments between ICANN and the bodies that produce the policies implemented by the IANA department. Let me be crystal
clear – the policies implemented by IANA are produced by the Internet Engineering Task Force (for protocol parameters), the Address Supporting Organization (for IP addresses), the Generic Names Supporting Organization (for generic domain names) and the ccTLDs
and Country-Code Names Supporting Organization (for country-code domain names). We welcome your help in order to strengthen these relationships and the assurances of a clear division between the processes that produce the policies and their implementation.
<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">You can review </span><a href="http://www.icann.org/en/about/agreements" target="_blank"><span style="font-family:Arial">existing commitments</span></a><span style="font-family:Arial"> with policy bodies on the following
page: </span><a href="http://www.icann.org/en/about/agreements" target="_blank"><span style="font-family:Arial">ICANN’s Major Agreements and Related Reports</span></a><span style="font-family:Arial">.
<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">In addition, here are other links to major agreements and related documents:<u></u><u></u></span></p>
<p style="text-autospace:none"><span>·<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><a href="http://www.icann.org/en/about/agreements/cctlds" target="_blank"><span style="font-family:Arial">ccTLDs</span></a><span style="font-family:Arial">.
<u></u><u></u></span></p><p style="text-autospace:none"><span>·<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><span style="font-family:Arial">IAOC / IAB:<u></u><u></u></span></p><p style="margin-left:1in"><span style="font-family:'Courier New'">o<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><a href="http://www.icann.org/en/about/agreements/ietf/ietf-icann-mou-01mar00-en.htm" target="_blank"><span style="font-family:Arial">Original Memorandum of Understanding</span></a><span style="font-family:Arial">, dated 1 March 2000, RFC 2860.<u></u><u></u></span></p>
<p style="margin-left:1in"><span style="font-family:'Courier New'">o<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><a href="http://www.icann.org/en/about/agreements/ietf/ietf-iana-agreement-2014-07mar13-en" target="_blank"><span style="font-family:Arial">Most recent MOU Supplemental Agreement</span></a><span style="font-family:Arial">, effective 7 March 2014.<u></u><u></u></span></p>
<p style="text-autospace:none"><span>·<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><span style="font-family:Arial">Number Resources Organization:<u></u><u></u></span></p><p style="margin-left:1in"><span style="font-family:'Courier New'">o<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><a href="http://archive.icann.org/en/aso/aso-mou-29oct04.htm" target="_blank"><span style="font-family:Arial">Memorandum of Understanding</span></a><span style="font-family:Arial">, dated 21 October 2004.<u></u><u></u></span></p>
<p style="margin-left:1in"><span style="font-family:'Courier New'">o<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><span style="font-family:Arial">Exchange of Letters (</span><a href="http://www.icann.org/en/news/correspondence/akplogan-to-twomey-23mar09-en.pdf" target="_blank"><span style="font-family:Arial">NRO to ICANN-March 2009</span></a><span style="font-family:Arial">;
</span><a href="http://www.icann.org/en/news/correspondence/twomey-to-akplogan-17apr09-en.pdf" target="_blank"><span style="font-family:Arial">ICANN to NRO-April 2009</span></a><span style="font-family:Arial">;
</span><a href="http://www.icann.org/en/news/correspondence/plzak-to-twomey-17dec07-en.pdf" target="_blank"><span style="font-family:Arial">NRO to ICANN-December 2007</span></a><span style="font-family:Arial">;
</span><a href="http://www.icann.org/en/news/correspondence/twomey-to-plzak-19dec07-en.pdf" target="_blank"><span style="font-family:Arial">ICANN to NRO-December 2007</span></a><span style="font-family:Arial">).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal"><span style="font-family:Arial">We have a full plate for the next 15 months. Together, we must carefully manage these four concurrent and inter-related tracks. And while September 2015 is not a deadline, we must organize ourselves on a
clear timeline to succeed. This is critical work – and I am confident that, united, we will get it done.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Arial"> </span></p><p class="MsoNormal" align="center" style="text-align:center">
<span style="font-family:Arial">##<u></u><u></u></span></p></div><div style="font-size:medium"><br></div><div style="font-size:medium"><br></div></div></span>
</blockquote></div><br>_______________________________________________<br>
soac-infoalert mailing list<br>
<a href="mailto:soac-infoalert@icann.org" target="_blank">soac-infoalert@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/soac-infoalert" target="_blank">https://mm.icann.org/mailman/listinfo/soac-infoalert</a><br>
<br></div><br></div>
</blockquote></div>
</div></div></blockquote></div><br></div></div>
</blockquote></div>