Page History
Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The 2nd At-Large Summit (ATLAS II)
AL-ATLAS-02-DCL-01-01-EN was submitted to the ICANN Board on 26 June 2014. For complete historical information on the development of this Advice, visit the At-Large workspace: Atlas II Declaration and the At-Large website: https://atlarge.icann.org/advice_statements/9735.
| View file | ||||
|---|---|---|---|---|
|
| Recommendation | Description | Current Phase | ||||||
|---|---|---|---|---|---|---|---|---|
| Recommendation 1 | ICANN should continue to support outreach programmes that engage a broader audience, in order to reinforce participation from all stakeholders. |
| ||||||
| Recommendation 2 | ICANN should increase support (budget, staff) to programmes having brought valuable members to the community. |
| ||||||
| Recommendation 3 | ICANN should continue to shape an accountability model reaching not only Board members but all parts of the ICANN community, in order to develop a more transparent and productive environment. |
| ||||||
| Recommendation 4 | ICANN should study the possibility of enhancing and increasing the role of Liaisons between its different Advisory Committees and Supporting Organizations (AC/SOs) to do away with the “silo culture”. |
| ||||||
| Recommendation 5 | ICANN should examine how best to ensure that end-users remain at the heart of the accountability process in all aspects pertaining to the transition of stewardship of the IANA function. |
| ||||||
| Recommendation 6 | ICANN's MSM should serve as the reference in encouraging all participants (individuals or parties) to declare and update existing or potential conflicts-of-interest, each time a vote takes place or consensus is sought. |
| ||||||
| Recommendation 7 | A periodic review of ICANN's MSM should be performed to ensure that the processes and the composition of ICANN's constituent parts adequately address the relevant decision-making requirements in the Corporation. |
| ||||||
| Recommendation 8 | The ALAC has the duty to keep track of action taken on all of the above recommendations. |
| ||||||
| Recommendation 9 | ICANN should open regional offices with a clear strategy, subject to a cost-benefit analysis, focusing on the areas where the access to the Internet is growing, and where such growth is more likely to occur. |
| ||||||
| Recommendation 10 | The next evolution of language services must adopt further extension of live scribing for all meetings and generally extend the current interpretation and translation processes and make translation available in a timely manner. |
| ||||||
| Recommendation 11 | ICANN must implement a range of services to facilitate access according to various criteria (gender; cultural diversity) and user needs (disabilities, etc). |
| ||||||
| Recommendation 12 | In collaboration with At-Large Structures, ICANN should put in place campaigns to raise awareness and extend education programmes across underrepresented regions. |
| ||||||
| Recommendation 13 | ICANN should review the overall balance of stakeholder representation to ensure that appropriate consideration is given to all views, proportionally to their scope and relevance. |
| ||||||
| Recommendation 14 | ICANN should adjust its contractual framework to minimize conflict between its requirements and relevant national laws. |
| ||||||
| Recommendation 15 | ICANN should examine the possibility of modifying its legal structure befitting a truly global organization, and examine appropriate legal and organizational solutions. |
| ||||||
| Recommendation 16 | ICANN needs to improve their direct communications regardless of time zones. |
| ||||||
| Recommendation 17 | ICANN needs to be sensitive to the fact that social media are blocked in certain countries and, in conjunction with technical bodies, promote credible alternatives. |
| ||||||
| Recommendation 18 | Support end-users to take part in policy development. |
| ||||||
| Recommendation 19 | Eliminate barriers to participation and engagement with ICANN processes and practices. |
| ||||||
| Recommendation 20 | Input the user perspective, wherever necessary, to advance accountability, transparency and policy development within ICANN. |
| ||||||
| Recommendation 21 | Encourage public campaigns on using the Internet for education, information, creativity and empowerment. |
| ||||||
| Recommendation 22 | Members of the general public should be able to participate in ICANN on an issue-by-issue basis. Information on the ICANN website should, where practical, be in clear and non-technical language. |
| ||||||
| Recommendation 23 | The roles and jurisdiction of the Ombudsman should be expanded. The ICANN website should provide a clear and simple way for the public to make complaints. |
| ||||||
| Recommendation 24(a) | Both the areas of the (a) Ombudsman and (b) Contractual Compliance should report regularly on the complaints they received, resolved, pending resolution and actions taken to address issues raised by unresolved complaints. |
| ||||||
| Recommendation 24(b) | Both the areas of (a) Ombudsman and (b) Contractual Compliance should report regularly on the complaints they received, resolved, pending resolution and actions taken to address issues raised by unresolved complaints. |
| ||||||
| Recommendation 25 | To enhance ICANN's community effort on building a culture of Transparency and Accountability, as called for in the recommendations of ATRT2, oversight of the Board's decisions now requires an effective mechanism of checks and balances, capable of providing true multi-stakeholder oversight and effective remedies. |
| ||||||
| Recommendation 26 | Current policy management processes within ICANN are insufficient. ICANN must implement a workable Policy Management Process System, available for use across the SO/ACs, in order to: enhance Knowledge Management, improve the effectiveness of all ICANN volunteer communities, improve cross-community policy-specific activity, enhance policy development metrics, facilitate multilingual engagement, create a taxonomy of policy categories, provide policy development history as an aid for newcomers. |
| ||||||
| Recommendation 27 | The Board must implement ATRT2 Recommendation 9.1, regarding Formal Advice from Advisory Committees. |
| ||||||
| Recommendation 28 | The ALAC should work with all RALOs and ALSes to map the current expertise and interests in their membership, to identify Subject Matter Experts and facilitate policy communication. |
| ||||||
| Recommendation 29 | The ALAC should implement an automated system for tracking topics of interest currently being discussed among the various RALOs, and accessible by everyone. |
| ||||||
| Recommendation 30 | For each Public Comment process, SOs and ACs should be adequately resourced to produce impact statements. |
| ||||||
| Recommendation 31 | ICANN and the ALAC should investigate the use of simple tools and methods to facilitate participation in public comments, and the use of crowdsourcing. |
| ||||||
| Recommendation 32 | ICANN should ensure that all acronyms, terminology in its materials are clearly defined in simpler terms. |
| ||||||
| Recommendation 33 | The ALAC should arrange more At-Large Capacity Building Webinars. |
| ||||||
| Recommendation 34 | In collaboration with the global Internet user community, the ALAC shall reiterate the link between the fundamental rights of Internet users, and the Public Interest. |
| ||||||
| Recommendation 35 | The ICANN Board should hold a minimum of one conference call with the At-Large Community in between ICANN Public Meetings. |
| ||||||
| Recommendation 36 | The At-Large Community should envisage conference calls with other ACs and SOs in between ICANN public meetings to improve collaboration and engagement. |
| ||||||
| Recommendation 37 | Additional logistical support from ICANN is needed to improve the At-Large wiki. |
| ||||||
| Recommendation 38 | ICANN should ensure that its Beginner Guides are easily accessible. |
| ||||||
| Recommendation 39 | ICANN should encourage open data best practices that foster re-use of the information by any third party. |
| ||||||
| Recommendation 40 | ICANN should offer a process similar to the Community Regional Outreach Pilot Program (CROPP), but applicable to short lead-time budget requests not related to travel. |
| ||||||
| Recommendation 41 | The ALAC should work with the ICANN Board in seeking additional sources of funding for At-Large activities. |
| ||||||
| Recommendation 42 | ICANN should enable annual face-to-face RALO assemblies, either at ICANN regional offices or in concert with regional events. |
| ||||||
| Recommendation 43 | RALOs should encourage their inactive ALS representatives to comply with ALAC minimum participation requirements. |
|
