I am looking forward to welcoming you to the ICANN68 Virtual Policy Forum. While we were unable to hold the meeting in Kuala Lumpur, Malaysia, the meeting will be held in the Kuala Lumpur time zone (UTC+8).
I’d like to take this opportunity to thank the Kuala Lumpur host committee for providing support and expertise while we were planning for ICANN68 in Kuala Lumpur. We also appreciated the committee’s understanding when the ICANN Board decided not to proceed with an in-person meeting due to the COVID-19 pandemic.
Kuala Lumpur is a beautiful city and we hope to return to it in the near future! In the meantime, follow me on Twitter (@jia_rong_low), as I will share something fun about Kuala Lumpur each day of the ICANN meeting (22-25 June).
You are in for a treat during ICANN68. Following the success of the ICANN67 Virtual Community Forum, the virtual meeting experience has been improved. Zoom – our remote participation tool – comes with built-in collaboration tools, where multiple participants can share their screens simultaneously and co-annotate for a more interactive meeting. You are encouraged to download the latest Zoom app on your participation device. Further, interpretation services for all UN languages will be available as well! (As a heads-up, an additional device to listen to the interpreted audio is recommended.) More details on remote participation can be found here.
Another tip: bookmark the ICANN meetings page. This is where I go to find all necessary information, including the ICANN68 schedule.
To our Asia Pacific (APAC) community, please join us for our APAC Space session on 23 June, where we will feature a topic with a high interest topic, “The Impact of COVID-19 on APAC.” On 22 June, the Intellectual Property Constituency (IPC) will organize a virtual Open House targeted at the APAC Intellectual Property community. Our APAC technical community members will be sharing their expertise and experience on the deployment of DNS Security Extensions (DNSSEC) at sessions such as Tech Day and the DNSSEC and Security Workshop (both on 22 June).
I look forward to ‘meeting’ you, virtually.
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.”