14,932
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + − *====At-Large engagement in ICANN== + + − *==The future structure and governance of ICANN== + − *New gTLDs including IDN gTLDs+ − *Transparency and accountability of ICANN+ − *security issues within ICANN's mandate.<ref>https://atlarge.icann.org/files/atlarge/correspondence-05mar09-en.pdf</ref>+ + + + + + + + + + + + + + + + + + − 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 working together in February 2009 in advance of the Summit and met twice during the summit to finalize their statements.+ +
→Working Groups
===Working Groups===
===Working Groups===
Five working groups were formed to draft and finalize a Summit Declaration to the [[ICANN Board]]. The five topics were
Five working groups were formed to draft and finalize a Summit Declaration to the [[ICANN Board]].<ref>https://atlarge.icann.org/files/atlarge/correspondence-05mar09-en.pdf</ref> 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 working together in February 2009 in advance of the Summit and met twice during the summit to finalize their statements.
The five topics were:
====At-Large engagement in ICANN====
The general sentiment was that participation was poor and there was much room for improvement.
The general sentiment was that participation was poor and there was much room for improvement.
{| class="wikitable"
! 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 || more professional remote participation systems (telephonic, chat interface, video streaming), especially for vision- and hearing-impaired users. ICANN should provide opportunities for regional groups to meet on the horizontal level to feed back into the international level. PDP will improve by considering 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 help identify the documents to be translated for ICANN
|-
| 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 for timely access; avoid accommodating volunteer ALAC members and representatives from ALSes in remote, low-quality hotels; for regional meetings, all members should receive travel and expense support; amend the Rules and Procedures for Travel Support to comply with the proposals from the 2008 ALAC Statement to the ICANN Board
|}
====The future structure and governance of ICANN====
====New gTLDs including IDN gTLDs====
====Transparency and accountability of ICANN====
====Security issues within ICANN's mandate====
==References==
==ATLAS II==
==ATLAS II==