Skip to main content
Resources

Minutes | Meeting of the New gTLD Program Committee

Note: On 10 April 2012, the Board established the New gTLD Program Committee, comprised of all voting members of the Board that are not conflicted with respect to the New gTLD Program. The Committee was granted all of the powers of the Board (subject to the limitations set forth by law, the Articles of Incorporation, Bylaws or ICANN's Conflicts of Interest Policy) to exercise Board-level authority for any and all issues that may arise relating to the New gTLD Program. The full scope of the Committee's authority is set forth in its charter at http://www.icann.org/en/groups/board/new-gTLD.

A Regular Meeting of the New gTLD Program Committee of the ICANN Board of Directors was held telephonically on 18 July 2014 at 13:00 UTC.

Committee Chairman Cherine Chalaby promptly called the meeting to order.

In addition to the Chair the following Directors participated in all or part of the meeting: Fadi Chehadé (President and CEO, ICANN), Steve Crocker (Board Chairman), Chris Disspain, Olga Madruga-Forti, Erika Mann, Gonzalo Navarro, Ray Plzak, George Sadowsky, and Mike Silber.

Heather Dryden, Bill Graham, Bruno Lanvin and Kuo-Wei Wu sent apologies.

Jonne Soininen (IETF Liaison) and Suzanne Woolf (RSSAC Liaison) were in attendance as non-voting liaisons to the Committee.

Secretary: John Jeffrey (General Counsel and Secretary).

ICANN Executives and Staff in attendance for all or part of the meeting: Akram Atallah (President, Global Domains Division); Francisco Arias (Director, Technical Services – Global Domains Division); Megan Bishop (Board Support Coordinator); Michelle Bright (Board Support Manager); Allen Grogan (Chief Contracting Counsel); Dan Halloran (Deputy General Counsel); Cyrus Namazi (Vice President, DNS Industry Engagement); Olof Nordling (Senior Director, GAC Relations); David Olive (Vice President, Policy Development); Erika Randall (Counsel); Amy Stathos (Deputy General Counsel); Christine Willett (Vice President, gTLD Operations); and Mary Wong (Senior Policy Director).

These are the Minutes of the Meeting of the New gTLD Program Committee, which took place on 18 July 2014.

  1. Main Agenda
    1. Name Collision Occurrence Management
    2. Reconsideration Request 14-10, dot Sport Limited

 

  1. Main Agenda:

    1. Name Collision Occurrence Management Framework

      The Committee continued its discussions concerning a framework to address collision occurrences between new gTLDs and existing private uses of the same strings. Akram Atallah presented the proposed Name Collision Occurrence Management Framework (the "Framework"), and engaged the Committee in a discussion of the elements of the Framework. Akram described the proposed 90-day "controlled interruption" period as the notification measure to alert parties that they may be leaking queries intended from private namespaces to the public DNS. Akram reported on the community comments on the Framework received during the ICANN meeting in London, and the proposed refinements to the Framework to address the community comments. The proposed refinements included modification of the length of time required for reporting on the handling of name collision reports.

      George Sadowsky inquired whether the proposed Framework was consistent with the advice offered by the Security and Stability Advisory Committee (SSAC) in SAC062. Akram provided an overview of some of the remaining differences between the approach proposed in the Framework and the SSAC's advice. Akram explained that the noted differences are not in conflict with the SSAC recommendations but present tradeoffs that the Committee should consider. One such difference Akram noted was the proposed standard that would be established to invoke an emergency response for name collision reports, which would be limited to situations where there is a reasonable belief that the name collision presents a clear and present danger to human life. The Committee discussed the appropriateness of such a limitation, and the tradeoffs associated with its implementation.

      Olga Madruga-Forti asked for clarification about how the Framework would address concerns raised by the SSAC and the community regarding the rules and method of allocation of previously "blocked" second-level domains after the controlled interruption period is completed. The Committee discussed the issue and considered how the existing rights protection mechanisms in in the New gTLD Program interact with the proposed requirements in the Framework. The Committee also considered whether changes would be needed to the existing rights protection mechanisms to address the community comments, and whether additional public comment was needed on the matter.

      As part of its discussion, the Committee also contemplated next steps to begin developing the long-term plan to manage gTLD name collision issues. Ray Plzak commented on potential policy issues relating to the name collision issue, and suggested the possibility of engaging the GNSO to consider whether policy work on developing the long-term plan should be undertaken. The Committee then discussed how best to engage with the GNSO on this issue and the process to move forward with the Framework.

      The Committee decided to schedule a follow-up meeting before the end of July to further consider the proposed Name Collision Occurrence Framework.

    2. Reconsideration Request 14-10, dot Sport Limited

      The Chair introduced the agenda item and provided a summary of the Board Governance Committee's recommendation on Reconsideration Request 14-10. Amy Stathos highlighted the grounds for reconsideration claimed in the request.

      Mike Silber moved and Chris Disspain seconded the proposed resolution. After discussion, the Committee took the following action:

      Whereas, dot Sport Limited filed Reconsideration Request 14-10 asking the New gTLD Program Committee ("NGPC") to reconsider: (i) the Expert Determination, and ICANN's acceptance of that Determination, upholding SportAccord's Objection to the Requester's application for .SPORTS; (ii) the International Centre for Expertise of the International Chamber of Commerce's designation of the Expert Panelist who presided over the objection proceedings; and (iii) the Board Governance Committee's ("BGC's") Determination denying Reconsideration Request 13-16.

      Whereas, the BGC considered the issues raised in Reconsideration Request 14-10.

      Whereas, the BGC recommended that the Request be denied because the Requester has not stated proper grounds for reconsideration, and the NGPC agrees.

      Resolved (2014.07.18.01), the NGPC adopts the BGC Recommendation on Reconsideration Request 14-10, which can be found at https://www.icann.org/en/system/files/files/recommendation-sport-21jun14-en.pdf [PDF, 205 KB].

      All members of the Committee present voted in favor of Resolution 2014.07.18.NG01. Bill Graham, Bruno Lanvin, Kuo-Wei Wu, Olga Madruga-Forti, and Erika Mann were unavailable to vote on the Resolution. The Resolution carried.

      Rationale for Resolution 2014.07.18.NG01

      1. Brief Summary

        SportAccord filed a Community Objection against Dot Sport Limited's (the "Requester") application for .SPORTS and prevailed. The Requester then filed Request 13-16, suggesting that, among other reasons, the Expert Panel ("Expert" or "Panel") allegedly violated established policy or process by failing to disclose material information relevant to his appointment. On 8 January 2014, the BGC denied Request 13-16, finding, among other things, that the Requester had provided no evidence demonstrating that the Expert had failed to follow the applicable ICC procedures for independence and impartiality.

        The Requester, in this second Reconsideration Request for the same matter, now claims that on 25 March 2014, it discovered additional evidence that the Expert had a conflict of interest. Specifically, the Requester claims that it recently discovered that the Expert now has, and previously has had, financial and professional relationships with an entity that is "related" to SportAccord. The Requester claims the Expert should have but did not disclose those relationships in the objection proceeding.

        The Requester's claims are unsupported. First, the Request is untimely. Request 14-10 challenges Board and staff actions that occurred on or prior to 13 January 2014, yet was received on 2 April 2014, well past the 15-day deadline to file a reconsideration request. While the Requester claims that this second Reconsideration Request is appropriate because the Requester only recently discovered the Expert's alleged conflict of interest, as is discussed below, the Requester's a claim does not justify an untimely reconsideration request. Second, the allegedly newly discovered information relating to a purported conflict of interest does not support reconsideration. Therefore, the BGC has recommended that Reconsideration Request 14-10 be denied. The NGPC agrees.

      2. Facts
        1. Relevant Background Facts

          Both dot Sport Limited (the "Requester") and SportAccord applied for .SPORTS and are in the same contention set.

          On 13 March 2013, SportAccord filed a Community Objection ("Objection") to the Requester's application, asserting that there was "substantial opposition to the gTLD application from a significant portion of the community to which the gTLD string may be explicitly or implicitly targeted." (Applicant Guidebook ("Guidebook"), § 3.2.1; New gTLD Dispute Resolution Procedure ("Procedure"), Art. 2e.)

          On 29 July 2013, the ICC appointed Dr. Guido Santiago Tawil as the expert ("Expert" or "Panel") to consider SportAccord's Objection. On 23 October 2013, the Panel rendered an Expert Determination in favor of SportAccord ("Expert Determination")1.

          On 8 November 2013, the Requester filed Request 13-16 2, seeking reconsideration of the Expert Determination, claiming that the Panel applied the wrong standard in contravention of established ICANN policy or process and the Expert failed to disclose material information relevant to his appointment in violation of established policy or process. On 8 January 2014, the Board Governance Committee ("BGC") denied Request 13-163.

          On 25 March 2014, the Requester purportedly discovered additional facts regarding an alleged commercial relationship between the Expert and the International Olympic Committee ("IOC"), an entity that the Requester contends "effectively control[s]" SportAccord4. (Request, §8, Pg. 5.) Specifically, the Requester claims that it discovered that: (i) one of the Expert's clients, DirecTV, acquired broadcasting rights for the Olympics from the IOC on 7 February 2014 (but only after the Expert Determination and the BGC's Determination on Request 13-16 were issued); and (ii) a partner in the Expert's law firm is the president of Torneos y Competencias S.A. ("TyC"), a company which has a history of securing Olympic broadcasting rights and of which DirecTV Latin America is the principal shareholder5. The Requester forwarded that information to the Ombudsman, with whom it had filed a complaint.

          On 31 March 2014, the Ombudsman issued a draft report on the Requester's complaint, which was later withdrawn pending consultation with other relevant parties.

          On 2 April 2014, the Requester filed Request 14-106, seeking reconsideration of: (i) the denial of Request 13-16; (ii) the Expert Determination and ICANN's acceptance of it; and (iii) the ICC's appointment of the Expert.7

          Recognizing that pursuant to Article V, Section 2 of the ICANN Bylaws, a complaint lodged with the Ombudsman cannot concurrently be pursued while another accountability mechanism on the same issue is ongoing, the Ombudsman advised ICANN that he sought confirmation from the Requester as to whether it was aware of these Bylaws parameters and asked how the Requester wished to proceed. ICANN was advised on or about 13 May 2014 that the Requester confirmed that it was fully aware of these Bylaws provisions and that it would like to pursue this Reconsideration Request rather than the Ombudsman's request.

        2. Requester's Claims

          The Requester makes three claims. First, the Requester claims that the BGC failed to consider material information in rejecting Request 13-16, namely the allegedly newly-discovered information regarding the Expert's alleged conflict of interest. Second, the Requester claims the Expert violated ICANN policy and process by failing to reveal his alleged conflict of interest. Third, the Requester claims that the ICC violated ICANN policy and process in appointing the Expert.

      3. Issues

        The issues for reconsideration are as follows:

        1. Whether the Board failed to consider material information in rejecting Reconsideration Request 13-16, namely the allegedly newly-discovered information regarding the Expert's alleged conflict of interest;
        2. Whether the Expert violated any ICANN policy and process by failing to disclose his alleged conflict of interest; and
        3. Whether the ICC violated any ICANN policy and process in appointing the Expert.
      4. The Relevant Standards for Evaluating Reconsideration Requests

        ICANN's Bylaws call for the BGC to evaluate and make recommendations to the Board with respect to Reconsideration Requests. See Article IV, Section 2 of the Bylaws. The NGPC, bestowed with the powers of the Board in this instance, has reviewed and thoroughly considered the BGC Recommendation on Request 14-10 and finds the analysis sound.8

      5. Analysis and Rationale
        1. The Request is Untimely.

          The BGC concluded, and the NGPC agrees, that Reconsideration Request 14-10 is untimely and does not support reconsideration. Reconsideration requests must be submitted within 15 days of either "the date on which information about the challenged Board action is first published in a resolution [including rationale]" or "the date on which the party submitting the request became aware of, or reasonably should have become aware of, the challenged staff action." (Bylaws, Art. IV, § 2.5.) The Requester seeks reconsideration of: (i) the appointment of the Expert, which occurred on 29 July 2013; (ii) the Expert Determination, which was issued on 23 October 2013; and (iii) the BGC's determination on Reconsideration Request 13-16, which was issued on 8 January 2014 and posted on 13 January 2014.

          Reconsideration Request 14-109, however, was received on 2 April 2014, which is: (i) over six months after the Expert was appointed; (ii) nearly six months following the issuance of the Expert Determination; and (iii) nearly three months following the BGC's determination on Request 13-16.

          The Requester claims that on 25 March 2014 it discovered new evidence that: (i) one of the Expert's clients, DirecTV, acquired broadcasting rights for the Olympics on 7 February 2014, following the issuance of the Expert Determination ("DirecTV Contract"); and (ii) a partner in the Expert's law firm is the president of TyC, a company which has a history of securing Olympics broadcasting rights and of which DirecTV Latin America is the principal shareholder ("TyC Relationship"). In sum, the Requester suggests that an alleged connection between the Expert (or his law firm) and DirecTV, a "recipient of IOC broadcasting rights,"; creates a conflict of interest because SportAccord and the IOC enjoy a "close collaborative relationship." (Request, § 8, Pg. 5-8.)

          Based upon this belated discovery of new evidence, the Requester claims the 15-day deadline for reconsideration requests should be tolled. (Request, § 5, Pg. 2.) The Requester, however, does not explain how it suddenly became aware of this information on 25 March 2014, or explain why it could not reasonably have become aware of the information at an earlier date.

          The only recent event that the Requester claims creates an alleged conflict of interest is the DirecTV Contract, but that contract was signed on 7 February 2014, almost two months prior to the filing of the instant Request (and nearly five months after the Expert issued the Determination). The Requester's only other evidence for an alleged conflict is the TyC Relationship, a business relationship that appears to be decades old. In addition, all of the Requester's evidence regarding the DirecTV Contract and the TyC Relationship is based on publicly available information from Internet sites such as Wikipedia, Chambers and Partners, and a public sports website, which could have been discovered long prior to 25 March 2014.

          Because the Requester could have become aware of the alleged conflicts earlier, the Requester's belated discovery of publicly available information does not justify tolling the 15-day time limit. (Bylaws, Art. IV, § 2.5; see also, id. at Art. IV, § 2.2 (reconsideration based on alleged failure to consider material information is inappropriate where the requester could have submitted, but did not submit, the information for the Board's consideration).)

        2. The "Newly-Discovered" Evidence Does Not Support Reconsideration.

          The Requester cites to two pieces of "newly-discovered" evidence that allegedly establish the Expert's conflict of interest: (1) the DirecTV Contract; and (2) the TyC Relationship. Separate and apart from the timeliness issue, the BGC concluded, and the NGPC agrees, that the "newly-discovered" evidence of an alleged conflict of interest does not support reconsideration.10

          1. The DirecTV Contract is Not Evidence of a Conflict of Interest Sufficient to Support Reconsideration.

            In support of its claim that there is a "direct commercial relationship" between the IOC and the Expert, the Requester relies on the 7 February 2014 DirecTV Contract, stating that: "just 3 months after [the Expert's Determination on the SportAccord Objection,] Direct TV[, one of the Expert's clients,] secured a highly lucrative and sought after broadcasting rights deal covering Latin America for the 2014 winter Olympic Games in Sochi, Russia and the 2016 summer Olympic Games in Rio de Janeiro, Brazil." (Request, § 8, Pg. 7.) The Requester concedes that the purported "direct commercial relationship" arose more than three months after the Expert Determination, and does not even attempt to establish that the belated 7 February 2014 DirecTV Contract somehow affected the Expert's 23 October 2013 Determination.

            Likewise, the BGC could not have considered this information on 8 January 2014, when it rendered its determination on Request 13-16, because the DirecTV Contract had not yet been executed.

            As a result, the Requester has failed to demonstrate that the Expert or the ICC violated established policies or procedures or that the BGC failed to consider material information. Therefore, reconsideration is not appropriate. (Bylaws, Art. IV, § 2.)

          2. The TyC Relationship Does Not Support Reconsideration.

            The Requester also alleges a "newly discovered" conflict of interest based on the TyC Relationship. (Request, § 8, Pgs. 7-8.) Specifically, the Requester claims that DirecTV Latin America is the principal shareholder of TyC, another sports broadcasting firm in the Latin American region. (Id., § 8, Pg. 7.) The Requester states that TyC is "a major client of M&M Bomchil law firm," where the Expert is a partner. (Id.) The Requester further states that the President of TyC is also a Senior Partner in M&M Bomchil and "is therefore a business partner of [the Expert]." (Id.) The Requester alleges a conflict of interest based on its claim that TyC "has a longstanding business relationship with IOC having secured broadcasting rights on 5 consecutive occasions since the Atlanta Games in 1996," and that TyC "most recently won the Argentinean television rights for the Vancouver 2010 Winter Olympics and London 2012 Olympic Games." (Id. at § 8, Pg. 8 (emphasis added).) In this regard, the Requester claims that the Expert should have disclosed the TyC Relationship and, having failed to do so, has violated ICANN policy and process.

            Section 3.4.4 of the Guidebook governs the selection of expert panels for purposes of the objection procedures at issue here. Section 3.4.4 provides that the ICC will "follow its adopted procedures for requiring such independence, including procedures for challenging and replacing an expert for lack of independence." (Guidebook, Section 3.4.4.) The ICC Rules of Expertise would therefore govern any challenges to the independence of experts appointed to evaluate community objections. Requester provides no evidence demonstrating that the Expert failed to follow the applicable ICC procedures for independence and impartiality prior to his appointment or that the ICC failed to require the Expert to do so. As the BGC noted in its determination on Request 13-16, the Expert submitted to the ICC, and to the parties, his curriculum vitae, as well as his Declaration of Acceptance and Availability and Statement of Impartiality and Independence in accordance with the ICC Rules of Expertise. (13-16 Determination at Pgs. 12-13.) As such, reconsideration is not appropriate with respect to the Expert's disclosure.

            Reconsideration is also unwarranted with respect to the BGC's failure to consider the TyC Relationship in its determination on Request 13-16. Reconsideration is appropriate for "actions or inactions of the ICANN Board that have been taken or refused to be taken without consideration of material information, except where the party submitting the request could have submitted, but did not submit, the information for the Board's consideration at the time of the action or refusal to act." (Bylaws, Art. IV, § 2.2(b)) (emphasis added). As discussed above, the TyC Relationship appears to be decades-old, and the Requester gives no explanation for why it did not submit, or could not have submitted, the information regarding the relationship to the BGC at the time the BGC considered Request 13-16.

            The Requester's failure to submit the evidence for the BGC's consideration with Request 13-16 does not constitute a failure on the part of the BGC to consider material evidence and does not constitute a basis for reconsideration of Request 13-16.

      6. Decision

        The NGPC had the opportunity to consider all of the materials submitted by or on behalf of the Requester or that otherwise relate to Request 14-10. Following consideration of all relevant information provided, the NGPC reviewed and has adopted the BGC's Recommendation on Request 14-10, which shall be deemed a part of this Rationale. The full text of Recommendation can be found at https://www.icann.org/en/system/files/files/recommendation-sport-21jun14-en.pdf [PDF, 205 KB] and is attached to the Reference Materials to the NGPC Submission on this matter.

        In terms of timing of the BGC's Recommendation, Section 2.16 of Article IV of the Bylaws provides that the BGC shall make a final determination or recommendation to the Board [or NGPC as appropriate] with respect to a Reconsideration Request within thirty days following receipt of the request, unless impractical. See Article IV, Section 2.16 of the Bylaws. To satisfy the thirty-day deadline, the BGC would have to have acted by 2 May 2014. Due to the Requester's invocation of multiple accountability mechanisms on parallels tracks, including the complaint the Requester lodged with the Ombudsman and the instant Reconsideration Request, additional time was required for the Ombudsman to confer with the Requester and to clarify which accountability mechanism the Requester intended to pursue, delaying the BGC's consideration of this matter. Moreover, due to the volume of Reconsideration Requests received within recent months, the first practical opportunity for the BGC to make a decision on this Request was on 21 June 2014; it was impractical for the BGC to do so sooner. Accordingly, the NGPC meeting on 18 July 2014, was the first NGPC meeting that has been scheduled following the BGC's action on Request 14-10 with sufficient time to evaluate and consider the BGC's Recommendation.

        Adopting the BGC's recommendation has no financial impact on ICANN and will not negatively impact the systemic security, stability and resiliency of the domain name system.

        This decision is an Organizational Administrative Function that does not require public comment.

 

The Chair called the meeting to a close.

Published on 9 September 2014


1 https://www.icann.org/en/system/files/files/request-annex-sport-1-08nov13-en.pdf [PDF, 141 KB]

2 https://www.icann.org/en/system/files/files/request-sport-08nov13-en.pdf [PDF, 159 KB]

3 https://www.icann.org/en/system/files/files/determination-sport-08jan14-en.pdf [PDF, 184 KB]

4 In support of its contention, the Requester offers only that: (a) two of the six members of SportAccord's Executive Council are also members of the IOC; and (b) "[f]ive of the eight members of the Council of SportAccord are directly appointed by three out of the only four sport associations officially recognized by the IOC on their website." (Request, § 8, Pg. 5.) The Requester also points out that SportAccord's website states that SportAccord enjoys a "close collaborative relationship" with the IOC. (Id.)

5 https://www.icann.org/en/system/files/files/request-sport-02apr14-en.pdf [PDF, 866 KB]

6 https://www.icann.org/en/system/files/files/request-sport-02apr14-en.pdf [PDF, 866 KB]

7 Although the Requester only requests reconsideration of the ICC's appointment of the Expert, it also appears to object to the ICC's response to the Requester's newly-discovered information, stating that the Requester's representative "wrote to the ICC on two occasions to request that the ICC question [the Expert]" about the alleged conflict of interest, but that the ICC "repeatedly declined to do so." (Request, § 8, Pg. 5.) However, this claim is untimely, and the Requester has not identified any policy or procedure that the ICC allegedly violated that would support reconsideration.

8 Having a reconsideration process whereby the BGC reviews and, if it chooses, makes a recommendation to the Board/NGPC for approval, positively affects ICANN's transparency and accountability. It provides an avenue for the community to ensure that staff and the Board are acting in accordance with ICANN's policies, Bylaws, and Articles of Incorporation.

9 https://www.icann.org/en/system/files/files/request-sport-02apr14-en.pdf [PDF, 866 KB]

10 In support of its Request, the Requester references a 31 March 2014 communication the Ombudsman sent to the Board regarding the Expert's alleged conflict of interest, in which the Ombudsman expressed concern and recommended "a rehearing of the objection with a different expert appointed." (Request, § 8, Pg. 11.) However, the Ombudsman's communication, by itself, does not support reconsideration because it does not constitute Board action. Moreover, the Ombudsman's communication has subsequently been withdrawn. As such, it would be premature for the NGPC to consider the Ombudsman's comments on any alleged conflict of interest.

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