Comment Close Date | Statement Name | Status (Please click "Adopted" to download a copy of the Final Statement) | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
---|---|---|---|---|---|---|---|---|---|---|---|---|
11.01.2013 | At-Large White Paper on Future Challenges Entitled Making ICANN Relevant, Responsive and Respected | No Statement | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Heidi Ullrich heidi.ullrich@icann.org | n/a |
Comment/Reply Periods (*) | Important Information Links | |||
Comment Open: | 20 November 2012 | |||
Comment Close: | ||||
Close Time (UTC): | 23:59 UTC | Public Comment Announcement | ||
Reply Open: | To Submit Your Comments (Forum) | |||
Reply Close: | View Comments Submitted | |||
Close Time (UTC): | 23:59 UTC | Report of Public Comments | ||
Brief Overview | ||||
Originating Organization: | ALAC | |||
Categories/Tags: |
| |||
Purpose (Brief): | The At-Large White Paper on "Making ICANN Relevant, Responsive and Respected" (R3 White Paper) seeks to address the questions that are now being raised about whether the present ecosystem of Internet governance, including ICANN, is able to adapt to recent changes in the ecosystem that have taken place, and more specifically, within the following four areas:
The document suggests a number of recommendations on how the challenges within these areas might be addressed. The purpose of this public comment period is to obtain feedback and collect broader community input into the further development of this White Paper. | |||
Current Status: | Following a request by the ALAC Executive Committee on 14 November 20 12, ICANN Staff has now published the At-Large White Paper on Future Challenges entitled "Making ICANN Relevant, Responsive and Respected" (R3) for public comment. | |||
Next Steps: | The At-Large Future Challenges Working Group will update the At-Large White Paper on Future Challenges entitled "Making ICANN Relevant, Responsive and Respected" (R3) after considering community feedback submitted through this forum. An updated version of the White Paper will then be presented to the ALAC and the broader community during a public meeting at the 46th ICANN Meeting in Beijing. | |||
Staff Contact: | Heidi Ullrich | Email: | Heidi.Ullrich@icann.org | |
Detailed Information | ||||
Section I: Description, Explanation, and Purpose | ||||
The At-Large White Paper entitled "Making ICANN Relevant, Responsive and Respected" (R3 White Paper) identifies four major challenges that ICANN is facing:
A series of recommendations is offered for each of these four challenges with the aim of initiating the significant changesICANN will be required to undertake if it is to adapt to the identified challenges as well as others within the Internet eco-system. Over the next several months, the At-Large Future Challenges Working Group will be seeking input from both within ICANNand the broader Internet community. The next milestone in the development of the R3 White Paper will be a public session during the 46th ICANN Meeting scheduled to be held in Beijing in April 2013. This Public Comment solicitation represents an opportunity for the ICANN community to provide its views on the issues outlined in the R3 White Paper. | ||||
Section II: Background | ||||
The At-Large White Paper entitled "Making ICANN Relevant, Responsive and Respected" (R3 White Paper) was developed by the globally diverse At-Large Future Challenges Working Group through wide consultation with the At-Large community. It was unanimously ratified by the ALAC in September 2012. | ||||
Section III: Document and Resource Links | ||||
At-Large White Paper on Future Challenges entitled Making ICANN Relevant, Responsive and Respected (R3) [PDF, 109 KB] Translations of the At-Large White Paper on Future Challenges entitled Making ICANN Relevant, Responsive and Respected (R3): | ||||
Section IV: Additional Information | ||||
N/A |
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.