The RIPE Community and the Evolution of the IANA Functions
Leaders of the I* Internet technical coordination organisations met several times and, in line with the Montevideo Statement on the Future of Internet Cooperation, agreed on some common principles for an evolution such as the one announced by the US Government. Regular participants in these meetings, including their affiliated organisations, are noted here.
As an outcome of these discussions, a common position was developed on the following points:
- The roles of all Internet registry policy bodies 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.
- The IETF, IAB, and RIRs are committed to the role of ICANN as the IANA protocol parameter and IP address registry operator.
- 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.
The full text, agreed upon by the I* leaders, is included below.
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).
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.
In the RIPE community, these discussions will take place via the communication and discussion channels already in place, including the RIPE mailing list, the Cooperation Working Group and RIPE Meetings (including the upcoming RIPE 68 Meeting in Warsaw this May). The RIPE NCC will work, as ever, to facilitate these discussions and ensure that their output is effectively channeled into the global process.
RIPE community members are encouraged to share any thoughts, comments or questions on the RIPE mailing list or the RIPE Cooperation Working Group mailing list, and there will be further discussion on this topic at RIPE 68.
Agreed text by the Leaders of I* organisations:
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 Registry Operators, 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.
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 Affirmation of Commitments (AoC) community reviews, including Accountability and Transparency Review Team (ATRT). In addition, ICANN will continue to embrace its aggressive roadmap to truly globalize its structures.
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.
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.
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.
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.
-- end --