At-Large Summit

The At-Large Summit (ATLAS) is a gathering of the representatives of individual Internet users participating in ICANN. There have been three ATLASes.

Overview

Goals; Obstacles; Achievements

ATLAS I

ATLAS I was the first-ever gathering of the representatives of individual Internet users participating in ICANN. Organized as part of ICANN 34 in Mexico City, ATLAS I featured two general sessions for all participants as well as thematic sessions and workshops on issues led by At-Large Community members.

Five Working Groups were formed to draft and finalize a Summit Declaration to the ICANN Board. The subjects for the working groups were chosen via a survey of the entire At-Large Community between December 2008 and January 2009. The summit participants were assigned to the working group that they selected as of most interest to them, and then the groups were balanced regionally and according to language needs. All five working groups began collaborating in February 2009 in advance of the summit and met twice during ATLAS I to finalize their statements. The five topics were: 1) at-large engagement, 2) the future of ICANN, 3) New gTLDs including IDNs, 4) security issues within ICANN's mandate, and 4) transparency and accountability. The general sentiment was that 1) participation was poor; 2) the future of ICANN depended on safeguarding against capture, which was defined as unilateral decision-making and favoring vested interests; 3) there were unnecessary barriers to entry for a broad variety of gTLD applicants; 4) DNS security needed to be stricter; and 5) ICANN needed to be more transparent for Internet users who want to participate and needed to balance operator/business interest with ALAC/GAC.

At-Large Engagement

Issue	Recommendations
IDN POLICY	Fund a timely public information campaign in collaboration with ALSes in the next budget ICANN should consult ALSes to reach communities and end-users
GNSO	Cultivate specialists on GNSO issues in At-Large Community
LOCAL LEVEL	A face-to-face At-Large meeting in each region every year to identify and discuss issues Gather community input in advance, using local radio or SMS
ICANN MEETINGS	Professional remote participation systems (telephonic, chat interface, video streaming), especially for vision- and hearing-impaired users Provide opportunities for regional groups to meet on the horizontal level to feed back into the international level PDP must consider regional differences in views comprehensively
GLOBAL OUTREACH	Differentiated approaches to manage and implement ICANN activities ALAC must engage early in SO PDP to reflect end-users ALAC and the Fellowship committee should collaborate to enhance outreach ALSes need support in providing local users’ feedback (information, sensitization, training seminars on ICANN issues on radio, TV)
TRANSLATION	Continue to apply the multilingualism best practices of other international organizations ALSes should be actively involved in translation RALOs should help identify the documents to be translated
TRAVEL SUPPORT	At-Large participants need full travel support to ICANN meetings, including visa costs Start the travel process earlier and local hosts should help with visas Meeting planners should consider affordability as a criterion Deliver per diem remuneration in a timely manner Avoid accommodating volunteer ALAC members and ALS representatives in remote, low-quality hotels All members should receive travel expense support for regional meetings Amend the Rules and Procedures for Travel Support to comply with the 2008 ALAC Statement to the ICANN Board

Transparency and Accountability

Issue	Recommendations
Transparency
Timing of Major Documents	State how staff deals with input from constituencies on documents for the Board Schedule documents and Executive Summaries to allow time for discussion
Finance	Develop and publish a budget for each ICANN entity Define the responsibilities for executing the budgets Periodic public evaluation of budgetary execution
Budget	Create budgetary allocation for expenditure by ALAC and its constituent RALOs Account for expenditures made by ALAC and its constituent members
Accounting for Public Input	Appropriately annotate substantive ICANN documents to indicate the origin of support or dissent for specific proposals
Contractual Compliance and Process	Document the life cycle of compliance procedures, requirements, metrics, follow-up, enforcement, and appeals Make available for public review what is required of the contracting parties Periodically audit and improve goals to help cope with the potentially high volume of complaints
ICANN's Public Service Role	Annually orient one ICANN meeting toward non-commercial, commercial, and individual users Open up the periodic ICANN regional meetings to participants concerned with public interest
Conflicts of Interest	Review and update conflict-of-interest policies as they apply to SOs, ACs, and other bodies
Accountability
Joint Project Agreement	balance operator/business interest and ALAC/GAC
Addressing ALAC Advice	The Board must react formally to advice from ALAC and enter into formal consultations to discuss any disagreements The Board must explain why it rejects ALAC's advice when it does The composition of the Board should represent Civil Society as represented by the At Large Community The ICANN Board should include two voting Directors nominated by the At Large Community

Other Working Group Topics

Issue	Recommendations
Future of ICANN	Accessible open public forums for all meetings # expand and enforce multi-stakeholder model Stakeholder education and explanation on all aspects of ICANN Multiple languages Simplify documents More time for outreach and community feedback Protocol for reporting and investigating (attempted) capture # regular performance reviews, risk analyses, complaint investigations
Barriers to new GTLDs & IDNs	Further categorization Fee schedule based on current, actual cost-recovery Rounds of gTLD applications, with a fixed deadline, subject to the string contention dispute mechanisms ICANN should not engage in any trademark protection and should recognize non-trademark traditional knowledge rights of Indigenous Peoples Entirely abolish objections on Morality and Public Order # At-Large can be the Independent Objector Applicants' legal status shouldn't disqualify them Required technical understanding # parties should choose their Dispute Resolution Service Providers
DNS Security	Study impact of DNSSEC on installed base The root should be signed in a way that provides integrity and is globally accepted.# modify contracts to allow registrants to deploy DNSSEC conveniently Stricter registration process to minimize fraudulent/criminal registrations Implement proposals from 2005 Hijacking report

With every ATLAS, there is an increasing formalization of ideas, recommendations, and procedures, all toward the aim of fostering concrete results. One of the key outcomes of Atlas I was the lesson that the community needs to document, delegate, and follow-up on many tasks along the way to ensure that the ICANN Board, as well as other ICANN entities, including ALAC, acknowledge and explain whether they are implementing the recommendations or not.

ATLAS II

ATLAS II was held in London in conjunction with ICANN 50. The summit brought together representatives from At-Large Structures to debate ICANN policies, share information, and experience an ICANN meeting. The attendees represented Internet end users, and many had never experienced an ICANN meeting before. As with ATLAS I, the goal of the meeting was to reach consensus and draft reports on what the At-Large Community had decided were the five most urgent issues.

The Second At-Large Summit (ATLAS II) took place after the Board approved a special budget for the event. The summit resulted in the ATLAS II Declaration, which the then Chair of the ALAC Olivier Crépin-Leblond sent to the then Chair of the ICANN Board Steve Crocker on August 7, 2014.

The Declaration was the result of contributions of representatives from 150 At-Large Structures from 70 countries who met face to face in London in June 2014.

The Declaration includes 43 recommendations for the ICANN Board, ICANN, and the ALAC, 10 observations for the wider Internet community, and rationales from the five ATLAS II thematic working groups for the recommendations and observations. The thematic groups included:

1. Future of Multi-Stakeholder Models
2. The Globalization of ICANN
3. Global Internet: The User Perspective
4. ICANN Transparency and Accountability
5. At-Large Community Engagement in ICANN

In August 2014, the ATLAS II Implementation Taskforce was established, with members consisting of organizers of the ATLAS II, drafters of the Declaration, and leaders in the At-Large Community. The taskforce led the transformation of each recommendation into concrete actions as carried out by At-Large assignees, who ensured that the concrete action recommendations reached ICANN Staff, the ICANN Board, and/or ALAC.

Last updated on Jul 29, 2019, a thumbnail table of the 43 recommendations, their recipients, assignees, and completion status showed that of the 22 recommendations to the board, 18 had been “completed,” one had been “discarded,” and 3 were still “in progress.” A completed recommendation means it has been transformed into concrete actions and a milestone has been reached. Over 40% of the recommendations to the Board concerned the dual item of IANA Transition & ICANN Accountability. Meanwhile, the recommendations to the ALAC focused on raising the level of involvement and representation of At-Large Community members in ICANN. This overarching goal encompassed the following objectives, most of which have reached a milestone and have been marked as “completed”:

1. simplify and clarify ICANN for Internet users so they can actually be part of the multistakeholder model
2. find new and better ways of incorporating Internet users into the policy development process
3. make more and better use of the people and structures that are already involved in the At-Large Community, through RALO surveys and more frequent and a wider variety of modes of communication within the community
4. periodically assess the multistakeholder model to gauge whether the At-Large Community is represented and their needs met (reduce conflicts between ICANN requirements and national laws; expand the jurisdiction of the Ombudsman, who along with Contractual Compliance, should publish all complaints proceedings.

Finally, the Post ATLAS II Implementation Taskforce generated a list of Lessons Learned

1. one champion for each recommendation
2. the champion can be a chair, subject matter expert, moderator/assistant moderator, reporter/assistant reporter of the thematic group that generates the recommendation. If the champion becomes incapable of fulfilling the duties, then the entire thematic group must complete the tasks.
3. The thematic groups must prepare, reconvene, provide status updates on implementation and feedback, and continue assigning tasks to move the recommendation forward
4. a template for ATLAS recommendations is needed; it should explain the context, to whom it is allocated, and the specifics
5. recommendations should be processed on a yearly basis

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

Internationalized Domain Name

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Policy Development Process

Internet Assigned Numbers Authority

Regional At-Large Organization