Skip to main content

Chairman’s Blog: Previewing the Montevideo Workshop

On a regular basis, both in-between ICANN meetings and at the beginning of each ICANN Meeting, the ICANN Board meets in a workshop format. During these workshops, the Board and ICANN’s management team come together for in-depth consideration of important and timely ICANN issues.

These workshops provide the Board with face-to-face time for discussion and decision-making on matters of interest to the ICANN community and requirements regarding the work of the ICANN organization. The Board generally uses one day for committee and working group meetings and two days as a full group on timely topics and longer-term strategic issues. The Board usually selects 10-12 topics during each Workshop.

From 20-23 September 2017, the ICANN Board of Directors will be meeting in Montevideo for our last intersessional Board workshop of the year. Ahead of that meeting, I want to give you a brief overview of what we expect to be covering and discussing.

Recently, the Board has adopted a five-block structure to help guide how we spend our time at workshops and we will be conducting the upcoming workshop in this manner.

The five blocks for this workshop are:

  1. Oversight of Policy Development & Cross-Community Initiatives
  2. ICANN Org Oversight
  3. Strategic & Forward Thinking
  4. Governance & Fiduciary Responsibilities
  5. Community Engagement & External Relationships

We’re meeting in Montevideo in part to facilitate attendance and interaction with the Latin America and Caribbean Network Information Centre (LACNIC), who will be in town for one of their annual meetings. The extra day associated with this workshop will give us time to interact with the LACNIC Board and the LACNIC community. Two key committee meetings this time are the Organizational Effectiveness Committee (OEC), which will be looking at ongoing At-Large Review and addressing community coordination issues for the Specific Reviews, and the Board Audit Committee, which will review the draft audited financials and hear from the Independent Auditors about their work.

On the Friday, 22 September, our schedule is divided up into three blocks, following the opening and a dialogue with ICANN CEO Göran Marby. During these blocks, we’ll be hosting one public session, the details of which you can find here. The public session will address how the ICANN Board intends to respond to the Governmental Advisory Committee’s (GAC) advice in its Johannesburg Communiqué.

In addition to the public session, which I highly encourage you to join and listen to, the Board will discuss the path to reaching resolution of open issues on name collision. The Board will also start planning for the election of the Board’s leadership positions, as well as slating for the Board’s committees in advance of the Annual Meeting at ICANN60 in Abu Dhabi, where these selections will be made.

The final day of the workshop, the Saturday, 23 September, will start with a webcasted Board meeting, which I hope you’ll be able to join. The remainder of the day will be focused on strategic issues and the road ahead for both the Board and the organization, including conversations about priorities for FY18 and long-term financial planning.

This workshop comes few weeks ahead of the Annual General Meeting. For the last several years we have made a practice of inviting incoming Board members to join us even before they are formally seated. I am pleased that León Sanchez, Matthew Shears, Avri Doria and Sarah Deutsch will all be able to join us. This facilitates smooth transition and helps the new members come up to speed quickly.

As many of you are aware, this is my last year as Chairman of the ICANN Board, with my term ending at the beginning of November. I look forward to sharing my personal reflections with the Board during this workshop. Personally, I’m also looking forward to enjoying some delicious Uruguayan asado. We’ll plan to update you in the days following the Board workshop to share key takeaways and updates from the sessions discussed here.

Comments

    Hans Gutbrod  11:12 UTC on 13 September 2017

    I would like to ask how to raise concerns about ethics about senior ICANN staff. It has come to my attention that a senior representative of the organization is behaving in ways that at the very least contain a problematic conflict of interest, and at worst suggest that they should not have a position in which they are entrusted with public affairs. I would appreciate your guidance on who is responsible on this matter.

    vinton g cerf  00:26 UTC on 14 September 2017

    Steve notes that this is his final year as Chairman. There will be further opportunities to thank him for his long service to ICANN, starting with his chairmanship of the SSAC, but I would like to note here my thanks as a member of the community and beneficiary of ICANN's work. Steve's leadership has been essential in the past several years especially leading up to the termination of the NTIA contract, freeing ICANN to operate as a stand-alone international entity. We collectively owe him a great debt.

    Emily Crane Pimentel  10:32 UTC on 14 September 2017

    To raise a concern, please visit ICANN’s Complaints Office and the ICANN Office of the Ombudsman. Links to both can be found below, under "Contact Us" and "Accountability & Transparency," respectively. The blog post "Clarifying the Roles of the ICANN Complaints Office and Ombudsman" may be helpful, and can be found in our blogs section, dated 18 May 2017. -- Emily Crane Pimentel, Director of Communications, ICANN

    dubai tour  01:15 UTC on 15 September 2017

    thank you

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