ICANN Resolutions » 2004-07-23 - Internationalized Domain Names

Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. 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.

2004-07-23 - Internationalized Domain Names

Resolution of the ICANN Board
Internationalized Domain Names

Board directs staff to coordinate reporting on IDN implementation issues and experiences, and directs the establishment of a President's Advisory Committee on IDN.

Meeting Date: 
周五, 23 七月 2004
Resolution Number: 
04.68, 04.69, 04.70, 04.71
Implementation Actions: 
  • Report on IDN experiences.
    • Responsible entity: ICANN staff, registries
    • Due date: None provided
    • Completion date: Ongoing
  • Establish President's Advisory Committee on IDN.
    • Responsible entity: ICANN staff
    • Due date: None provided
    • Completion date: 23 November 2005
Resolution Text: 

Whereas, the ICANN Board recognizes that it is important that the Internet evolve to be more accessible to those who do not use the ASCII character set.

Whereas, the Board notes that the internationalization of the Internet's domain name system must be accomplished through standards that are open, non-proprietary, and fully compatible with the Internet's existing end-to-end model and that preserve globally unique naming in a universally resolvable public name space.

Whereas, the IETF has adopted a four-part protocol suite defining a standard for internationalized domain names in applications that was published as RFCs 3490, 3491, 3492, and 3454.

Whereas, a broad range of registries, experts, and other stakeholders in the ICANN community have been working hard for several years to develop registry-level registration policies, for example RFC 3743.

Whereas, the ICANN Board has had Working Groups investigate facts and identify issues that may arise concerning IDN's and these Committees have reported to the community.

Whereas, the Board reiterates the importance of implementing the technical standards for IDN's in a coordinated manner, that does not destabilize the global, single root, unique identifier system.

Whereas the Board recognises that significant work remains to be undertaken outside of ICANN's scope in order to provide end-to-end availability of IDN's to end-users and that close co-ordination of these efforts is needed.

Whereas, ICANN is committed to the further study of IDNs in the TLD space, and commits to facilitating venues in which IDN can be discussed, and encourages venues to further encourage the implementation of IDNs.

Resolved [04.68] that the ICANN staff report to the Board and community on the implementation status of IDNs and pending issues.

Resolved further [04.69] that the ICANN staff work with registries and other administrators who use IDNs to report back on usability, successes, and other relevant experiences.

Resolved [04.70] to thank the IDN Workshop organizers and participants for their important contributions to the Workshop, and sharing of knowledge on issues surrounding the implementation of IDN.

Resolved [04.71] that the Board instructs the President to establish a President's Advisory Committee on IDN, to provide the Board and ICANN community with advice on issues that relate to IDN policies, in particular issues that impact the implementation of IDN especially at the top level.

Additional Information: