Skip to main content

Chairman’s Blog

Over the next few months I will be using this blog to share some insights and commentary on the operation of the ICANN Board and to introduce various Board members. This past week the Board passed a resolution to evolve the Board Governance Committee to be more responsive and more efficient in dealing with concerns with decisions of the Board.

I’ve asked Chris Disspain, chair of the Board Governance Committee to explain the details.

Evolving the Board Governance Committee

Chris Disspain, Board Governance Committee Chair

Over the past several weeks, the Board Governance Committee (BGC) has been considering how to streamline its work in the face of high volumes of accountability mechanism work, including Reconsideration Requests.

As many of you know, the BGC is responsible for helping the Board improve its performance. Like Board Governance Committees in other organizations – the core activities of the BGC include an array of board performance related activities, such as conflicts of interest policies, board committee structures (including slating and charters of other committees), governance guidelines and other important governance related activities (see https://www.icann.org/resources/pages/charter-06-2012-02-25-en)

Over the past several years, the BGC’s work on Reconsideration Requests has increased, and that is only expected to continue under the new Bylaws. The BGC advised the Board that the attention it devotes to the accountability mechanisms is reducing the time available for the BGC’s core governance work and that performance would be enhanced through the development of a Board committee responsible for the oversight of ICANN Accountability Mechanisms, including the BCG’s Reconsideration responsibilities. This will help improve our performance as a Board, the BGC’s performance, and help us serve the community better.

The BGC’s work on Reconsideration Requests is set out in the Fundamental Bylaws, the part of ICANN’s Bylaws that require community approval to change.

Following the BGC’s recommendation, the Board has decided to launch a process to initiate a Fundamental Bylaws amendment so that we can have a full discussion with the ICANN community on enhancing ICANN’s governance and responsiveness to accountability mechanisms, while respecting the new community powers. We look forward to this first use of the Empowered Community and the enhanced dialogue among ICANN and the community.

For more information, please see the Board’s resolution. We will keep you updated as the Bylaws amendment process moves forward.

Comments

    Mike Roch  23:58 UTC on 28 February 2017

    Good blog Chairman sir. Kudos..

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