<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;">Sorry, but this has not reached the rpd list from my first attempt. Your input is requested.<div><br></div><div>- a.<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';">Adiel Akplogan <<a href="mailto:adiel@afrinic.net">adiel@afrinic.net</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>[afgwg-discuss] Consultation on post NTIA IANA functions oversight mechanism</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';">March 20, 2014 at 22:22:20 PM GMT+4<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';"><a href="mailto:afgwg-discuss@afrinic.net">afgwg-discuss@afrinic.net</a><br></span></div><br><div><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div> [ *** Apologies for cross-posting *** ] </div><div><br></div>Dear colleagues,<br> <br>On Friday 14 March, the United States Government announced that it intends to transition oversight of key Internet functions (including the Internet Assigned Numbers Authority or IANA) to the global multi-stakeholder community. It has asked ICANN to facilitate, in consultation with the global multi-stakeholder community, the development of a proposal for the transition.<br> <br>Leaders of the I* Internet technical coordination organisations (including AFRINIC), met several times and, in line with the <a href="http://www.afrinic.net/en/library/news/958-montevideo-statement-on-the-future-of-internet-cooperation">Montevideo Statement</a> on the Future of Internet Cooperation (October 2013), we agreed on some common principles for an evolution such as the one announced by the US Government. Regular participants in those meetings, including their affiliated organisations, are noted here:<br><a href="http://www.nro.net/news/statement-from-the-i-leaders-coordination-meeting">http://www.nro.net/news/statement-from-the-i-leaders-coordination-meeting</a><br> <br>As an outcome of these discussions, a common position was developed on the following points:<br> <br>- The roles of all Internet registry policy bodies will stay unchanged. These bodies continue to hold policy authority for the protocol parameter, number, and name spaces, including responsibility to ensure the faithful registry implementation according to those policies.<br> <br>- The IETF, IAB, and RIRs are committed to the role of ICANN as the IANA protocol parameter and IP address registry operator.<br> <br>- ICANN reaffirms its commitment to implement all IANA registry functions in accordance with the respective policies. ICANN will also provide affirmations to all stakeholders (including governments) that all Internet registry policy bodies and ICANN itself will continue to use open and transparent processes.<br> <br>The full text, agreed upon by the I* leaders, is included at the end of this email.<br> <br>Separately, ICANN released a timeline that details its expectations of the multi-stakeholder consultation process. More information on these plans will undoubtedly come out of the upcoming ICANN Meeting in Singapore (23-27 March). The timeline document is available here:<br><a href="http://www.icann.org/en/about/agreements/iana/functions-transfer-process-14mar14-en.pdf">http://www.icann.org/en/about/agreements/iana/functions-transfer-process-14mar14-en.pdf</a><br> <br>While this timeline focuses on ICANN meetings and events, it is clear that this process will not take place only in ICANN venues. The five RIR communities are key stakeholders in this process, and it is vital that we discuss these issues both within our regional communities and globally to ensure that our voices are heard and our concerns recognised. The stable, accurate and professional management of the IANA functions, including management of the global IP address pool, is fundamental to the operation of the Internet. It is important that we not lose sight of this fact as management of the IANA evolves to more faithfully reflect the multi-stakeholder nature of the Internet community.<br> <br>AFRINIC urges the African community at all levels to participate to the upcoming discussions on the future of the IANA functions. We all want to engage because we want the discussions to come up with suggestions and mechanisms that ensure an ongoing interoperable stable and yes, secure Internet. These discussions need to take into consideration views from all over the world as the services provided by IANA touch everyone. The Internet itself has become a tool that we cannot live without today and studies demonstrate how embracing ICTs and the Internet can boost economic and social development, thus taking us ever closer to a world where Sustainable Development Goals can be a reality.<br> <br>We encourage the African community to join the discussion we are launching on our Resource Policy Discussion <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> and AFRICANN <<a href="mailto:africann@afrinic.net">africann@afrinic.net</a>> lists and also join us at the next Africa Internet Summit in Djibouti May 25-June 6, 2014 (<a href="http://africainternetsummit.org/">africainternetsummit.org</a>) to hear more on a panel that we are organising: "Resiliency and stability of IANA functions: what accountability mechanisms to put in place?"<br> <br>I look forward to further discussion at AIS14.<br> <br>Best regards,<br> <br>Adiel A. Akplogan<br>CEO AFRINIC<br> <br><div> <div>Agreed text by the Leaders of I* organisations:<br> <br>In order to ensure global acceptance and affirmation of ICANN's role as administrator of the IANA functions, we are now pursuing the transition of USG's stewardship of the IANA functions from the USG to ICANN. The roles of all Internet registry policy bodies (such as the RIRs, IAB, IETF, ASO, ccNSO, ccTLD ROs, and gNSO) stay unchanged. These bodies continue to hold policy authority for the protocol parameter, number, and name spaces, including responsibility to ensure the faithful registry implementation according to those policies.<br> <br>This transition from the USG has been envisaged since the early days of ICANN. It is now feasible due to the growing maturity of ICANN and other organisations in the Internet ecosystem. ICANN's structures and accountability mechanisms continue to evolve and advance guided by the AoC community reviews, including ATRT. In addition, ICANN will continue to embrace its aggressive roadmap to truly globalize its structures.<br> <br>In order to operationalize the transition from USG, ICANN will engage with the Internet community in a bottom-up public consultation process to ensure appropriate accountability mechanisms. In addition, ICANN will work with the names, numbers, and protocol communities to formalize relationships, commitments, and mutual responsibilities.<br> <br>When community stakeholders have input about the policies emanating from the names, numbers, and protocol communities, they would be directed to pursue their interests through the relevant Internet communities (such as the gNSO, ccNSO, ccTLD ROs, ASO, IAB, IETF, or the RIRs) and their mechanisms for consideration and potential redress.<br> <br>The IETF, IAB, and RIRs are committed to open and transparent processes. They also are committed to the role of ICANN as the IANA protocol parameter and IP address registry operator. The accountability mechanisms for ICANN's administration of these core internet functions will provide escalation routes that assure the names, numbers, and protocol communities that if IANA's performance is lacking, those communities can pursue defined processes for improving performance, including pre-agreed independent 3rd party arbitration processes.<br> <br>ICANN reaffirms its commitment to implement all IANA registry functions in accordance with the respective policies. ICANN will also provide affirmations to all stakeholders (including governments) from all Internet registry policy bodies and itself that all of us will use open and transparent processes.<br> <br>-- end --</div></div></div>_______________________________________________<br>afgwg-discuss mailing list<br><a href="mailto:afgwg-discuss@afrinic.net">afgwg-discuss@afrinic.net</a><br>https://lists.afrinic.net/mailman/listinfo.cgi/afgwg-discuss<br></div></blockquote></div><br></div></body></html>