Jump to content

IANA Functions Stewardship Transition: Difference between revisions

From ICANNWiki
JP (talk | contribs)
No edit summary
JP (talk | contribs)
No edit summary
Line 31: Line 31:


==Initial Steps and Scoping of Work==
==Initial Steps and Scoping of Work==
Following ICANN 49, ICANN published a "Draft Proposal, Based on Initial Community Feedback, of the Principles and Mechanisms and the Process to Develop a Proposal to Transition NTIA's Stewardship of the IANA Functions" for public comment in April 2014.<ref name="draft1">[https://www.icann.org/resources/pages/draft-proposal-2014-04-08-en ICANN.org Archive - Draft Proposal of the Principles, Mechanisms, and Process to Develop a Proposal for the IANA Transition], April 8, 2014</ref> The proposal included a scoping document designed to focus discussion on what was expected of the process.<ref>[https://www.icann.org/en/about/agreements/iana/iana-transition-scoping-08apr14-en.pdf IANA Transition Scoping Document], April 8, 2014 (PDF)</ref>  
Following ICANN 49, ICANN published a "Draft Proposal, Based on Initial Community Feedback, of the Principles and Mechanisms and the Process to Develop a Proposal to Transition NTIA's Stewardship of the IANA Functions" for public comment in April 2014.<ref name="draft1">[https://www.icann.org/resources/pages/draft-proposal-2014-04-08-en ICANN.org Archive - Draft Proposal of the Principles, Mechanisms, and Process to Develop a Proposal for the IANA Transition], April 8, 2014</ref> The proposal included a scoping document designed to focus discussion on what was expected of the process.<ref name="scope">[https://www.icann.org/en/about/agreements/iana/iana-transition-scoping-08apr14-en.pdf IANA Transition Scoping Document], April 8, 2014 (PDF)</ref> In a blog post following the publication of the draft proposal, Fadi Chehade applauded the ICANN community for its hard work and likened the upcoming transition to the removal of training wheels from a bicycle.<ref>[https://www.icann.org/en/blogs/details/training-wheels-off-11-4-2014-en ICANN.org Blog - Training Wheels Off], April 11, 2014</ref> Notably, Chehade singled out that the "U.S. Government, including the NTIA" had approved the scoping document, and that the scope was "consistent with the views of the leaders of various Internet organizations including the Internet Engineering Task Force, the Internet Society and the Regional Internet Registries."
 
===Scope===
In addition to including the NTIA's "must-haves" from its March announcement, the scoping document presented a brief overview of the IANA functions and used that as the basis for defining the scope of the transition planning process:
<blockquote> The Internet Assigned Numbers Authority (IANA) functions are a set of interdependent technical functions that enable the continued efficient operation of the Internet. The IANA functions include: (1) the coordination of the assignment of technical Internet protocol parameters; (2) the processing of change requests to the authoritative root zone file of the DNS and root key signing key (KSK) management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the ARPA and INT top-level domains (TLDs)...<br />The dialogue and resulting proposal are to focus on defining accountability mechanisms that would serve to replace the current stewardship role played by NTIA to ensure ICANN’s performance of the IANA functions based on the agreements and/or policies provided by the respective bodies (IETF, GNSO, RIRs, ASO, ccTLDs, ccNSO).<ref name="scope" /></blockquote>
The scoping document also identified topics that had emerged during the ongoing community engagement process which, though important, were outside the scope of a process focused on developing a proposal for transition of stewardship of the IANA functions:
* Policy development related to the IANA functions;
* ICANN's current role as the IANA functions operator; and
* A range of issues related to the Internet, but not related to the IANA functions, including data privacy, cybersecurity, child protection, IP protection, the management of TLDs, or the review or reform of ICANN.<ref name="scope" />
 
The scoping document was the subject of some debate on the listserv after its publication. Many participants disagreed with the limitations on the scope of the conversation. [[Brenden Kuerbis]] and [[Milton Mueller]] posted an amended version in redline that broadened the scope of discussion, and in particular argued for a continued separation between ICANN and the performance of the IANA functions.<ref>[https://docs.google.com/document/d/1nYQwmfTB52fLwT88RpAyGd3kD69rBLXbnG5zi5IT9yw/edit Google Docs - Transition Proposal Scoping Document], last modified April 10, 2014</ref> When Chehade's "Training Wheels Off" blog post appeared, however, it appeared to some listserv participants that the scoping document was cast in stone.<ref name="ianalistserv" />  


===Draft Proposal: Principles, Mechanisms, and Process===
===Draft Proposal: Principles, Mechanisms, and Process===
Line 43: Line 53:
| Web-based platform<br />Utilize working group methods<br />Organize dialogues<br />Leverage existing information and processes<br />Conduct stress tests<br />Establish a clear and visible timeline<br />Recognize discussion in other fora<br />Make engagement platforms widely accessible<br />Multilingual support<br />Multiple comment & feedback fora<br />
| Web-based platform<br />Utilize working group methods<br />Organize dialogues<br />Leverage existing information and processes<br />Conduct stress tests<br />Establish a clear and visible timeline<br />Recognize discussion in other fora<br />Make engagement platforms widely accessible<br />Multilingual support<br />Multiple comment & feedback fora<br />
|}
|}
Based on the recommendations and feedback received, ICANN proposed a steering group that would be composed of two representatives from each SO and AC, two representatives from "affected parties" IETF, IAB, ISOC, and NRO, a liaison from the ICANN Board, and a secretariat from ICANN staff to act as support to the group.<ref name="draft1" /> The steering group would be convened in time to convene for a first meeting at [[ICANN 50]]. During that meeting, the group would: elect a chair; finalize the group's charter; and establish processes and procedures for development of the transition proposal. Based on the experience of successful working groups, the draft identified three necessary elements of the development process:
Based on the recommendations and feedback received, ICANN proposed a steering group that would be composed of two representatives from each SO and AC, two representatives from "affected parties" [[IETF]], [[IAB]], [[ISOC]], and [[NRO]], a liaison from the ICANN Board, and a secretariat from ICANN staff to act as support to the group.<ref name="draft1" /> The steering group would be convened in time to convene for a first meeting at [[ICANN 50]]. During that meeting, the group would: elect a chair; finalize the group's charter; and establish processes and procedures for development of the transition proposal. Based on the experience of successful working groups, the draft identified three necessary elements of the development process:
* Provide adequate time for affected parties and other interested parties to identify and define necessary elements of the transition proposal, so that the steering group can effectively deliberate on all elements;
* Provide adequate time for affected parties and other interested parties to identify and define necessary elements of the transition proposal, so that the steering group can effectively deliberate on all elements;
* "Appropriate" community outreach and input as the proposal is drafted; and
* "Appropriate" community outreach and input as the proposal is drafted; and

Revision as of 19:21, 22 July 2021

The IANA Functions Stewardship Transition was a multistakeholder policy-making process and community discussion regarding the transition of IANA functions stewardship from the NTIA to the global Internet community. The process and discussion was spearheaded by ICANN and its various stakeholder groups, and was catalyzed by an announcement in March 2014 by NTIA that they would be relinquishing the stewardship to the Internet community.[1]

Background[edit | edit source]

The Internet Assigned Numbers Authority (IANA) was first proposed by Jon Postel while he was in graduate school at UCLA.[2] Postel realized that the ever-growing ARPANET would require a "numbers czar" to manage a canonical list of numbers and addresses to avoid address collisions.[2] He was appointed as the first numbers czar by general agreement. As the global Internet emerged, the "czar" position became formalized as IANA.

ICANN was initially a contractor to the NTIA as a service provider for the IANA functions. With its announcement in 2014, the NTIA confirmed and followed through on the U.S. Government's commitment to an Internet free of governmental (or United Nations) supervision. The first step in that process was for ICANN to convene stakeholders and create a proposal for how the IANA functions will remain secure and unwavering. The announcement outlined a number of principles which the ICANN proposal must meet:

  • Must Support and enhance the multistakeholder model;
  • Must Maintain the security, stability, and resiliency of the Internet DNS;
  • Must Meet the needs and expectation of the global customers and partners of the IANA services; and,
  • Must Maintain the openness of the Internet.

ICANN subsequently published their own press release that applauded NTIA's announcement and called it a recognition of the U.S. government to ICANN's "maturation in becoming an effective multistakeholder organization".[3]

Reactions and Planning at ICANN 49[edit | edit source]

The NTIA announcement came a week before the first sessions at ICANN 49 in Singapore.[4] The announcement was a central topic of the meeting. During the course of the meeting, the IANA Transition Listserv was created.[5]

NCUC Conference on Internet Governance[edit | edit source]

The Noncommercial Users Constituency hosted a conference on March 21 that featured an address from Larry Strickling of the NTIA.[6] The NCUC conference was focused on issues of Internet governance, particularly in the lead-up to the netMundial conference[7] the following month. As Steve Crocker noted in his opening remarks, "[t]here's an awful lot of buzz, of course, about the announcement from NTIA about the transition of their role with respect to the IANA process."[8]

Strickling, in his "keynote assessment" session, was asked to respond to the panels that had come before through the course of the day, and to also provide context and background for the NTIA's decision. He emphasized that the NTIA intended ICANN to lead a collaborative process with all relevant organizations, both within and outside of the ICANN community:

But on the question of the multistakeholder involvement for all this, we've tried to make it very clear from the outset that this is broader than just ICANN. ICANN is the party with whom we contract for the performance of the IANA functions. ICANN obviously, through these meetings and through its activities, has great experience in terms of running multistakeholder processes and, more importantly, iterative multistakeholder processes where people can work together on an issue over a period of time to reach a consensus decision. So we've asked ICANN to convene, but we've made it very clear that this is something that we expect the Internet society, the Internet Engineering Task Force, the Internet Architecture Board, the RIRs, all of the technical community needs to be participating in this, and we expect that will be reflected in the session on Monday and will be reflected in the process as it's designed and carried out throughout all of this.[9]

Other Mentions[edit | edit source]

The Welcome Ceremony and President's Welcome featured the NTIA transition announcement prominently in both Steve Crocker and Fadi Chehade's remarks.[10] Chehade emphasized the seriousness of the task of transitioning the IANA functions to the global internet community, as well as the importance of strengthening ICANN's accountability and transparency.[10] The opening session was followed by a session specifically directed toward the topics of IANA Transition and ICANN accountability.[11] The session featured presentations from ICANN board chair Steve Crocker, as well as Fadi Chehade and others involved in the early coordination efforts for the transition. Initially, it was anticipated that the process would take eighteen months, culminating in the termination of ICANN's contract with NTIA in October 2015.[12] Chehade fielded a number of questions and comments regarding ICANN's role in transition planning.[11] This session represented the launch of the multistakeholder process to establish a plan for transitioning the IANA functions stewardship.[13] The session began with introductory comments from Steve Crocker, and then a short presentation from Brian Cute [14] intended to tee up questions regarding the evolution of ICANN's accountability principles, process, and commitments.[15] As Cute emphasized in his presentation, the session was largely devoted to listening to community input and impressions regarding ICANN's accountability and the three questions around the AoC.[15]

Other sessions that addressed or discussed the NTIA decision included a session presenting reports from the volunteer strategic panels involved in aspects of ICANN's strategic planning process,[16] as well as a plenary session on Internet Governance.[17] There was also much activity within the SO and AC working sessions during the conference around transition planning. At the Public Forum, the first item on the agenda was an overview of that work from SO/AC leadership, as well as a brief description of what the IANA functions actually are. [18]

Initial Steps and Scoping of Work[edit | edit source]

Following ICANN 49, ICANN published a "Draft Proposal, Based on Initial Community Feedback, of the Principles and Mechanisms and the Process to Develop a Proposal to Transition NTIA's Stewardship of the IANA Functions" for public comment in April 2014.[19] The proposal included a scoping document designed to focus discussion on what was expected of the process.[20] In a blog post following the publication of the draft proposal, Fadi Chehade applauded the ICANN community for its hard work and likened the upcoming transition to the removal of training wheels from a bicycle.[21] Notably, Chehade singled out that the "U.S. Government, including the NTIA" had approved the scoping document, and that the scope was "consistent with the views of the leaders of various Internet organizations including the Internet Engineering Task Force, the Internet Society and the Regional Internet Registries."

Scope[edit | edit source]

In addition to including the NTIA's "must-haves" from its March announcement, the scoping document presented a brief overview of the IANA functions and used that as the basis for defining the scope of the transition planning process:

The Internet Assigned Numbers Authority (IANA) functions are a set of interdependent technical functions that enable the continued efficient operation of the Internet. The IANA functions include: (1) the coordination of the assignment of technical Internet protocol parameters; (2) the processing of change requests to the authoritative root zone file of the DNS and root key signing key (KSK) management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the ARPA and INT top-level domains (TLDs)...
The dialogue and resulting proposal are to focus on defining accountability mechanisms that would serve to replace the current stewardship role played by NTIA to ensure ICANN’s performance of the IANA functions based on the agreements and/or policies provided by the respective bodies (IETF, GNSO, RIRs, ASO, ccTLDs, ccNSO).[20]

The scoping document also identified topics that had emerged during the ongoing community engagement process which, though important, were outside the scope of a process focused on developing a proposal for transition of stewardship of the IANA functions:

  • Policy development related to the IANA functions;
  • ICANN's current role as the IANA functions operator; and
  • A range of issues related to the Internet, but not related to the IANA functions, including data privacy, cybersecurity, child protection, IP protection, the management of TLDs, or the review or reform of ICANN.[20]

The scoping document was the subject of some debate on the listserv after its publication. Many participants disagreed with the limitations on the scope of the conversation. Brenden Kuerbis and Milton Mueller posted an amended version in redline that broadened the scope of discussion, and in particular argued for a continued separation between ICANN and the performance of the IANA functions.[22] When Chehade's "Training Wheels Off" blog post appeared, however, it appeared to some listserv participants that the scoping document was cast in stone.[5]

Draft Proposal: Principles, Mechanisms, and Process[edit | edit source]

The draft proposal collected lists of principles and mechanisms proposed by the community during ICANN 49 and via listserv.[19] The report identified ten common themes in each category from the feedback received to date:

Principles Mechanisms
Inclusive
Transparent
Global
Accountable
Multistakeholder
Focused (in scope)
Pragmatic and evidence-based
Open to all voices
Do no harm
Based in consensus
Web-based platform
Utilize working group methods
Organize dialogues
Leverage existing information and processes
Conduct stress tests
Establish a clear and visible timeline
Recognize discussion in other fora
Make engagement platforms widely accessible
Multilingual support
Multiple comment & feedback fora

Based on the recommendations and feedback received, ICANN proposed a steering group that would be composed of two representatives from each SO and AC, two representatives from "affected parties" IETF, IAB, ISOC, and NRO, a liaison from the ICANN Board, and a secretariat from ICANN staff to act as support to the group.[19] The steering group would be convened in time to convene for a first meeting at ICANN 50. During that meeting, the group would: elect a chair; finalize the group's charter; and establish processes and procedures for development of the transition proposal. Based on the experience of successful working groups, the draft identified three necessary elements of the development process:

  • Provide adequate time for affected parties and other interested parties to identify and define necessary elements of the transition proposal, so that the steering group can effectively deliberate on all elements;
  • "Appropriate" community outreach and input as the proposal is drafted; and
  • The finalization of the proposal for submission to the NTIA should be consensus-driven.[19]

The draft also posed specific questions for the community to consider as it provided comments and feedback. The draft again anticipated the process to be complete before the next expiration of the IANA contract between NTIA and ICANN in September 2015[19]

Public comment on the Draft Proposal was extensive.[5]

According to an article authored by Larry Strickling on August 17, 2015, NTIA's Assistant Secretary for Communications and Information and Administrator, the IANA Transition, which was set to begin September 30, 2015 will not be complete until September 30, 2016. The organization believes that while ICANN has made tremendous strides in its transition, it still has more work to accomplish. [23]

ICANN 53 Announcement[edit | edit source]

At the ICANN 53 Welcome Session, June 22 2015, CEO & President, Fadi Chehadé presented his keynote speech which focused on the IANA Transition and its progress. In his opening remarks, Chehadé outlined three important areas of focus: 1. Strengthening ICANN and preparing it for the transition, 2. Fortifying community support, and 3. Reinforcing bonds with ICANN's technical community.[24]

These three goals are integral to the much larger transition process. The President then went on to describe the necessary timeline of activities prior to the transition. Phase One includes Cross-Community and Board preparation of a proposal and adoption of NTIA's requested bylaw amendments. Phase Two, according to NTIA's Larry Strickling, will last anywhere between four to five months, which include a period of review between the United State's government and members of ICANN's community. Strickling would then assess whether the proposal meets the criteria set by the NTIA and has adopted all necessary bylaws. After the NTIA delivers a certification letter to congrees, the governmental branch has 30 legislative days to review the proposal. Once the review of the proposal is complete, the implementation and full transfer of stewardship takes place. [25]

ICANN Community Discussion[edit | edit source]

After the NTIA announcement, discussion began among ICANN's various stakeholders regarding how the stewardship of the IANA functions should be transitioned and to what entity or entities. Various sessions and panels focused on this topic at ICANN 49 - Singapore and continued at ICANN 50 - London. It was also a topic of much discussion in organizations and conferences such as NETmundial, ISOC, IETF, Internet Governance Forum, and the United Nations.

Process Development[edit | edit source]

The NTIA announcement led to an ICANN-spearheaded discussion that began with a "Call for Public Input on the Draft Proposal of the Principles, Mechanisms and Process to Develop a Proposal to Transition NTIA's Stewardship of the IANA Functions" that was posted by ICANN on 8 April 2014. The organization received hundreds of comments, highlighting the need to create a multistakeholder, transparent, and bottom-up process. A process document was published that included next steps and the implementation of a Coordination Group that would lead discussion and process of the IANA transition going forward.[26]

Coordination Group[edit | edit source]

The Coordination Group was formed by the ICANN community via nominations from 13 community groups, totaling 27 individuals. The current coordination group includes:

The first face-to-face meeting of the Coordination Group took place in London from 17-18 July 2014.[27]

Public comment period[edit | edit source]

On December 2nd 2014, ICANN opened the public comment period on the draft transition document produced by the coordination group.[28]

Legal roadblock[edit | edit source]

On the 4th December 2014, a large federal funding bill for over $1 trillion passed the United States House of Representatives to which Republicans had attached a rider defunding any attempt by the NTIA to transfer its functions before October 2015. The global internet community reacted with "a combination of weariness and growing cynicism about the United States and its role in Internet governance."[29]

Videos[edit | edit source]

References[edit | edit source]

  1. NTIA.gov - NTIA Announces Intent to Transition Key Internet Domain Name Functions, March 14, 2014
  2. 2.0 2.1 Internet Society - IANA Timeline
  3. Press Release March 14, 2014
  4. ICANN 49 Archive - Full Schedule, March 21-27, 2014
  5. 5.0 5.1 5.2 ICANN.org Listserv Archive - IANA Transition, 2014-2017
  6. ICANN 49 Archive - NCUC Conference on Internet Governance - the Road to Sao Paolo and Beyond, March 21, 2014
  7. Netmundial.br Archive - Netmundial Conference, April 23-24, 2014
  8. ICANN 49 Archive - NCUC Morning Transcript, March 21, 2014
  9. ICANN 49 Archive - Transcript, NCUC Keynote Assessment, March 21, 2014
  10. 10.0 10.1 ICANN 49 Archive - Transcript, Welcome Ceremony & President's Welcome, March 24, 2014
  11. 11.0 11.1 ICANN 49 Archive - IANA Accountability Transition, March 24, 2014
  12. ICANN 49 Archive - Presentation deck, IANA Accountability Transition, March 24, 2014
  13. ICANN 49 Archive - ICANN Accountability, March 24, 2014
  14. ICANN 49 Archive - Presentation Deck, AoC Accountability, March 24, 2014
  15. 15.0 15.1 ICANN 49 Archive - Transcript, ICANN Accountability & the AoC, March 24, 2014
  16. ICANN 49 Archive - Strategy Panels and the Planning Process, March 24, 2014
  17. ICANN 49 Archive - Update on Internet Governance, March 26, 2014
  18. ICANN 49 Archive - Transcript, Public Forum, March 27, 20174
  19. 19.0 19.1 19.2 19.3 19.4 ICANN.org Archive - Draft Proposal of the Principles, Mechanisms, and Process to Develop a Proposal for the IANA Transition, April 8, 2014
  20. 20.0 20.1 20.2 IANA Transition Scoping Document, April 8, 2014 (PDF)
  21. ICANN.org Blog - Training Wheels Off, April 11, 2014
  22. Google Docs - Transition Proposal Scoping Document, last modified April 10, 2014
  23. [1] An Update on the IANA Transition. Retrieved 19 August 2015.
  24. https://buenosaires53.icann.org/en/schedule/mon-welcome
  25. ICANN President at ICANN 53, retrieved 07 Oct 2015
  26. Process to Develop the Proposal and Next Steps Transition of NTIA's Stewardship of the IANA Functions - ICANN.org; Retrieved 16 July 2014
  27. Coordination Group ICANN.org: Retrieved 16 July 2014
  28. ICANN opens comment period for its move out of US control
  29. Congress defunds IANA transitionRetrieved 15th December 2014.