Introduction
Rinalia Abdul Rahim, At-Large member from the Asian, Australian and Pacific Islands Regional At-Large Organization (APRALO), composed an initial draft of this Statement [PDF, 256 KB] after discussion of the topic within At-Large and on the Mailing Lists.
On 19 April 2014, this Statement was posted on the At-Large IDN Variant TLDs – LGR Procedure Implementation – Maximal Starting Repertoire Version 1 Workspace.
On 21 April 2014, Olivier Crépin-Leblond, Chair of the ALAC, requested ICANN Policy Staff in support of the ALAC to send a Call for Comments on the Recommendations to all At-Large members via the ALAC-Announce Mailing List.
On 28 April 2014, a version incorporating the comments received was posted on the aforementioned workspace and the Chair requested that Staff open an ALAC ratification vote on the proposed Statement.
On 03 May 2014, Staff confirmed that the online vote resulted in the ALAC endorsing the Statement with 13 votes in favor, 0 votes against, and 0 abstentions. You may review the result independently under: http://www.bigpulse.com/pollresults?code=3866XQfZBMDfsybwkvXNLTdC.
Summary
- We view the lack of response from the Cyrillic, Greek, Georgian, Hebrew, Lao, Latin and Thai communities as of the ICANN 49 meeting in Singapore to be a matter of concern.
- We recommend the ICANN IDN Variant TLD Program Team to: 1) Work together with the ICANN Global Stakeholder Engagement Team to raise awareness; 2) provide a briefing to the GAC, the ccTLD community, and RALOs to seek their support; 3) work with the ICANN Communications Team to simplify key documents related to the Root Zone Project; 4) provide concrete examples of how Generation Panels can be formed; 5) facilitate or enable appropriate facilitation to support the collaboration of language communities; 6) ensure that language communities that share a script are all represented in a script Generation Panel; and 7) leverage on the Internet Governance Forum to widen awareness.
- We commend the Integration Panel for producing a Maximal Starting Repertoire (MSR) in a format that is easy for language communities to understand and use.
- We advise against freezing script segments of the MSR without receiving sufficient input from language communities either via a script Generation Panel or from the script community.
- We request that the Integration Panel provide confirmation to the community that subsequent versions of the MSR may include an expanded set of possible code points based on the review and input received from language communities.
- We believe that a version-release timeline should be published for the MSR and LGR which can be used by language communities to plan their submissions as well as to expect version updates.
- We call on the Integration Panel to ensure that its work does not discriminate against language communities with a smaller number of speakers.