Skip to main content

Board Member Integrity Screening

I have no doubt that all of ICANN agrees that the ICANN community and the organization should expect Board members to hold themselves to the highest standards of integrity, and to uphold the reputation and credibility of the Board as a whole. To that end, I want to share with you the steps that we have, and will be taking, in this regard.

As can be seen from Steve Crocker’s blog, the Board has been considering the issue of Board member screening for some time. The Board Governance Committee carefully considered this matter in detail at its meetings on 11 October 2017 and 27 October 2017. Based on this input, the Board is taking several steps.

First, the four current and incoming voting Board members who have not gone through the due diligence screening process that the Nominating Committee (NomCom) utilizes have volunteered to do so immediately. These are the voting Board members selected by the Country Code Names Supporting Organization (Chris Disspain and Mike Silber) and the Generic Names Supporting Organization (Becky Burr and Matthew Shears).

Second, should any concerns be raised during the screening process, these will be considered and the Board will take appropriate action depending on the severity and breadth of any such concerns, which may include invoking the Bylaws provisions relating the removal of Directors.

Third, on Thursday, the Board will pass a resolution directing Göran Marby, President and CEO, to develop a proposal paper to be posted for public comment. The paper will ask all of ICANN’s Supporting Organizations and Advisory Committees to seriously consider utilizing the same or similar integrity screening process for both voting directors and non-voting liaisons. As it does for the NomCom, the Address Supporting Organization and the At-Large community, the ICANN org is prepared to facilitate this screening process for all Board members selected by the Community.

We look forward to continuing the discussion of this issue following the public comment process mentioned above


    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"""" is not an IDN."