Skip to main content
Resources

Work Stream 2 – Recommendations to Improve Diversity

The objective of the recommendations produced by the Cross-Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) on improving ICANN's diversity is to ensure there is comprehensive representation of the global Internet community, and an extensive range of perspectives in skills and experience, throughout all levels of ICANN. The CCWG-Accountability noted that these recommendations apply to the Board, org, Nominating Committee, ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs), as well as stakeholder groups, constituencies, and Regional At-Large Organizations.

There are three areas of focus: 1) agreement on elements of diversity; 2) measuring and promoting diversity; and 3) ongoing support for assessing and reporting on diversity.

The org and community share ownership in implementing six recommendations included in this topic, with ICANN org supporting the community's discussions and activities. The two remaining recommendations are for org to own and implement.

Rec Description Implementation Status
1.1

SO/AC/Groups should agree that the following seven key elements of diversity should be used as a common starting point for all diversity considerations within ICANN:

* Geographic/Regional Representation

* Language

* Gender

* Age

* Physical Disability

* Diverse skills

* Stakeholder Group or Constituency.

In progress. Targeted completion date: Q2 2023.

1.2

Each SO/AC/Group should identify which elements of diversity are mandated in their charters or ICANN Bylaws and any other elements that are relevant and applicable to each of its levels including leadership (Diversity Criteria) and publish the results of the exercise on their official websites.

In progress. Targeted completion date: Q4 2023.

1.3

Each SO/AC/Group, supported by ICANN staff, should undertake an initial assessment of their diversity for all of their structures including leadership based on their Diversity Criteria and publish the results on their official website.

Not started. Targeted completion date: Q2 2024

1.4

Each SO/AC/Group should use the information from their initial assessment to define and publish on their official website their Diversity Criteria objectives and strategies for achieving these, as well as a timeline for doing so.

Not started. Targeted completion date: Q2 2024

1.5

Each SO/AC/Group, supported by ICANN staff, should undertake a regular update of their diversity assessment against their Diversity Criteria and objectives at all levels including leadership. Ideally this update should be carried out annually but not less than every three years. They should publish the results on their official website and use this information to review and update their objectives, strategies, and timelines.

Not started. Targeted completion date: Q2 2024

1.6

ICANN staff should provide support and tools for the SO/AC/Groups to assist them in assessing their diversity in an appropriate manner. ICANN should also identify staff or community resources that can assist SO/ACs or other components of the community with diversity-related activities and strategies.

In progress. Targeted completion date: Q3 2023.

1.7

ICANN staff should support SO/AC/Groups in developing and publishing a process for dealing with diversity-related complaints and issues.

In progress. Targeted completion date: Q2 2023.

1.8

ICANN staff should support the capture, analysis, and communication of diversity information, seeking external expertise if needed, in the following ways:

1.8.1. Create a Diversity section on the ICANN website.

1.8.2. Gather and maintain all relevant diversity information in one place.

1.8.3. Produce an Annual Diversity Report for ICANN based on all the annual information and provide a global analysis of trends and summarize SO/AC/Groups recommendations for improvement, where appropriate. This should also include some form of reporting on diversity complaints.

1.8.4. Include diversity information derived from the Annual Diversity Report in ICANN's Annual Report.

In progress. Targeted completion date: Q4 2022.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."