Status of ICANN org’s Human Rights Impact Assessment Recommendations Implementation

ICANN org has implemented nearly half of all recommendations in the year since publishing its first-ever internal Human Rights Impact Assessment (HRIA). The focus has been on improving relevant processes, practices, and policies that may impact human rights concerns within the areas under review. Building on this progress, ICANN org will implement additional work in conjunction with, and as a part of, ICANN’s ongoing plans to improve organizational processes and procedures. ICANN org affirms its commitment to incorporate this work into the overall culture of ICANN in order to uphold the positive human rights impacts of our work and mitigate negative impacts, wherever possible.

Specific examples of ICANN org’s efforts during this past year include:

Implemented International Organization for Standardization ISO 3100-based framework for managing risks at each ICANN meeting location
Increased awareness about travel security through staff blogs and communications
Enhanced pre-meeting training for staff
Updated Physical Security Program framework to reflect staff and visitor privacy issues
Incorporated questions about human rights to an annual third-party managed ICANN Org Employee Engagement Survey (e.g. questions regarding equal and fair treatment)
Launched a revised Flexible Work Arrangements Policy
Formalized existing practice of allowing staff to enjoy public religious or cultural holidays, even when not based in the country where the official public holiday is recognized
Increased focus on mental health issues with a designated Mental Health month and awareness raising of the various avenues for employees seeking support with regards to health concerns
There is additional work to be done which will be going to the pipeline and prioritized along with other community-driven objectives. About half of the remaining recommendations are in progress, with the rest under consideration. In the meantime, ICANN org will continue to enhance its daily operational activities to best meet international standards and best practices in the spirit of the HRIA recommendations.
Domain Name SystemInternationalized 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”””” is not an IDN.”

Source link