Jump to content

Reconsideration: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
Jessica (talk | contribs)
 
(3 intermediate revisions by 2 users not shown)
Line 21: Line 21:


==Process==
==Process==
Under the current Bylaws, the [[ICANN Board|Board Accountability Mechanisms Committee]] (BAMC) reviews and considers the requests.<ref>Articles 4.2(e) and (k), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> In previous versions of the reconsideration process, the Board Governance Committee was responsible for the full review process (with no referral to the ICANN Ombudsman as described below).<ref>see, e.g., the [https://www.icann.org/resources/pages/bylaws-2012-02-25-en#IV Accountability Mechanisms] of the Bylaws in effect as amended in July 2014</ref> If the committee determines that the reconsideration request fails to meet the requirements specified in Article 4.2 of the Bylaws, or is "frivolous," it can summarily dismiss the request on that basis.<ref>Article 4.2(k), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> Dismissal on the sole basis that the request is frivolous is rare.<ref>See, e.g., [https://www.icann.org/resources/pages/reconsideration-16-2-commercial-connect-request-2016-02-10-en Request 16.2 - Commercial Connect LLC], February 25, 2016, where despite noting Commercial Connect's abuse of "all of ICANN's Accountability Mechanisms," the BAMC nonetheless provides an analysis on the sufficiency of the request.</ref>  
Under the current Bylaws, the [[Board Committees|Board Accountability Mechanisms Committee]] (BAMC) reviews and considers the requests.<ref>Articles 4.2(e) and (k), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> In previous versions of the reconsideration process, the Board Governance Committee was responsible for the full review process (with no referral to the ICANN Ombudsman as described below).<ref>see, e.g., the [https://www.icann.org/resources/pages/bylaws-2012-02-25-en#IV Accountability Mechanisms] of the Bylaws in effect as amended in July 2014</ref> If the committee determines that the reconsideration request fails to meet the requirements specified in Article 4.2 of the Bylaws, or is "frivolous," it can summarily dismiss the request on that basis.<ref>Article 4.2(k), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> Dismissal on the sole basis that the request is frivolous is rare.<ref>See, e.g., [https://www.icann.org/resources/pages/reconsideration-16-2-commercial-connect-request-2016-02-10-en Request 16.2 - Commercial Connect LLC], February 25, 2016, where despite noting Commercial Connect's abuse of "all of ICANN's Accountability Mechanisms," the BAMC nonetheless provides an analysis on the sufficiency of the request.</ref>  


If the reconsideration request passes through the initial review, the BAMC refers the matter to the [[ICANN Ombudsman]] for investigation. In the event that the Ombudsman must recuse themselves, the BAMC will investigate on its own. The Ombudsman may employ the services of experts to assist with their investigation.<ref>Article 4.2(l), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> In addition, the BAMC may request additional information from the requestor, third parties, ICANN staff, and anyone else it deems relevant to the inquiry.<ref>Articles 4.2(m)-(o), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref>  
If the reconsideration request passes through the initial review, the BAMC refers the matter to the [[ICANN Ombudsman]] for investigation. In the event that the Ombudsman must recuse themselves, the BAMC will investigate on its own. The Ombudsman may employ the services of experts to assist with their investigation.<ref>Article 4.2(l), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref> In addition, the BAMC may request additional information from the requestor, third parties, ICANN staff, and anyone else it deems relevant to the inquiry.<ref>Articles 4.2(m)-(o), [https://www.icann.org/resources/pages/governance/bylaws-en/#article4 ICANN Bylaws], as amended November 28, 2019</ref>  
Line 39: Line 39:
===Early Days: 1999-2000===
===Early Days: 1999-2000===
In the lead-up to ICANN's pilot expansion of the number of [[Top Level Domain|TLDs]], the reconsideration process was utilized for a variety of issues, from inclusion of specific constituencies in SOs to attempted appeals of UDRP decisions.
In the lead-up to ICANN's pilot expansion of the number of [[Top Level Domain|TLDs]], the reconsideration process was utilized for a variety of issues, from inclusion of specific constituencies in SOs to attempted appeals of UDRP decisions.
{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | Early Reconsideration Requests, 1999-2000
|+ class="nowrap" | Early Reconsideration Requests, 1999-2000
|-
|-
Line 115: Line 115:
===2000: New TLD Expansion Pilot===
===2000: New TLD Expansion Pilot===
ICANN's pilot program for expanding the root resulted in a number of applications for new TLDs, and a number of reconsideration requests regarding decisions about those applications.
ICANN's pilot program for expanding the root resulted in a number of applications for new TLDs, and a number of reconsideration requests regarding decisions about those applications.
{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | 2000 New TLD Pilot & Sponsored TLDs
|+ class="nowrap" | 2000 New TLD Pilot & Sponsored TLDs
|-
|-
Line 146: Line 146:
| "ICANN could not responsibly reject proposals for new TLDs merely because the applicants have requested TLDs that include letters also found in country-code TLDs such as <.bz.>"
| "ICANN could not responsibly reject proposals for new TLDs merely because the applicants have requested TLDs that include letters also found in country-code TLDs such as <.bz.>"
|-
|-
| [https://www.icann.org/resources/pages/01-3-2014-02-07-en 01-3:] [[Monsoon Assets Limited]] (BVI)]
| [https://www.icann.org/resources/pages/01-3-2014-02-07-en 01-3:] [[Monsoon Assets Limited]] (BVI)
| Request to reconsider non-selection of Monsoon's application for the New TLD pilot
| Request to reconsider non-selection of Monsoon's application for the New TLD pilot
| No*
| No*
Line 153: Line 153:
| Reconsideration request was not timely submitted and did not substantiate its claims
| Reconsideration request was not timely submitted and did not substantiate its claims
|}
|}
===Diverse and Sparse Requests: 2001-2010===
===Diverse and Sparse Requests: 2001-2010===
During most of the 2000s, the reconsideration mechanism was used for a variety of complaints about ICANN processes or policy-making. There were no reconsideration requests in 2003, 2007, 2008, and 2009.
During most of the 2000s, the reconsideration mechanism was used for a variety of complaints about ICANN processes or policy-making. There were no reconsideration requests in 2003, 2007, 2008, and 2009.
   
   
{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | The Decade of Varied Requests: 2001 - 2010
|+ class="nowrap" | The Decade of Varied Requests: 2001 - 2010
|-
|-
Line 310: Line 311:
The vast majority of the reconsideration requests from October 2010 until April 2014 dealt with: policy formation, [[Applicant Guidebook]] development, and other issues related to the launch of [[New gTLD Program]]; and after the launch, threshold decisions regarding applications for TLD strings.
The vast majority of the reconsideration requests from October 2010 until April 2014 dealt with: policy formation, [[Applicant Guidebook]] development, and other issues related to the launch of [[New gTLD Program]]; and after the launch, threshold decisions regarding applications for TLD strings.


{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | Applicant Guidebook, Policy Development, and Application Processing: 2010-2014
|+ class="nowrap" | Applicant Guidebook, Policy Development, and Application Processing: 2010-2014
|-
|-
Line 576: Line 577:
From April 2014 to the end of 2016, the reconsideration process was used extensively by applicants to the [[New gTLD Program]]. The [[Community Priority Evaluation]] process was a frequent bone of contention, as well as various string contention sets.
From April 2014 to the end of 2016, the reconsideration process was used extensively by applicants to the [[New gTLD Program]]. The [[Community Priority Evaluation]] process was a frequent bone of contention, as well as various string contention sets.


{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | New gTLD Program: 2014-2016
|+ class="nowrap" | New gTLD Program: 2014-2016
|-
|-
Line 952: Line 953:


===Reconsideration Stalwarts & Back to Business: 2016-Present===
===Reconsideration Stalwarts & Back to Business: 2016-Present===
By late 2016, all but a few applicants to the [[New gTLD Program]] had acknowledged defeat or were engaged in other processes to resolve their disputes with ICANN and other applicants. Those still persisting with reconsideration requests were increasingly focused on staff responses to [[Documentary Information Disclosure Process]] requests surrounding the disposition of their various applications. The reconsideration process returned to a mixture of consumer complaints and objections to policy or process.
By late 2016, all but a few applicants to the [[New gTLD Program]] had acknowledged defeat or were engaged in other processes to resolve their disputes with ICANN and other applicants. Those still persisting with reconsideration requests were increasingly focused on staff responses to [[Documentary Information Disclosure Policy]] requests surrounding the disposition of their various applications. The reconsideration process returned to a mixture of consumer complaints and objections to policy or process.


In 2020 and 2021, the BAMC became more comfortable with summary dismissal of requests that were either outside the scope of the Bylaws, or failed to state a claim.
In 2020 and 2021, the BAMC became more comfortable with summary dismissal of requests that were either outside the scope of the Bylaws, or failed to state a claim.


{| class="wikitable mw-collapsible mw-collapsed" width=100%
{| class="wikitable mw-collapsible" width=100%
|+ class="nowrap" | Lingering New gTLD Program Issues and Other Matters: 2016-Present
|+ class="nowrap" | Lingering New gTLD Program Issues and Other Matters: 2016-Present
|-
|-

Latest revision as of 19:25, 14 January 2022

Reconsideration is one of ICANN's Accountability Mechanisms. This option is provided in the ICANN Bylaws Article IV, Section 2. Any person or entity materially affected by an action (or inaction) of ICANN may request reconsideration of that action by the ICANN Board.[1]

Matters Subject to Reconsideration[edit | edit source]

Requestors may submit reconsideration requests if they have been adversely affected by:

(i) One or more Board or Staff actions or inactions that contradict ICANN's Mission, Commitments, Core Values and/or established ICANN policy(ies);

(ii) One or more actions or inactions of the Board or Staff that have been taken or refused to be taken without consideration of material information, except where the Requestor could have submitted, but did not submit, the information for the Board's or Staff's consideration at the time of action or refusal to act; or

(iii) One or more actions or inactions of the Board or Staff that are taken as a result of the Board's or staff's reliance on false or inaccurate relevant information.[2]

The ICANN Empowered Community (EC) may submit a "Community Reconsideration Request" if approved under the rules listed in the "EC Mechanism" Annex of the Bylaws[3]; and if the matter relates to the exercise of the powers and rights of the EC as defined by the Bylaws.[4] Annex D outlines the process through which "Decisional Participants" may petition the EC to submit a Community Reconsideration Request.[3]

Applicability to Processing of Applications in the New gTLD Program[edit | edit source]

The reconsideration process was available for challenges to expert determinations rendered by third party dispute resolution service provider (DRSP) panels in the New gTLD Program, if the panels or staff failed to follow established policies or processes in reaching the expert determination.[5] In other words, the substance of an expert determination could not be challenged, but a failure in procedural requirements could be.

The vast majority of the reconsideration requests related to third party, staff, and Board decisions related to TLD applications were denied, in part or in whole, because they attempted to request reconsideration of substantive matters, rather than procedural issues.

Excluded from Reconsideration[edit | edit source]

The Bylaws expressly exclude the following subjects from the reconsideration mechanism:

  • Disputes relating to country code top-level domain ("ccTLD") delegations and re-delegations;
  • Disputes relating to Internet numbering resources; and
  • Disputes relating to protocol parameters.[6]

Process[edit | edit source]

Under the current Bylaws, the Board Accountability Mechanisms Committee (BAMC) reviews and considers the requests.[7] In previous versions of the reconsideration process, the Board Governance Committee was responsible for the full review process (with no referral to the ICANN Ombudsman as described below).[8] If the committee determines that the reconsideration request fails to meet the requirements specified in Article 4.2 of the Bylaws, or is "frivolous," it can summarily dismiss the request on that basis.[9] Dismissal on the sole basis that the request is frivolous is rare.[10]

If the reconsideration request passes through the initial review, the BAMC refers the matter to the ICANN Ombudsman for investigation. In the event that the Ombudsman must recuse themselves, the BAMC will investigate on its own. The Ombudsman may employ the services of experts to assist with their investigation.[11] In addition, the BAMC may request additional information from the requestor, third parties, ICANN staff, and anyone else it deems relevant to the inquiry.[12]

The Ombudsman (or the BAMC on its own behalf) completes a substantive evaluation of the reconsideration request. Following the completion of the substantive evaluation, the BAMC shall review and consider all information gathered in the written record, including supplemental information from any of the sources described in Sections 4.2(m)-(o).[13]

The BAMC then submits a non-binding recommendation to the full Board for its consideration. The Board makes the final determination on the reconsideration request.[14]

Urgent Requests[edit | edit source]

The requestor may request urgent review of an action or inaction by the Board if they believe that "timing requirements of the process set forth in...Section 4.2 are too long." An approved request for urgent review causes the entire process to operate under expedited time frames.[15] Only actions by the Board are subject to urgent review.[16]

Summary Tables of Requests[edit | edit source]

The following tables present the reconsideration requests submitted to ICANN, their subject matter, and their disposition.

  • "Deny" in the "Recommendation" and "Board Action" columns means that no action was taken regarding the reconsideration request (i.e., the request was denied).
  • The "Dismissed?" column designates whether the request was summarily dismissed under the then-current standards for dismissal. In many cases, even if the committee's recommendation noted that a request could be summarily dismissed for procedural reasons, the reviewing committee would still address the substance of the request. In such cases, the "Dismissed?" column will read "No*" and the notes column will identify the justifications for dismissal.
  • The requests are numbered by ICANN in order received by year. No requests were received in 2003, 2007, 2008, and 2009.[17]

Early Days: 1999-2000[edit | edit source]

In the lead-up to ICANN's pilot expansion of the number of TLDs, the reconsideration process was utilized for a variety of issues, from inclusion of specific constituencies in SOs to attempted appeals of UDRP decisions.

Early Reconsideration Requests, 1999-2000
Reconsideration Request Subject Dismissed? Recommendation Board Action Notes
99-1: Eric Brunner & Bob Gough Proposing the creation of a separate Indigenous Intellectual Property Constituency No Deny Deny
99-2: Gene Marsh Inclusion of Top Level Domain Association in the Names Council Yes Deny Deny The original request did not include the required information, and a request from ICANN to Marsh to provide additional information went unanswered. Request was also time-barred.
99-3: Bruce Perelman Allowing the registration of ?.com and ~.com Yes Deny Deny There was no action by the Board that could be reconsidered.
99-4: Karl Auerbach Revocation of the agreement between the Department of Commerce, ICANN, and Network Solutions No Deny Deny
00-1: Russ Smith Reconsideration of the decision to cancel 800+ accidentally registered domain names with trailing hyphens (i.e., abc-.com) No Deny Deny For a brief period of time, NSI's software enabled people to register names with trailing hyphens, which was contrary to both RFC and existing policy.
00-2: Nigel Roberts Contents of request withheld by request Probably No Recommendation Issued Did not act Both the request and ICANN's response are not published, at the request of Mr. Roberts
00-3: Paul Wilson obo APNIC Inclusion of term "globally specified applications" in IANA Functions Contract No No Recommendation Issued Did not act
00-4: Bret Fausett ICANN's failure to timely publish board meeting minutes from April 6 No Revise Bylaws Bylaws for publication of meeting minutes revised after public comment
00-5: James Trefil obo Adam Corelli Requestor lost a UDRP case and appealed in court; wanted the link to the UDRP decision removed from ICANN's website No Deny Deny

2000: New TLD Expansion Pilot[edit | edit source]

ICANN's pilot program for expanding the root resulted in a number of applications for new TLDs, and a number of reconsideration requests regarding decisions about those applications.

2000 New TLD Pilot & Sponsored TLDs
00-6: A. J. L. de Breed Rejection of an application for a New TLD under the 2000 program because it was accompanied by a $1,000 check, rather than the required $50,000 fee No Deny Deny
00-7: D. Alexander Floum ICANN Staff posted its evaluation of Floum's company, IODesign, as part of IODesign's application for a new TLD. The evaluation categorized IODesign's technical and business readiness as "poor." Floum wanted that evaluation to be removed. No Deny Deny
00-8: Ivan Vachovsky
00-9: Roy Goldberg
00-10: Paul Stahura
00-11: Sarnoff Corporation
00-12: The .TV Corporation
00-13: Image Online Design
00-14: SRI International
00-16: Telnic Limited
01-2: .Kids Domains, Inc.
The listed reconsiderations requests all dealt with applications under ICANN's 2000 New TLD pilot program which did not succeed. All of them asked for reconsideration of those applications. No Deny Deny The committee, in its recommendations regarding all of these requests, prefaced their analysis of the specific request with a general overview of the selection process.
01-1: Beltraide Request to reconsider delegation of .biz, because of confusion with the .bz ccTLD No Deny Deny "ICANN could not responsibly reject proposals for new TLDs merely because the applicants have requested TLDs that include letters also found in country-code TLDs such as <.bz.>"
01-3: Monsoon Assets Limited (BVI) Request to reconsider non-selection of Monsoon's application for the New TLD pilot No* Deny Deny Reconsideration request was not timely submitted and did not substantiate its claims

Diverse and Sparse Requests: 2001-2010[edit | edit source]

During most of the 2000s, the reconsideration mechanism was used for a variety of complaints about ICANN processes or policy-making. There were no reconsideration requests in 2003, 2007, 2008, and 2009.

The Decade of Varied Requests: 2001 - 2010
01-4: Verio ICANN's changes to the RAA prohibiting the use of WHOIS information for unsolicited marketing communications No Refer to DNSO, but make no changes at present Accepted recommendation
01-5: Michael Froomkin and Jonathan Weinberg Withdraw ICP-3 from the ICP Series No Deny, but adopt formal process of Board approval of designation to ICP Followed recommendation
01-6: Russ Smith Arguing for increasing publicity of materials relevant to UDRP procedures, standards, and rules No Forward suggestions to UDRP Providers Approved the committee's suggestion Responsibility for training third party neutrals rests with UDRP service providers, not ICANN
01-7: Edward Hasbrouck RAA for .aero should be revised No Deny Deny
02-1: David Ogden Denial of registration of pops.int by the Stockholm Convention on Persistent Organic Pollutants No Reverse Decision Reversed Decision
02-2: Russ Smith Enforce transfer obligations to comply with transfer policies No Deny Deny
02-3: Tony So Reversing deletion and loss of control of So's domain name No Subsequent events made the issue moot, so no action required; however, recommend a redemption grace period policy for registrants Followed recommendation regarding a grace period
02-4: Ethan Katsch Dissolution of the Independent Review Panel Nominating Committee No Deny Deny
02-5: Dotster Board resolution modifying agreement with Verisign to allow "Wish List Service" No Deny Deny
02-6: VeriSign Board resolution 02-100 No Modify Condition C to better meet the needs of consumers; no other action Approved recommendation
04-1: Bret Fausett Failure to post minutes of board meeting within timeline No Post was a day late; board should consider audio recordings of meetings; recommend staff training re: timelines Approved recommendations
04-2: Danny Lee Younger ga@dnso.org listserv archives not working No Problem was resolved before request was addressed No action Apologizing for delays in responding, staff noted that "We currently receive tens of thousands of pieces of spam for each legitimate request for reconsideration sent to reconsider@icann.org."
04-3: Network Solutions Alleged approval of alterations to Verisign Registry Agreement No No recommendation N/A It seems possible that this request was overtaken by events surrounding the Site Finder litigation
05-1: Bret Fausett Another missed deadline for posting of meeting minutes No Posting was late, although minimal impact b/c the affected public comment period deadline was extended; however, recommend real-time scribing of board meetings Approved recommendation
05-2: Edward Hasbrouck May 3, 2005 special meeting of the board was closed to outside observers Yes Ombudsman advised the committee that this request was no different from a complaint to the Ombuds office. Deemed frivolous.
06-1: Network Solutions, LLC, et. al. Board approval of Verisign Settlement in February 2006 No* Deny Deny Reconsideration requests are void if there was opportunity for requesters to make their opinions known to the board during public comment or other opportunities. Request also fails to substantiate or support its claims.
06-2: Danny Younger Board approval of Verisign settlement in February 2006 No* Deny Deny "The Committee concludes that there are no grounds to proceed, as each of the grounds is either: (i) not an appropriate subject for reconsideration; (ii) already considered by the Board, or (iii) could have been brought to the Board's attention prior to the 28 February 2006 approval."
06-3: Marilyn Cade Protesting ICANN Governance Committee decision that she could not run in a mid-term election for a vacated board seat. Cade resigned from the NomCom in order to run for the seat. No* Deny Deny Bylaws are "unambiguous" regarding former NomCom members' eligibility to be selected for board service; requestor fails to state a claim that would be subject to reconsideration
06-4: ICM Registry Board rejection of Registry Agreement with ICM for .xxx No No recommendation - Request Withdrawn by ICM, October 2006 N/A
10-1: Michael Palage Late publication of board meeting minutes No Posting was 10 hours late, so limited impact; but, recommend amendment of ICANN Bylaws requiring the posting of board resolutions within 2 days, and preliminary report within 7 days. Approved recommendation Palage, in the Public Comments to the proposed Bylaws amendment, expressed disappointment
10-2: .jobs Charter Compliance Coalition Approval of amendments to .JOBS Registry Agreement, permitting noncompanyname.jobs registrations & proposing a phased allocation of such names No Deny, but ICANN staff to closely monitor the rollout of these new names to ensure the registry complies with its charter Approved recommendation "…the Board Governance Committee is not at all clear that it has a full picture of how Employ Media intends to implement the Phased Allocation Process.""[18]

Lead-up and Application Phase of the New gTLD Program: 2010-2014[edit | edit source]

The vast majority of the reconsideration requests from October 2010 until April 2014 dealt with: policy formation, Applicant Guidebook development, and other issues related to the launch of New gTLD Program; and after the launch, threshold decisions regarding applications for TLD strings.

Applicant Guidebook, Policy Development, and Application Processing: 2010-2014
10-3: Michael Palage Resolution approving description of High-Security Top Level Domain program in the Applicant Guidebook No* Deny Deny No support for reconsideration based on the grounds listed in the Bylaws. BGC found that "Information that is not yet in existence cannot be considered “material information” for the purposes of the Reconsideration process.""[19]
11-1: Michael Gende Staff failure to assist Mr. Gende in obtaining zetamusic.com No* Deny Deny Failure to state a claim related to ICANN's mission.
12-1: International Olympic Committee New gTLD Committee's inaction re: advice from GNSO suggesting additional protections for Red Cross, IOC No Deny; but, suggest that the New gTLD Committee assess whether the time is now ripe to act on GNSO advice New gTLD Committee resolved to review new information since original decision
12-2: GNSO Intellectual Property Constituency Board Approval of the Registry Services Evaluation Process (RSEP) request of the registry operator for .cat, Fundació PuntCAT No Deny; but amend a preliminary "whereas" clause from the resolution to avoid confusion regarding the scope of the amendment [https://www.icann.org/resources/board-material/resolutions-2012-08-28-en#2.a Deny reconsideration, amend "whereas" clause as recommended Request for amendment was related to GDPR/WHOIS issues for a Spanish registry
13-1: Ummah Digital, Ltd. Staff rejection of Ummah's application based on Support Applicant Review Panel's Findings under the New gTLD Round No Deny; refer to SUBPRO for possible lessons learned Denied and referred to SUBPRO "ICANN’s Accountability Mechanisms are not intended for instances where a requestor: (1) is fully aware of the potential risks and defined outcomes within a process; (2) chooses to participate within that process; and (3) when they experience an unfavorable but defined outcome, seeks relief from that outcome."
13-2: Nameshop Staff rejection of Nameshop's change request, and application for financial assistance No Deny Deny
13-3: Non-Commercial Stakeholders Group Introduction of "prior offender" URLs in the Trademark Clearinghouse No Deny; but, the request raises important points wrt "policy" versus "implementation", and expanding the mechanisms of community consultation Deny, and refer issues raised to ICANN staff for inclusion in the ongoing community conversation re: policy vs. implementation
13-4: DotConnectAfrica Trust Rejection of DCA Trust's .africa application in the New gTLD Program No Deny Deny
13-5: Booking.com B.V. Placement of .hotels and .hoteis in a contention set No Deny Deny
13-6: Hotel Top Level Domain S.a.r.l. Dismissal of dotHotel's objection to Booking.com's .hotels application No Deny Deny
13-7: Dish DBS Corp Dish attempted to register .direct and DirectTV's objection was upheld No Deny Deny
13-8: Merck KGaA New gTLD Committee's recommendation that third party neutrals consider extenuating circumstances regarding missed objection deadlines No Deny Deny Merck KGaA, a German company had applied for .merck and .emerck. The American [[Merck & Co.'s objections to the two applications were ten and eleven minutes late, respectively
13-9: Amazon EU S.a.r.l. Amazon attempted to register a string that represented the Japanese translation of "online shopping." Commercial Connect objected to the application based on their application for .shop No Deny Deny Two 13-9 and 13-10 represented two different outcomes on similar facts - foreign language translations of "shopping" and their impact on .shop. The BGC recommended that a report be prepared regarding the two string confusion cases, and that neither string proceed to contracting until the NGPC had an opportunity to review.
13-10: Commercial Connect LLC The partner case to 13-9 - here Top Level Domain Holdings applied for a string representing a Chinese translation of "shop" and Commercial Connect's objection was denied No Deny Deny See above. The same concluding paragraph in both 13-9 and 13-10 states: "[T]he BGC recommended that staff provide a report to the NGPC, for delivery in 30 days, setting out options for dealing with the situation raised within this Request, namely the differing outcomes of the String Confusion Objection Dispute Resolution process in similar disputes involving Amazon’s Applied-for String and TLDH’s Applied-for String. In addition, the BGC suggested that the strings not proceed to contracting prior to staff’s report being produced and considered by the NGPC."
13-11: Non-Commercial Stakeholders Group Asking the board to review the sufficiency of the staff response to the NCSG's DIDP request regarding information related to the TMCH "Strawman" (which included the "50 prior offender" provision which was the subject of RR 13-3) and RR 13-3. No* Deny No action Under the then-current Bylaws, the BGC had the discretion to deny reconsideration requests regarding ICANN staff action or inaction without reference to the board. This request did not state "proper grounds for reconsideration" and was denied without further consideration. This is similar to the current "dismissal" powers of the BAMC.
13-12: Tencent Holdings Limited Tencent applied for 微博 and .Weibo. Sina, the mark holder for 微博, objected to both applications and the objections were sustained. No Deny Deny
13-13: Christopher Barron Rejection of GOProud's objection to Dotgay LLC's application for .gay No Deny Deny The BGC's recommendation was moot by the time the NGPC considered it, as GOProud had dissolved and reformed,[20] and Christopher Barron was not associated with the new entity, nor could he otherwise be contacted.
13-14: DERCars, LLC Google submitted objections to the three applications for .cars, but only prevailed as it related to DERCars' application. No No action - request was withdrawn It is unclear what, if any, work was done on this RR. In February 2014, DERCars became one of two applicants granted the right to appeal the inconsistent ruling.
13-15: Commercial Connect LLC Staff failure to invite Commercial Connect to begin the CPE process for .shop No* Deny No action taken As with RR 13-11, the BGC determined that Commercial Connect failed to state a claim under the rules of review, and so issued a final determination rather than a recommendation to the board.
13-16: dot Sport Limited SportAccord's objection to dot Sports' application for .sport was sustained No* Deny Denied without recommendation to the NGPC. See also RR 14-10
13-17: GCCIX, W.L.L. GCCIX applied for .gcc, which received objections from both theGAC and the Gulf Cooperation Council. The NGPC acted on the GAC advice and rejected the application No Deny Deny
13-18: ILGA ILGA's community objection to Afilias' application for .lgbt was rejected No* Deny No action taken Denied without recommendation to the NGPC
13-19: HOTREC HOTREC lost a community objection proceeding related to .hotels; the RR contends that NGPC should have stayed that proceeding when it paused consideration of several "closed generic" applications to allow time to engage with the GAC. No Deny Deny
13-20: DotSecure, Inc. DotSecure applied for .bank. The Int'l Banking Federation objected and the objection was sustained No* Deny No action taken Denied without recommendation to the NGPC: "There is no indication that ICANN violated any policy or process in accepting the determination sustaining IBF’s Objection to the Requester’s application for .BANK.
13-21: European Lotteries Requester objected to Afilias's application for .lotto, and lost No* Deny No action taken Denied without recommendation to the NGPC
12-22: DotMusic DotMusic's community objection to Amazon's .music application did not prevail No* Deny No action taken Denied without recommendation to the NGPC
13-23: Ruby Pike, LLC (Donuts) The Independent Objector prevailed in a "limited public interest" objection to Ruby Pike's application for .hospital No* Deny No action taken Denied without recommendation to the NGPC
14-1: Medistry LLC The Independent Objector submitted an objection to Medistry's application for .med. Medistry appealed on the grounds that the IO cannot object unless there is at least one public comment that opposes the application. No Reversed; Medistry's application allowed to proceed No action taken BGC issued the reversal itself
14-2: World Gold Council The WGC filed a community objection to a rival application for .gold; the objection failed because it did not represent a "clearly delineated community" No Deny No action taken
14-3: Corn Lake, LLC (Donuts) The Independent Objector submitted an objection to Corn Lake's application for .charity and succeeded No Deny No action taken
14-4: Union of Orthodox Jewish Congregations of America The Union's community objection regarding an application for .kosher was rejected No Deny No action taken The panel's decision took the applicant's Public Interest Commitments into account
14-5: Vistaprint Limited Web.com Group successfully objected to Vistaprint's .webs application on string confusion grounds No Deny No action taken
14-6: Dot Rugby Limited The International Rugby Board successfully objected to this and another application for .rugby No Deny No action taken
14-7: Asia Green IT System Ltd. Requester filed for .islam and .halal and was met with a flurry of objections, GAC advice, and other issues. The NGPC deferred action until Asia Green resolved the conflicts. Asia Green appealed that deferral. No Deny Deny
14-8: DotMusic DotMusic's community objections to a number of .music and .band applications all failed No Deny No action taken
14-9: Merck KGaA Merck KGaA submitted legal rights objections to .merck and .merckmsd No Deny No action taken
14-10: dot Sport Limited Requesting reconsideration of community objection to .sport described in RR 13-16, above, and the BGC's assessment of an undisclosed & purportedly insurmountable conflict of interest on the part of the IRP panelist No Deny Denied by resolution of the board

New gTLD Program: 2014-2016[edit | edit source]

From April 2014 to the end of 2016, the reconsideration process was used extensively by applicants to the New gTLD Program. The Community Priority Evaluation process was a frequent bone of contention, as well as various string contention sets.

New gTLD Program: 2014-2016
14-11: Commercial Connect LLC Commercial Connect's .shop application was placed "On Hold" pending multiple Accountability Mechanism proceedings No* Deny No action taken Request was late and, even if it was timely, failed to state a claim that warranted reconsideration
14-2: Tennis Australia Tennis Australia's CPE application failed No* Deny no action taken Request failed to substantiate any claim that would be subject to reconsideration
14-13: European Commission
14-14: UK
14-15 and 14-25: France
14-16 and 14-17: Spain
14-18 and 14-24: Vinicultural & Geographical Indicator Organizations
14-19 and 14-26: Italy
14-20: Portugal
14-21: Luxembourg
14-22: Switzerland
Urging reconsideration of the delegation of .wine and .vin No Deny Denied
14-23: Danielle F. Watson moviestar.photo registration failed Withdrawn by requester No action No action taken
14-27: Amazon EU S.a.r.l. Amazon's applications for .amazon as well as Chinese and Japanese translations of the word, were rejected by the NGPC on the basis of GAC advice. No Deny Denied GAC Advice from ICANN 47
14-28: DotMusic Requesting reconsideration of ICANN's acceptance of change requests from Amazon for its .music, .song, and .tunes applications after receipt of GAC advice regarding generic terms No Deny No action taken
14-29: DotKids Foundation ICANN deferred DotKids' application change request until the completion of the CPE process for .kids No Deny No action taken
14-30, 14-32, and 14-33: Dot Registry, LLC Dot Registry requested reconsideration of its failed CPE processes for .llc, .inc, and .llp No Deny Board separately initiated an assessment of its relationship with its CPE panel provider] Dot Registry ultimately withdrew all three RRs
14-31: TLDDOT GmbH TLDDOT did not prevail in a CPE for .gmbh No* Deny No action taken Requester's areguments for reconsideration were almost entirely substantive, and therefore failed to establish a claim for reconsideration
14-34: Despegar Online SRL, DotHotel, Inc., dot Hotel Limited, Fegistry, LLC, Spring McCook, LLC, and Top Level Domain Holdings Limited The six requesters were appealing Hotel Top-Level-Domain S.a.r.l.'s successful CPE for .hotel No Deny No action taken
14-35: Amazon EU S.a.r.l. Reconsideration of the staff response to Amazon's DIDP request regarding RR 14-27 No Deny No action taken "As there is no indication that ICANN violated any policy or procedure with respect to its response to the Requester’s DIDP Request, and given that portions of Request 14-35 are simply premature as ICANN has stated that it is still reviewing documents, the instant Request 14-35 should not proceed."
14-36: Asia Spa and Wellness Promotion Council (ASWPC) ICANN denied ASWPC's request to modify its application for .spa No* Deny No action taken No proper grounds for reconsideration
14-37: iRegistry Ltd. NGPC's adoption of the Name Collision Occurrence Management Framework No Deny Deny iRegistry did not prove that it was actually adversely affected by the adoption of the policy
14-38: The Business Constituency, the Registries Stakeholder Group, and the Non-Commercial Stakeholders Group Protesting the staff "imposition" of an Accountability Plan as posted, without public comment or bottom-up process Withdrawn No recommendation No action taken It appears that either this request inspired a change in process, or was overtaken by events - an additional public comment period was announced shortly after the request was filed.
14-39: Despegar Online SRL, Radix FZC, Famous Four Media Limited, Fegistry, LLC, Donuts, Inc., Minds + Machines Reconsideration of the staff response to a DIDP request regarding the .hotel CPE No* Deny No action taken No proper grounds for reconsideration
14-40: Dadotart, Inc. Dadotart did not prevail in a Community Priority Evaluation for .art No* Deny No action taken No proper grounds for reconsideration
14-41: Afilias Limited, BRS Media Inc., and Tin Dale, LLC Reconsideration of the European Broadcasting Union's succesful Community Priority Evaluation for .radio; and ICANN staff's response to a DIDP request concerning the same CPE No* Deny No action taken No proper grounds for reconsideration
14-42: Ministry of Industry, Trade, Investment and Digital Economy of the Kingdom of Morocco Handling of Morocco's objection to the .tata domain application No No recommendation No action taken The reconsideration request was deemed moot - Morocco's other efforts for relief succeeded before the RR was considered by the BGC
14-43: City of Spa ICANN decision to process applications for .spa as non-geographic name applications No* Deny No action taken No proper grounds for reconsideration
14-44: dotgay LLC dotgay did not prevail in a Community Priority Evaluation for .gay No Approve reconsideration No action taken "Accepting the Request merely allows the appointment of new CPE evaluators (and potentially new core team members) to conduct a new evaluation and issue a new report that will supersede the existing CPE Panel’s Report." (see RR 15-21)
14-45: .music LLC .music LLC did not prevail in a Community Priority Evaluation for .music No* Deny No action taken No proper grounds for reconsideration
14-46: Little Birch, LLC and Minds + Machines Group Limited Reconsideration of Big Room, LLC's successful Community Priority Evaluation for .eco No* Deny No action taken No proper grounds for reconsideration
15-1: Atgron, Inc. Atgron's Registry Services Evaluation Policy request to offer third-level domains was rejected after public comment No Deny No action taken
15-2: Big Room Inc. Requested reconsideration of ICANN's decision to launch a CEP with losing .eco applicants Withdrawn No recommendation No action taken See .eco article for history
15-3: Brice Trail, LLC (Donuts) Brice Trail's .doctor TLD was restricted to offering registration to "legitimate medical practitioners" Withdrawn No recommendation No action taken Needs more research into context/background - the decision was overturned but not via this RR
15-4: Schwarz Domains & Services GmbH & Co. KG Denial of request to change its application from .schwarzgroup to .kaufland] No* Deny No action taken No proper grounds for reconsideration
15-5: Atgron, Inc. Yes Deny No action taken "Reconsideration Request 15-5 is based on the exact same facts and circumstancesas Request 15-1, and makes no claims that the BGC failed to consider material information, orconsidered false or inaccurate material information, in deciding Request 15-1."
15-6: .Music LLC Requested reconsideration of ICANN's decision to: appove Dot Music Limited's application change request; and defer .Music LLC's change request until completion of the CPE process No* Deny No action taken No proper grounds for reconsideration
15-7: Booking.com BV and Travel Reservations SRL Requested reconsideration of the Booking.com v. ICANN IRP No Deny Denied by resolution
15-8: Atgron, Inc. Duplicate reconsideration request #3 Yes No recommendation No action taken Summarily dismissed as vexatious & a waste of ICANN resources
15-9 and 15-10: Atgron, Inc. Two more reconsideration requests, alleging "new information" that supplemented RR 15-1 No* Deny No action taken Requests are not timely; even if they were, the "new information" still does not provide grounds for reconsideration
15-11: Motion Picture Domain Registry Pty Ltd MPDR submitted a list of two-letter second level domains for approval for release - ICANN approved all except those that were objected to during public comment No Deny No action taken *Most objections were related to confusion with ccTLDs.
*"ICANN’s decision to withhold all objected-to two-letter labels pending the development of this evaluation process does not violate any established policy or procedure, because ICANN adhered to the Process in evaluating the Authorization Request and no other procedure has been finalized yet. As such, Request 15-11 is denied. The BGC will, however, monitor the development of the criteria and process for evaluating objections to the release of certain two-letter labels, and urge staff to proceed as expeditiously as practicable."
15-12: E-Flux.art, LLC Request to change its .art application from a community designation to a standard Withdrawn No recommendation No action taken The Applicant Guidebook specifically stated that applicants cannot change to or from a community designation once application is submitted.
15-13: Commercial Connect LLC Commercial Connect failed its CPE for .shop; requested reconsideration No Deny Denied by resolution
15-14: Foggy Sunset, LLC (Donuts) Requesting reconsideration of Asia Spa & Wellness Promotion Council's successful CPE for .spa No* Deny No action taken No proper grounds for reconsideration
15-15: Centre for Internet & Society Requested reconsideration of staff responses to two DIDP requests: documents pertaining to ICANN's "efforts to implement NETmundial Principles" into its policies; and "raw data" for ICANN's income statements from 1999-2011 No* Deny No action taken "There is no indication that: (i) ICANN staff violated established policy or procedure by determining that certain documents sought in the Second Financial Data DIDP Request were subject to DIDP Defined Conditions for Nondisclosure; or (ii) ICANN staff violated established policy or procedure by determining that certain documents sought in the Second NETmundial DIDP Request fell outside the scope of the DIDP."
15-16: CPA Australia Ltd Requester did not prevail in its Community Priority Evaluation for .cpa No* Deny No proper grounds for reconsideration
15-17: American Institute of Certified Public Accountants (AICPA) Requester did not prevail in its Community Priority Evaluation for .cpa No* Deny No proper grounds for reconsideration
15-18: Ron Andruff Reconsideration of the BGC's decision not to recommend Mr. Andruff for 2016 NomCom chair and the Board's apppointment of Stephane Van Gelder as 2016 NomCom chair. No Deny Denied by resolution of the Board No proper grounds for reconsideration; however, BGC thanked Mr. Andruff for his commitment to the ICANN Community and suggested that he be given an opportunity to address the Board regarding his request. The Board followed that suggestion.[21]
15-19: Business Constituency and Non-Commercial Stakeholders Group; and 15-20: Internet Commerce Association Reconsideration of the Board's approval of renewals of registry agreements for legacy TLDs .cat, .pro, and .travel No Deny Denied by resolution of the Board "The Requesters claim, without support, that ICANN staff unilaterally imposed the New gTLD Registry Agreement as a starting point for the Renewed Registry Agreements and, therefore, 'transform[ed] the PDDRP and URS into de facto Consensus Policies without following the procedures laid out in ICANN's Bylaws for their creation.' Contrary to what the Requesters claim, while the registry operators had a presumptive right of renewal under the terms of their existing legacy registry agreement, they chose to re-negotiate and renew their agreements based upon the New gTLD Registry Agreement terms."[22]
15-21: dotgay LLC dotgay did not prevail in its second Community Priority Evaluation for .gay No* Deny No action taken No proper grounds for reconsideration
15-22: Centre for Internet & Society Staff responses to two DIDP requests regarding ICANN Contractual Compliance activities No* Deny No action taken No proper grounds for reconsideration
16-1 and 16-2: Commercial Connect LLC Staff determinations regarding Commercial Connect's efforts to initiate a CEP around its .shop application, and to prevent an auction for .shop No Deny No action taken "The Requester’s claims are unsupported and are the latest in a long line of frivolous abuses of ICANN’s accountability mechanisms by the Requester. The Requester’s renewed attempt to challenge the CPE Report is improper and time-barred. The Requester has not raised any new arguments or evidence since its previous challenge to the CPE report in Request 15-13, which was denied. As to the other issues raised by the Requester, the facts demonstrate that ICANN staff adhered to established policy and procedure with respect to the Auction, took unprecedented steps to keep the Requester apprised of, and involved in, the Auction, and properly responded to the Requester’s many incomplete, aborted, and/or improper attempts to invoke ICANN’s accountability mechanisms. The BGC therefore denies Requests 16-1 and 16-2."
16-3: dotgay LLC Objecting to the Second CPE assessment for .gay (see RR 15-21) and taking issue with alleged process failures during the CPE No Deny No action taken dotgay LLC withdrew the request a month after the BAMC's recommendation was published
16-4: Roman Belichenko Requester's domain, magic-pills.com, was suspended by GoDaddy for selling pharmeceuticals and controlled substances without a prescription and/or directing traffic to sites that did. After suspension, GoDaddy refused a transfer request from requester, and requester sought reconsideration of that decision. No* Deny No action taken No proper grounds for reconsideration
16-5: DotMusic Limited DotMusic did not prevail in its Community Priority Evaluation process for .music No Deny Denied by resolution
16-6: DotKids Foundation DotKids did not prevail in its CPE for .kids No* Deny No action taken No proper grounds for reconsideration
16-7: DotMusic Limited Requesting reconsideration of staff response to DotMusic's DIDP request regarding the determination of DotMusic's Community Priority Evaluation of .music No* Deny No action taken No proper grounds for reconsideration
16-8: CPA Australia Ltd. CPA Australia did not prevail in its Community Priority Evaluation for .cpa No Deny No action taken RR was withdrawn after the BAMC's recommendation was published
16-9: Ruby Glen, LLC and Radix FZC Urgent reconsideration request regarding ICANN staff's refusal to halt the .web auction based on leadership changes at another applicant & auction participant No* Deny No action taken No proper grounds for reconsideration
16-10: Registries Stakeholder Group ICANN policy implementation guidance to registries that "improperly conflated" a Consistent Labeling and Display (CL&D) Policy with RDAP Withdrawn No recommendation No action taken Withdrawn by RySG prior to any action
16-11: Travel Reservations SRL; Spring McCook, LLC; Minds + Machines Group Limited; Famous Four Media Limited; dot Hotel Limited; Radix FCZ; dot Hotel Inc.; and Fegistry, LLC Board acceptance of Hotel Top-Level Domain S.a.r.l.'s successful Community Priority Evaluation for .hotel and instruction to staff to move forward was discriminatory to requesters (who were the other applicants), and invalid for other reasons No Deny Denied by resolution
16-12: Merck KGaA Requester did not prevail in its Community Priority Evaluation for .merck No Deny Denied by resolution

Reconsideration Stalwarts & Back to Business: 2016-Present[edit | edit source]

By late 2016, all but a few applicants to the New gTLD Program had acknowledged defeat or were engaged in other processes to resolve their disputes with ICANN and other applicants. Those still persisting with reconsideration requests were increasingly focused on staff responses to Documentary Information Disclosure Policy requests surrounding the disposition of their various applications. The reconsideration process returned to a mixture of consumer complaints and objections to policy or process.

In 2020 and 2021, the BAMC became more comfortable with summary dismissal of requests that were either outside the scope of the Bylaws, or failed to state a claim.

Lingering New gTLD Program Issues and Other Matters: 2016-Present
16-13: Merck KGaA Merck's application for merck.pharmacy during .pharmacy's sunrise period was rejected (the name was given to the U.S.-based Merck & Co.) No* Deny No action taken No proper grounds for reconsideration. "In sum, ICANN correctly determined that the Registry had complied with Spec 11. As ICANN informed the Requester, registry operators may set their own criteria for resolving disputes in the circumstance where two legitimate trademark holders apply for the same second level domain."
16-14: Fraser Lee Contractual Compliance closed Lee's complaint regarding ripoffreport.com, finding no violation of the Registrar Accreditation Agreement Yes Deny No action taken Summarily denied for failure to state a claim
17-1: Russ Smith Contractual Compliance closed Smith's two WHOIS SLA complaints concerning historical ownership data for his domain directorschoice.com No Deny Denied by resolution
17-2: DotMusic Limited Staff response to DotMusic's DIDP request regarding ICANN's Community Priority Evaluation process review No Deny Denied by resolution
17-3: dotgay LLC Staff response to dotgay's DIDP request regarding ICANN's Community Priority Evaluation process review No Deny Denied by resolution
17-4: DotMusic Limited and dotgay LLC Staff response to requesters' joint DIDP request regarding ICANN's Community Priority Evaluation process review No Deny Denied by resolution
17-5: DotKids Foundation Objecting to ICANN Staff taking DotKids' Community Priority Evaluation for .kids off hold prior to the conclusion of the CPE process review No Deny Denied by resolution
18-1: DotMusic Limited Another DIDP request (see 17-2, 17-4) related to ICANN's Community Priority Evaluation process review No Deny Denied by resolution
18-2: dotgay LLC Another DIDP request (see 17-3, 17-4) related to ICANN's Community Priority Evaluation process review No Deny Denied by Resolution
18-3: Astutium Ltd Termination of Astutium's Registrar Accreditation Agreement No Deny Denied by resolution
18-4: dotgay LLC Board resolutions accepting the final report of the CPE process review and concluding the review No Deny Denied by resolution
18-5: DotMusic Limited Board resolutions accepting the final report of the CPE process review and concluding the review No Deny Denied by resolution
18-6: Travel Reservations SRL; Minds + Machines Group Limited; Radix FZC; dot Hotel Inc.; Fegistry LLC Board resolutions accepting the final report of the CPE process review and concluding the review No Deny Denied by resolution
18-7: Afilias Domains No. 3 Limited Staff response to requester's DIDP request regarding the resolution of the .web contention set Yes Deny No action taken Summarily dismissed for failure to state a claim
18-8: Afilias Domains No. 3 Ltd Staff response to requester's second DIDP request regarding the resolution of the .web contention set No Deny Denied by resolution
18-9: DotKids Foundation Staff response to DotKid's request for financial support to engage in the .kids string contention process No Deny Denied by resolution
18-10: The Amazon Cooperation Treaty Organization Board decision to remove the "Will not proceed" label and instruct staff to process applications for .amazon No Deny; however, notes that close coordination is required (see Notes) Denied by resolution On the recommendation of the BAMC, the Board approved two additional resolutions:
Resolved (2019.01.16.03), the Board hereby reiterates that Resolution 2018.10.25.18 was taken with the clear intention to grant the President and CEO the authority to progress the facilitation process between the ACTO member states and the Amazon corporation with the goal of helping the involved parties reach a mutually agreed solution, but in the event they are unable to do so, the Board will make a decision at ICANN 64 on the next steps regarding the potential delegation of .AMAZON and related top-level domains.
Resolved (2019.01.16.04), the Board encourages a high level of communication between the President and CEO and the relevant stakeholders, including the representatives of the Amazonian countries and the Amazon corporation, between now and ICANN 64, and directs the President and CEO to provide the Board with updates on the facilitation process in anticipation of revisiting the status of the .AMAZON applications at its meeting at ICANN64.[23]
- 19-1: Colombian Government Board's decisions to remove the "Will Not Proceed" label from .amazon applications and instruct staff to move forward with processing No Deny Denied by resolution
19-2: Namecheap, Inc. Board's renewal of the .info and .org Registry Agreements with Afilias and Public Interest Registry, respectively, specifically as the effect of those renewals "eliminated 'the historic price caps' on registration fees" for the two domains. No No recommendation (see Notes) Denied by resolution The majority of the members of the BAMC recused themselves from voting on RR 19-2 because of potential or perceived conflicts, or out of an abundance of caution regarding the appearance of impropriety.[24]
19-3: Electronic Frontier Foundation Board's renewal of .org Registry Agreement with Public Interest Registry, and specifically the inclusion of Uniform Rapid Suspension procedures in the amended RA. No No recommendation (see Notes) Denied by resolution As with RR 19-2, the majority of the BAMC recused themselves from voting on this decision.
19-4: Merck KGaA and Merck Registry Holdings, Inc. ICANN's denial of a second postponement of the auction for .merck No Deny, with provisos Denied, incorporating the BAMC's recommendations & provisos The BAMC noted that, between the first postponement, the processing of RR 19-4, and the subseqent delay before board action, the delay would have lasted nearly the amount of time originally requested by the parties.
"If the Requestors jointly declare they have made progress since filing Request 19-4 and that they are very close to private resolution, the BAMC recommends that the Board ask ICANN org to consider providing the Requesters with some form of discretionary relief that could allow them to finalize a settlement."
20-1: Namecheap, Inc. ICANN's alleged lack of transparency and failure to follow established procedure in considering Public Interest Registry's change of control request No Deny Denied by resolution
20-2: Emily Rose Trust Requesting reconsideration of a UDRP decision Yes Deny Summarily dismissed for failure to state a claim
20-3: Silver A Marketing Domain renewal issues with GoDaddy Yes Deny Summarily dismissed for failure to state a claim
21-1: Dot Hotel Limited and Domain Venture Partners PCC Limited Approval of Afilias' change of control request, pertaining to its merger with Donuts Yes Deny Summarily dismissed for failure to state a claim
21-2: Pooja Gupta Requesting reconsideration of a registration issue with Net4.in Yes Deny Summarily dismissed for failure to state a claim
21-3: Dot Hip Hop, LLC Staff inaction regarding the assignment of .hiphop to requester after a purchase transaction with Uniregistry No Withdrawn by Dot Hip Hop by letter on January 13.[25] See .hiphop for more information

References[edit | edit source]

  1. ICANN.org - Reconsideration
  2. Article 4.2(c), ICANN Bylaws, as amended November 28, 2019
  3. 3.0 3.1 Annex D to the ICANN Bylaws, as amended November 28, 2019
  4. Article 4.2(b), ICANN Bylaws, as amended November 28, 2019
  5. New gTLD Program Applicant Guidebook - Module 6: Terms and Conditions (PDF)
  6. Article 4.2(d), ICANN Bylaws, as amended November 28, 2019
  7. Articles 4.2(e) and (k), ICANN Bylaws, as amended November 28, 2019
  8. see, e.g., the Accountability Mechanisms of the Bylaws in effect as amended in July 2014
  9. Article 4.2(k), ICANN Bylaws, as amended November 28, 2019
  10. See, e.g., Request 16.2 - Commercial Connect LLC, February 25, 2016, where despite noting Commercial Connect's abuse of "all of ICANN's Accountability Mechanisms," the BAMC nonetheless provides an analysis on the sufficiency of the request.
  11. Article 4.2(l), ICANN Bylaws, as amended November 28, 2019
  12. Articles 4.2(m)-(o), ICANN Bylaws, as amended November 28, 2019
  13. Article 4.2(p), ICANN Bylaws, as amended November 28, 2019
  14. Article 4.2(r), ICANN Bylaws, as amended November 28, 2019
  15. Article 4.2(s), ICANN Bylaws, as amended November 28, 2019
  16. See Reconsideration Request 21-3, where the BAMC denied Dot Hip Hop LLC's request for urgent reconsideration of inaction by ICANN staff
  17. ICANN Staff Responses to ATRT1 Team, October 1, 2010 (PDF)
  18. BGC Recommendation on RR 10-2, December 9, 2010
  19. BGC Recommendation on RR 10-3, December 4, 2010
  20. Daily Beast - Inside the Implosion of GOProud, June 6, 2014
  21. Board Meeting Minutes, October 21, 2015
  22. Resolution of the Board, February 3, 2016
  23. Resolution of the Board, January 16, 2019
  24. Resolution of the Board, re: Proposed Determination of Reconsideration Request 19-2, November 3, 2019
  25. Jeff Neumann letter to ICANN, January 13, 2022