AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
| Comment Close Date | Statement Name | Status (Please click "Adopted" to download a copy of the Final Statement) | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 29.04.2012 | IDN Variant Issues Project – Proposed Project Plan for Next Steps |
...
Adopted | Rinalia Abdul Rahim | 11.04.2012 | 18.04.2012 | 19.04.2012 | 19.04.2012 | 25.04.2012 | 26.04.2012 | 27.04.2012 | Kurt Pritz kurt.pritz@icann.org | AL/ALAC/ST/0412/8 |
Comment/Reply Periods (*) | Important Information Links: |
Comment Open: | 20 February 2012 |
Comment Close: | 18 March 2012 8 April 2012 |
Close Time (UTC): | 23:59 |
Reply Open: | 19 March 2012 9 April 2012 |
Reply Close: | 8 April 2012 29 April 2012 |
Close Time (UTC): | 23:59 |
Brief Overview |
|
Originating Organization: | Stakeholder Relations |
Categories/Tags: | Top-Level Domains |
Purpose (Brief): | To receive community feedback on the proposed project plan [PDF, 211 KB] for next steps of the IDN Variant Issues Project. |
Current Status: | Phase II of IDN Variant Issues Project has been completed with the publication of the final Integrated Issues Report [PDF, 2.15 MB] following the public comment period. Project team has created a project proposed plan for next steps and seeks community feedback on this plan. |
Next Steps: | This project plan will be discussed at the ICANN public meeting in Costa Rica in March 2012. Comments received in this forum as well as community feedback during the Costa Rica meeting will be incorporated into the final project plan. |
Staff Contact: | Kurt Pritz |
Email: | |
Detailed Information |
|
Section I: Description, Explanation, and Purpose | Public Comment: IDN Variant Issues Project -- Proposed Project Plan for Next Steps [PDF, 211 KB] |
Section II: Background | On 20 April 2011, ICANN announced the IDN Variant Issues Project to explore the issues associated with the potential inclusion of IDN variant TLDs in the DNS root zone. This project was initiated in response to a 2010 ICANN Board of Directors resolution. |
Section III: Document and Resource Links |
|
Section IV: Additional Information | None |
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.
...
[Draft] ALAC Response to the VIP Proposed Project Plan for Next Steps
Acknowledgment of VIP Team Achievement
The ALAC congratulates the IDN VIP team upon the successful completion of the case study reports and the final integrated report. We also wish to record our appreciation for the outreach efforts of the VIP Team aimed at enhancing the community’s understanding about the outcome of its work to date as well as the thinking/framework that guided its work and the processes entailed.
Significance of IDNs and Implications on Future Work of the VIP Team
...
The ALAC is pleased with the VIP Team’s interest in engaging the wider Internet community, which the Team expressed during the ICANN meeting Costa Rica in March 2012. In doing so, We request that the VIP Team maintain a high level of transparency and clarify the project basis for engaging consultants vs. community volunteers vs. ICANN staff.
Comments on the Internationalized Domain Names (IDN) Variant Issues Project (VIP) Proposed Project Plan
Approach
The approach taken by the VIP Team is a standardized, universal and comprehensive one, which has merit in that it takes into consideration aspects of fairness and security. The approach hinges crucially upon the expectation that it is possible to develop a comprehensive code-point repertoire and label generation rule-set within a specific time-frame. The VIP Team has been careful to clarify to the ALAC during a Webinar on 11 April 2012 that until the code-point repertoire and label-generation rule-set are complete, the implementation of any IDN Variant would not be considered regardless of the level of community readiness.
The ALAC concern regarding the VIP Team’s approach is as follows:
...
3. The process, timing and criteria for communities to demonstrate their readiness to implement IDN variants are not addressed. This set of information would serve as an invaluable guide for communities regardless of whether they are early entrants or late entrants to IDN Variant implementation.
The ALAC recommends the following:
1. Adopt an inclusive multi-stakeholder bottom-up approach to code-point repertoire development that is consistent with the ICANN IDN Guidelines and relies on the community consensus in identifying and determining code-points by language/script or groups of languages/scripts.
...
3. Clarify the process, timing and criteria for engaging with communities who consider themselves ready to implement IDN Variants. In addition engage the ICANN channels for reaching out to various language communities to raise their awareness of these considerations.
Cost
The ALAC would appreciate an elaboration on the financial basis of the proposed project.
Risk
The ALAC understands and appreciates that security risk considerations are paramount. The introduction of new technological advancement however, requires balancing risk considerations with benefits to be derived. The demand for IDN Variants and the findings of the VIP case study reports indicate that the benefits of implementing IDN Variant TLDs out-weigh the risks.
Way Forward
Given that the technical community, including the IETF and the IAB, has iterated that the issue of IDN Variants cannot be solved with a technical solution based on current DNS standards, the ALAC agrees with the view that, in the immediate term, the implementation of IDN Variant TLDs should be focused on:
...
Please click here to download a copy of the document below in PDF format.
|
