Historical Resolution Tracking Feature » Board IDN Working Group
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.
Board IDN Working Group
Board approves changing the name of the Board IDN Variants Working Group to the Board IDN Working Group, expands the scope of the Board IDN Working Group to include other IDN-related issues (as reflected in the Charter),
Whereas, the Board IDN Variants Working Group noted that the working group needs to be able to address IDN-related issues that are beyond those limited to variants, and has proposed that the scope of the working group be expanded to include all IDN-related issues.
Whereas, the BGC considered the issues raised by the Board IDN Variants Working Group (BV-WG) and the proposed charter reflecting the expanded scope of the working group and recommended that: (a) the name of the BV-WG be changed to the Board IDN Working Group; (b) the scope of the working group be expanded to include other IDN issues; and (c) the proposed charter be approved.
Resolved (2015.07.28.02), the Board hereby approves changing the name of the Board IDN Variants Working Group to the Board IDN Working Group, expands the scope of the Board IDN Working Group to include other IDN-related issues (as reflected in the Charter), approves the proposed Charter of the Board IDN Working Group, and identifies the following members of the Board IDN Working Group: Rinalia Abdul Rahim, Ram Mohan (Chair), Jonne Soininen, Kuo-Wei Wu, and Suzanne Woolf.
The Board IDN Variants Working Group (BV-WG) was initially created by the Board in December 2010 (see https://www.icann.org/resources/board-material/resolutions-2010-12-10-en#7), and the initial membership was established in March 2011 (See https://www.icann.org/resources/board-material/resolutions-2011-03-18-en...). At that time, the purpose of the BV-WG was to oversee and track the IDN Variant Issues Project. Since that time, it has become clear that there are numerous issues related to IDNs that are beyond those specific to variants and should be addressed by a working group. This has become especially applicable given the continued registrations of new gTLD IDNs. In its recent meetings, the BV-WG has noted the frequency and need to address various IDN-related issues beyond those limited to variants. As a result, the BV-WG is proposing that the scope of this working group be expanded to include other IDN-related issues. Specifically, the BV-WG proposed that the name of the working group be changed to the Board IDN Working Group and provided the following proposed charter language regarding the purpose and scope of the Board IDN Working Group:
To provide oversight on efforts related to work on the planning, design, development and implementation of Internationalized Domain Names (IDNs) in the context of both generic top-level domains (gTLDs) and country code TLDs (ccTLDs), including but not limited to the analysis of feasibility and introduction of IDN TLDs in a manner that ensures the continued security and stability of the Internet.
The working group will also provide oversight on aspects of Universal Acceptance specifically related to IDN TLDs.
The BGC reviewed the proposal and proposed charter language, and considered the importance of having Board involvement in various IDN-related issues in order to capitalize on the technical expertise and varied skill sets of those on the Board. As a result, the BGC recommended that the working group be re-named the Board IDN Working Group, the scope of the working group be expanded to include other IDN issues, and the proposed Charter be accepted.
Adopting the BGC's recommendation has no direct financial impact on ICANN and is likely to positively impact the systemic security, stability and resiliency of the domain name system.
This decision is an Organizational Administrative Function that does not require public comment.