Skip to main content

Blog Update: BGC's Comments on Recent Reconsideration Request

Earlier this week ICANN's Board Governance Committee (BGC) recommended that the ICANN Board deny a Reconsideration Request from dotgay LLC, in which it objected to emails to authors of letters of support having been sent by an administrator at the Community Priority Evaluation (CPE) provider rather than an evaluator. This will be considered by the full Board at its next meeting.

As a reminder, the CPE process was developed by the global ICANN community. It is the responsibility of ICANN to ensure the process is followed. To reiterate, this BGC recommendation is not a statement about the validity of dotgay LLC's application or dotgay LLC's supporters. ICANN supports and encourages diversity and inclusion, both internally within ICANN organization and within our community.

Four applicants for .GAY remain in contention (including dotgay LLC), and we look forward to the award of the .GAY TLD in the near future.

For additional background information, I encourage you to read my earlier blog and view examples of CPE results, which are both published below.

Community Priority Evaluation Results: Examples

BGC's Comments on Recent Reconsideration Request

Chris Disspain, Chair, BGC – 3 February 2016

During its meetings on 13 January and 1 February 2016, ICANN's Board Governance Committee (BGC) considered a Request for Reconsideration filed by dotgay LLC. This request asked us to reconsider the outcome of a Community Priority Evaluation (CPE), which resulted in dotgay LLC's .GAY application not achieving community priority. Having carefully considered the Request for Reconsideration, the BGC denied it at our face-to-face meeting on 1 February 2016.

The information below provides a bit more detail about CPE and Reconsideration, and clarifies what this decision means for the dotgay LLC application, dotgay LLC's supporters and the .GAY TLD.

This decision does not mean there will be no .GAY TLD. There are four applicants (including dotgay LLC) vying to operate this TLD. These applicants have the option to resolve the contention among themselves, through channels outside of ICANN processes. If self-resolution cannot be achieved, the four applications for .GAY will be scheduled to participate in an ICANN-facilitated "method of last resort" auction to resolve the contention.

Of the four entities applying for the .GAY TLD, dotgay LLC's application was the only community application, and therefore the only application eligible to seek community priority through CPE. If an application achieves community priority, it is then able to move forward towards contracting, and the other applications will no longer proceed. dotgay LLC's .GAY application did not achieve community priority so it continues to compete with the other three applications.

It should be noted that dotgay LLC has been through both the CPE and Reconsideration processes twice. After completion of the first CPE in October 2014, through the Reconsideration process, a procedural error in the CPE was identified and the BGC determined that the application should be re-evaluated. However, the same outcome and score were achieved both times.

The BGC, which is responsible for evaluating such requests, is limited by the Bylaws in evaluating this Request for Reconsideration. Specifically, the BGC is only authorized to determine if any policies or processes were violated during CPE. The BGC has no authority to evaluate whether the CPE results are correct.

I want to make clear that the denial of the Request for Reconsideration is not a statement about the validity of dotgay LLC's application or dotgay LLC's supporters. The decision means that the BGC did not find that the CPE process for dotgay, LLC's .GAY application violated any ICANN policies or procedures.

It is ICANN's responsibility to support the community-developed process and provide equitable treatment to all impacted parties. We understand that this outcome will be disappointing to supporters of the dotgay LLC application. We appreciate the amount of interest that this topic has generated within the ICANN community, and we encourage all interested parties to participate in the multistakeholder process to help shape how future application rounds are defined.

For more information about CPE criteria, please see ICANN's Applicant Guidebook, which serves as basis for how all applications in the New gTLD Program have been evaluated. For more information regarding Requests for Reconsideration please see ICANN's Bylaws.


    Nguyen Phat  00:46 UTC on 01 July 2016

    very good

    karan  08:22 UTC on 21 December 2016

    The best thing which I liked it a lot google

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