6.1. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI working group, to consider a number of actions to make its deliberations more transparent and better understood to the ICANN community. Where appropriate, ICANN should provide the necessary resources to facilitate the implementation of specific activities in this regard. Examples of activities that the GAC could consider to improve transparency and understanding include:
a. Convening “GAC 101” or information sessions for the ICANN community, to provide greater insight into how individual GAC members prepare for ICANN meetings in national capitals, how the GAC agenda and work priorities are established, and how GAC members interact intersessionally and during GAC meetings to arrive at consensus GAC positions that ultimately are forwarded to the ICANN Board as advice;
b. Publishing agendas for GAC meetings, conference calls, etc., on the GAC website seven days in advance of the meetings and publishing meeting minutes on the GAC website within seven days after each meeting or conference call.
c. Updating and improving the GAC website to more accurately describe GAC activities, including intersessional activities, as well as publishing all relevant GAC transcripts, positions and correspondence;
d. Considering whether and how to open GAC conference calls to other stakeholders to observe and participate, as appropriate. This could possibly be accomplished through the participation of liaisons from other ACs and SOs to the GAC, once that mechanism has been agreed upon and implemented;
e. Considering how to structure GAC meetings and work intersessionally so that during the three public ICANN meetings a year the GAC is engaging with the community and not sitting in a room debating itself;
f. Establishing as a routine practice agenda setting calls for the next meeting at the conclusion of the previous meeting;
g. Providing clarity regarding the role of the leadership of the GAC; and,
h. When deliberating on matters affecting particular entities, to the extent reasonable and practical, give those entities the opportunity to present to the GAC as a whole prior to its deliberations.
6.2. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI, to facilitate the GAC formally adopting a policy of open meetings to increase transparency into GAC deliberations and to establish and publish clear criteria for closed sessions.
6.3. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI, to facilitate the GAC developing and publishing rationales for GAC Advice at the time Advice is provided. Such rationales should be recorded in the GAC register. The register should also include a record of how the ICANN Board responded to each 2item of advice.
6.4. The Board, working through the BGRI working group, should develop and document a formal process for notifying and requesting GAC advice (see ATRT1 Recommendation 10).
6.5. The Board should propose and vote on appropriate bylaw changes to formally implement the documented process for Board-GAC bylaws consultation as developed by the BGRI working group as soon as practicable (see ATRT1 Recommendation 11).Increase support and resource commitments of government to the GAC (see ATRT 1 Recommendation 14)
6.6. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI working group, to identify and implement initiatives that can remove barriers for participation, including language barriers, and improve understanding of the ICANN model and access to relevant ICANN information for GAC members. The BGRI working group should consider how the GAC can improve its procedures to ensure more efficient, transparent and inclusive decision-making. The BGRI working group should develop GAC engagement best practices for its members that could include issues such as: conflict of interest; transparency and accountability; adequate domestic resource commitments; routine consultation with local Domain Name System (DNS) stakeholder and interest groups; and an expectation that positions taken within the GAC reflect the fully coordinated domestic government position and are consistent with existing relevant national and international laws.
6.7. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI working group, to regularize senior officials’ meetings by asking the GAC to convene a High Level meeting on a regular basis, preferably at least once every two years. Countries and territories that do not currently have GAC representatives should also be invited and a stock-taking after each High Level meeting should occur.
6.8. ATRT2 recommends that the Board work jointly with the GAC, through the BGRI working group, to work with ICANN’s Global Stakeholder Engagement group (GSE) to develop guidelines for engaging governments, both current and non-GAC members, to ensure coordination and synergy of efforts.
6.9. The Board should instruct the GSE group to develop, with community input, a baseline and set of measurable goals for stakeholder engagement that addresses the following:
a. Relationships with GAC and non-GAC member countries, including the development of a database of contact information for relevant government ministers;
b. Tools to summarize and communicate in a more structured manner government involvement in ICANN, via the GAC, as a way to increase the transparency on how ICANN reacts to GAC advice (e.g. by using information in the GAC advice register).
c. Making ICANN’s work relevant for stakeholders in those parts of the world with limited participation; and,3
d. Develop and execute for each region of the world a plan to ensure that local enterprises and entrepreneurs fully and on equal terms can make use of ICANN’s services including new gTLD’s.
Archived Recommendation #6 Executive Summaries:
- Recommendation 6 - March 2016
- Recommendation 6 - December 2015
- Recommendation 6 - September 2015
- Recommendation 6 - June 2015
- Recommendation 6 - April 2015
- Recommendation 6 - January 2015
- Recommendation 6 - October 2014