Skip to main content

ICANN56, the New Meeting Format, and What that Means to You

Next month will see our second public meeting of 2016 - ICANN56 - take place in Helsinki. This is the second meeting under the new meeting strategy, but the approach to the mid-year meeting is different from what we’re used to. 

Why the change?

The community wanted to address the growing pains associated with the success and expansion of ICANN Public Meetings over the years. For example, ICANN55 in Marrakech hosted over 2200 delegates and nearly 400 sessions. The rising demand for more sessions along with the increase in overall attendance has resulted in over-scheduled agendas and reduced opportunities for cross-community interaction. After a considerable amount of research and analysis, the community-led Meeting Strategy Working Group drafted a set of recommendations, which were provided for public comment and ultimately approved by the board. The new meeting strategy was designed to derive the following benefits:

  • Enhance cross-community interaction

  • Increase efficient use of time by each part of the community

  • Increase concentrated time of policy work while reducing session conflict/overlap

  • Increase opportunity for issue-based and/or language-based interactions

  • Reduce meeting length for some groups based upon their focus and interest

  • Continued regional rotation for all meetings

What does this mean for the upcoming ICANN56 in Helsinki?

ICANN56 falls under the Meeting B (Policy Forum) structure. This means it is strictly a four-day meeting with sessions limited to “policy work and outreach,” with the Supporting Organizations and Advisory Committees taking the lead in organizing the program. The guiding principle is that sessions scheduled should be core to current policy development work, and involve working with other constituencies on matters that would benefit from cross-community dialogue. Session requests can only be made through SO/AC leadership.

Under the Meeting B format, ICANN56 will not have an opening ceremony, high-interest topics, public forums, public board meeting or sponsor exhibition area.

ICANN56 will be a first for all of us. Your feedback and input will be important to us as we review and assess the new structure to further enhance the delivery of the Meeting B strategy going forward.

Please feel free to leave questions or comments below and Tanzanica King or I will get back to you. 

Comments

    pitaracoupon  06:38 UTC on 12 August 2016

    your meeting is good and with the Supporting Organizations and Advisory Committees taking the lead in organizing the program. The guiding principle is that sessions scheduled should be core to current policy development work, and involve working with other constituencies on matters that would benefit from cross-community dialogue. Session requests can only be made through.

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."