ICANN68 Virtual Policy Forum: Schedule Now Available

Today, the ICANN organization published the schedule for the ICANN68 Virtual Policy Forum to be held from 22-25 June 2020. The ICANN community took the lead in organizing the four-day program. The schedule features plenary sessions exploring Domain Name System (DNS) abuse and malicious registrations, DNS and the Internet of Things, and how to advance policy work during the COVID-19 pandemic. Please remember to register for ICANN68.

ICANN68 is the fifth Policy Forum and the second virtual ICANN Public Meeting. It is also the first ICANN Public Meeting to be supported entirely by remote ICANN org teams working from their homes around the world. ICANN68 will take place in the UTC+8 time zone of Kuala Lumpur, Malaysia—the original host city. Later this week, ICANN org will share more details about language interpretation services for ICANN68.

With the goal of ensuring operational security, stability, and resiliency of the Internet, the ICANN community develops policy recommendations through three Supporting Organizations (SOs) and refines them through four Advisory Committees (ACs), all composed of global stakeholders. Policy development at ICANN takes place through open and consultative processes such as teleconferences, Public Comment, and ICANN Public Meetings. The SOs, ACs, Stakeholder Groups, and Constituencies have arranged sessions during ICANN68 to advance priority items while maintaining their regular work schedules. I would like to thank the ICANN community for its continued commitment to collaborative planning for ICANN Public Meetings.

To help participants prepare for the Policy Forum, please register for the upcoming ICANN68 Prep Sessions. The Pre-ICANN68 Policy Report and the GNSO Policy Briefing ICANN68 Edition are available as well. Whether you are a regular participant, an occasional participant, or a newcomer, I encourage you to engage in the ICANN68 Virtual Policy Forum.
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””icann.org”” is not an IDN.”

Source link