3,197
edits
Changes
Jump to navigation
Jump to search
Line 43:
Line 43: − + Line 60:
Line 60: + + + + + + + +
IANA Functions Stewardship Transition (view source)
Revision as of 20:45, 22 July 2021
, 2 years agono edit summary
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" />
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===
===April 2014 Draft Proposal: Principles, Mechanisms, and Process===
The draft proposal collected lists of principles and mechanisms proposed by the community during ICANN 49 and via listserv.<ref name="draft1" /> The report identified ten common themes in each category from the feedback received to date:
The draft proposal collected lists of principles and mechanisms proposed by the community during ICANN 49 and via listserv.<ref name="draft1" /> The report identified ten common themes in each category from the feedback received to date:
{| class="wikitable"
{| class="wikitable"
Public comment on the Draft Proposal was extensive.<ref name="ianalistserv" />
Public comment on the Draft Proposal was extensive.<ref name="ianalistserv" />
===June 2014: Process and Next Steps===
After evaluating community feedback and input, ICANN released a report on changes to the proposed process, as well as other updates and next steps.<ref name="june14">[https://www.icann.org/resources/pages/process-next-steps-2014-06-06-en ICANN.org - IANA Transition: Process and Next Steps], June 6, 2014</ref> Based on feedback from a variety of constituencies, the composition and name of the proposed steering group changed: the "coordination group" now included 2 ALAC members, 1 ASO member, 4 ccNSO members (comprised of both ccNSO member and non-member ccTLD managers), 3 (non-registry) GNSO members, 2 members from gTLD registries, 2 GAC members, 1 member from the International Chamber of Commerce/Business Action to Support the Information Society, 2 IAB members, 2 IETF members, 2 ISOC members, 2 NRO members, 2 RSSAC members, and 2 SSAC members. The board liaison and staff expert liaison brought the initial total up to 29 people on the coordination group. ICANN 50 was no longer the venue for the first meeting of the group; instead, the action items for SOs, ACs, and other bodies appointing members "encouraged [the communities] to make their final selections by the end of the ICANN 50 meeting," with a hard deadline for submitting names by July 2, 2014. The new first meeting date was tentatively scheduled for July 16-18, 2014.<ref name="june14" />
There were other alterations to the proposed process, including the addition of "diversity" to the list of defining principles, and a provision that in the event there was not full consensus on an issue, dissenting opinions should be documented during the process. There were no alterations to the scope of the development process.<ref name="june14" />
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. <ref>[http://www.ntia.doc.gov/blog/2015/update-iana-transition] An Update on the IANA Transition. Retrieved 19 August 2015.</ref>
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. <ref>[http://www.ntia.doc.gov/blog/2015/update-iana-transition] An Update on the IANA Transition. Retrieved 19 August 2015.</ref>
===Activity and Changes at ICANN 50===
==ICANN 53 Announcement==
==ICANN 53 Announcement==