Historical Resolution Tracking Feature » 2007-06-29 - Acknowledgement of Policy Progress on IDNs
Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
2007-06-29 - Acknowledgement of Policy Progress on IDNs
Board requests responses from GNSO, ccNSO, ALAC, and GAC on issues concerning IDN ccTLDs.
- Respond to published issues and questions.
- Responsible entity: GNSO, ccNSO, GAC, ALAC
- Due date: 29 October 2007
- Completion date: 29 October 2007
- Recommend a course of action for IDN ccTLDs associated with the ISO 3166-1.
- Responsible entity: GNSO, ccNSO, GAC, ALAC
- Due date: None provided
- Completion date: 25 June 2008
Whereas, the Board expresses its gratitude to the ICANN community, including the GNSO, ccNSO, GAC, and ALAC for their work related to the deployment of IDNs.
Whereas, the ccNSO, GNSO, GAC and ALAC are actively addressing policy aspects related to the introduction of internationalized top-level labels.
Whereas, a joint effort involving the ccNSO and GAC has made considerable progress, publishing a list of issues and questions that need to be addressed in order to move forward with IDN ccTLDs associated with the ISO 3166-1 two-letter codes.
Whereas, the ICANN community is discussing the details involved in using an interim approach to IDN ccTLDs associated with the ISO 3166-1 two-letter codes to meet near-term demands and to gain experience with mechanisms for selection and authorization of such TLDs that can inform a policy development process aimed at creating an overall policy.
Whereas, the ICANN Board remains committed to the development and deployment of IDNs that enable people to use domain names with characters other than a through z and 0 through 9, and at the same time benefit from the promise of a single interoperable Internet.
Resolved (07.56), the ICANN Board respectfully requests that that the ICANN community including the GNSO, ccNSO, GAC, and ALAC provide the Board with responses to the published list of issues and questions that need to be addressed in order to move forward with IDN ccTLDs associated with the ISO 3166-1 two-letter codes in a manner that ensures the continued security and stability of the Internet. The Board requests status reports regarding progress by the conclusion of the ICANN meeting in Los Angeles in October 2007.
Resolved (07.57), the ICANN Board respectfully requests that the ICANN community including the GNSO, ccNSO, GAC, and ALAC continue to work collaboratively, taking the technical limitations and requirements into consideration, to explore both an interim and an overall approach to IDN ccTLDs associated with the ISO 3166-1 two-letter codes and recommend a course of action to the Board in a timely manner.
- All responsible entities responded to published issues and questions:
- GNSO Response: http://sanjuan2007.icann.org/drafts/ccnso-gac-issues-paper-idn-cctld-draft-21Aug07.pdf.
- ccNSO Response: http://ccnso.icann.org/about/minutes/resolutions-idn-from-ccnso-council-02oct07.pdf.
- ALAC Response: http://www.atlarge.icann.org/correspondence/idn-response.htm.
- GAC Response: http://gac.icann.org/system/files/GAC_29_San_Juan.pdf.
- The IDNC Working Group's final report to the Board is available at: http://www.icann.org/en/announcements/announcement-15jul08-en.htm
- http://www.icann.org/en/announcements/announcement-15jul08-en.htmIssues Paper on Selection of IDN ccTLDs associated with the ISO 3166-1 two letter codes: http://ccnso.icann.org/workinggroups/final-draft-issues-idn-cctlds-iso-26jun07.pdf.
- The IDN ccTLD Fast Track Process was launched on 16 November 2009, and information on the process is available at http://www.icann.org/en/topics/idn/fast-track/.
- The resolution does not address funding for the items identified therein.