Summary

  • The Community Priority Evaluation report dated 6 October 2014 awarded Big Room 14 points out of 16, exactly the passing threshold set by the 2012 Applicant Guidebook. Because all four .ECO applications were in direct contention, ICANN’s acceptance of the passing result allowed Big Room to proceed and removed the three standard applications from the route to the string.
  • The evaluator did not find that every environmental organisation, business, government body and professional called itself part of a single “.ECO community”. It assessed the community that Big Room had defined through memberships, accreditation, certification, environmental missions and professional status, and found that definition sufficiently delineated, organised, longstanding and extensive under the published criteria.
  • The score depended on classification as much as on evidence. Big Room received full points for community establishment and registration policies, three of four for nexus and uniqueness, and three of four for endorsement. The panel withheld the second support point because it found neither documented authority in Big Room nor a single institution recognised as representative of the whole defined community. It nevertheless awarded the maximum opposition score after classifying the opposition submitted as irrelevant under the CPE rules.
  • Reconsideration Request 14-46 and the later Independent Review Process declaration did not provide a general appeal from the merits score. The reviews tested whether ICANN and its provider had followed applicable policy and whether the Board and its committee had acted consistently with ICANN’s governing documents. They did not authorise a fresh CPE calculation.
  • Priority was only the first gate. The .ECO registry agreement dated 8 July 2016 designated Big Room as operator subject to the remaining requirements for delegation and root-zone entry. The IANA delegation report dated 25 August 2016 then recorded completion of programme, identity, contact and technical checks. Neither document retrospectively validated the 2014 judgement about the environmental community; each exercised a different authority.

The point that resolved a four-way contest

The decisive .ECO document was nine pages long. Its first page carried the result: 14 points, “prevailed”, and a minimum passing score of 14. The application passed at the threshold. Any one-point reduction in the published calculation would have produced 13 and failed.

That arithmetic had an exclusionary consequence because of the rule ICANN had adopted before any .ECO application was evaluated. Under Module 4 of the Applicant Guidebook, a community-based applicant could elect Community Priority Evaluation. If it reached at least 14 points, it could proceed and directly contending standard applications were eliminated. If no community applicant qualified, the contention set would move to auction unless the applicants resolved it by another permitted means. The Guidebook expressly acknowledged the severity of the preference: a qualifying community application displaced standard applications regardless of how well qualified those applications might otherwise be.

The report therefore performed two functions. Analytically, the Economist Intelligence Unit panel scored Big Room against four published criteria: community establishment, nexus between the string and the community, registration policies, and community endorsement. Administratively, once ICANN accepted the outcome and updated the application statuses, that score resolved which applicant could continue towards contracting. The evaluator did not choose a registry operator by comparing four business plans. It decided whether one application satisfied a priority rule whose consequence had already been fixed by ICANN.

The distinction matters because the result is easily overstated. CPE did not confer exclusivity over the word “eco” outside the New gTLD contention process. The panel did not decide who represented environmentalism in law, politics or public debate. It answered a narrower question created by the programme: whether the constituency and commitments described in Big Room’s application met the CPE criteria strongly enough to displace directly contending standard applications for the same string.

The report itself preserved that boundary. Its disclaimer said that the CPE result did not necessarily determine the application’s final outcome and did not amend or waive the Applicant Guidebook or any registry agreement. Contracting, testing, delegation eligibility and root-zone implementation remained to be completed. Within the contention set, however, the score was immediately consequential. The Board Governance Committee’s determination on Reconsideration Request 14-46 stated that the contention set had been resolved and that only Big Room’s application would proceed.

A rule built to make one expert assessment dispositive

CPE was designed as an expert evaluation, not as an adversarial trial among every applicant for a string. The Guidebook required applicants to classify themselves at filing as community-based or standard. Only a community-based applicant could enter CPE. Standard applicants in the same contention set did not participate as candidates, did not receive a comparative score and could not demand that the panel choose the technically or commercially strongest registry proposal.

The asymmetry was deliberate. A community applicant sought a preference unavailable to a standard applicant, but it began at zero and faced a high threshold. The Guidebook described the scoring framework as a way to avoid two errors: priority for a community assembled merely to capture a desirable generic word, and denial of priority to a genuinely qualified community application. Those risks could not be resolved by counting endorsements alone.

The evaluator had to decide whether the stated constituency had more cohesion than a shared interest, whether the string identified it without substantial overreach, whether proposed restrictions were credible, and whether support or opposition came from institutions relevant to the community implicated by the application.

ICANN selected the Economist Intelligence Unit as the CPE provider and supplied the governing framework. The published CPE panel process described seven people participating in each assessment: two independent evaluators and a five-person core team. The two evaluators worked separately; one verified letters of support and opposition; a project coordinator reviewed completeness and consistency; disagreements could be mediated; and the core team reviewed the result before it went to ICANN. Application materials, public comments, correspondence and independent research could all enter the assessment.

Those controls were real, but they remained internal to the provider. They were intended to improve the first decision, not to create an external tribunal before which a losing applicant could cross-examine the community definition or obtain de novo rescoring. ICANN retained a different set of powers: it wrote and interpreted the programme framework, selected and contracted with the provider, accepted and administered the result, controlled application holds, entered the registry agreement and advanced the surviving application towards delegation. Outsourcing the score divided labour.

It did not transfer the entire allocation power to the evaluator.

The .ECO CPE status entry records that Big Room was invited on 12 March 2014 and that evaluation was completed on 7 October 2014. The report itself is dated 6 October. Keeping those dates separate avoids a small but revealing conflation: the provider completed its judgement, and ICANN then published and operationalised the result within the programme.

Four applications, one community-priority candidate

The contention set contained four applications for the identical string. Big Room Inc. filed the sole community-based application, application 1-912-59314. Little Birch, Top Level Domain Holdings and Planet Dot Eco filed standard applications. Minds + Machines Group joined Little Birch in the reconsideration proceeding; the BGC recorded that it was a wholly owned subsidiary of Top Level Domain Holdings, the named applicant on the relevant application.

This configuration defined both the power and the procedural weakness of CPE. Big Room alone was scored. The standard applicants had a direct economic interest in the result because a pass would end their route to .ECO, yet the evaluation was not a four-party merits hearing. They could contribute material through the public application record, comments, correspondence and opposition. They could later invoke ICANN accountability mechanisms if they alleged a qualifying procedural or institutional failure. They had no entitlement to present an alternative registry proposal as a competing merits case before the CPE panel.

That is not the same as saying that the standard applicants were voiceless. Their submissions could affect the evidence available, especially under the endorsement criterion. But participation in the record did not give them control over the score. The panel decided which material was relevant, how a group should be classified, whether a claimed affiliation was verifiable and whether the application’s definition met the Guidebook. ICANN then decided what administrative effect to give the report.

The procedural design becomes harder to defend as the consequence becomes more severe. Expert evaluation can be faster and more consistent than litigation. Yet when a one-point judgement removes three otherwise surviving applications from a scarce-resource allocation, the quality of the reasons and the availability of a remedy matter more than they would in an advisory assessment. .ECO exposed that tension without resolving it.

The community was the one stated in the application

The panel’s first and most consequential move was to identify the object it was evaluating. Criterion 1 did not ask whether all people concerned with ecology formed a single, universally acknowledged body. The Guidebook and the CPE Guidelines directed the evaluator to examine the community explicitly identified and defined in the application. The implicit reach of the string would be considered later under nexus.

Big Room made a broad constituency administratively legible by using formal affiliations and statuses. The CPE report described four categories. Environmental non-profits could qualify through UN accreditation, IUCN membership, or legal status paired with a documented environmental mission. Businesses could qualify through membership in environmental organisations, participation in the UN Global Compact, recognised environmental certification, or reporting to a sustainability standard. Government bodies needed environmental responsibilities. Individuals could qualify through environmental-organisation membership, academic status or professional certification.

These were not naturally occurring borders that the evaluator merely discovered. They were the applicant’s proposed boundaries. The panel’s institutional act was to accept them as clear, formal and verifiable enough to satisfy CPE. It awarded the maximum two points for delineation, finding a straightforward membership definition and sufficient awareness and recognition among members of the community as defined.

That finding should not be enlarged beyond its text. The report did not establish that every member of every qualifying organisation understood themselves to belong to one global constituency represented by Big Room. It reasoned that the categories shared demonstrable involvement in environmental activity, active commitments and overlapping goals. It pointed to cooperation among non-profits, businesses, governments and individuals through organisations and initiatives such as Conservation International, Greenpeace, IUCN and the UN Global Compact. That evidence supported the panel’s judgement under the CPE criteria.

It did not settle the broader sociological question of whether “the environmental community” has one boundary or one political centre.

The distinction between a community in social life and a community as represented in an application did much of the institutional work. Environmentalism contains conflict over methods, standards, industry participation, market claims, conservation priorities and who may speak for whom. Big Room translated that contested field into membership proofs. The provider then assessed whether those proofs formed a coherent category. CPE consequently favoured constituencies that could be expressed through records an evaluator could verify: membership lists, accreditation, certification, legal purpose, reporting systems and professional status.

That evidentiary form has distributional consequences. Informal movements can be cohesive but difficult to document. Large networks can be internally divided yet easy to evidence because their ties are formal. The .ECO panel did not require Big Room to eliminate disagreement inside the proposed constituency. It required a boundary, evidence of organisation and a basis for treating the members as more than people with a common interest.

Historical depth by aggregation

Big Room also received full credit for organisation and pre-existence. The panel identified institutions mainly dedicated to environmental work and documented activity connecting categories in the defined community. For pre-existence, it relied on organisations and activity that long pre-dated the September 2007 policy cut-off: IUCN’s establishment in 1948, Greenpeace in 1971, the United Nations Environment Programme in 1972 and the UN Global Compact in 2000 were among the examples discussed.

Big Room itself did not need to be the ancient representative body of a pre-existing community. The relevant historical object was the community as defined and the institutions used to demonstrate it. By making those organisations constituent evidence, the application could connect a 2012 registry proposal to decades of prior activity. The panel treated the age of the constituent institutions as evidence that the claimed community had not been invented for the application round.

The extension score used the same logic. The report repeated figures supplied by the applicant: more than 40,000 non-profit organisations, more than 148,000 businesses, at least 193 governmental bodies and more than 18 million individuals. Those figures should not be read as an independently audited census of people who had authorised Big Room to act. The report explicitly attributed them to the applicant and used them as evidence of considerable size and geographical reach. It then found longevity in the continuing nature of environmental work and the institutions pursuing it.

This was historical depth by aggregation. Organisations founded at different times, for different purposes and with different constituencies were combined into one application-defined field. The CPE question was not whether that aggregation produced a unitary political body. It was whether the resulting category was sufficiently delineated, organised, pre-existing, large and durable to receive four points. The panel said yes.

“Eco” identified the community without naming it

The nexus criterion exposed the semantic tension in that construction. Big Room received two of three points for nexus and one of one for uniqueness. The panel found that “eco” was not the established name of the community and not a recognised short form or abbreviation of that name. Environmental organisations commonly described their field with “environment”, “ecology”, “sustainability” and related terms rather than using “eco” alone as the formal name of a community.

A full nexus score was therefore unavailable. The panel nevertheless found that the string identified the community. “Eco” was commonly associated with environmental protection, environmentally responsible practices, products and services. In the panel’s view, that association closely described the defined constituency without extending substantially beyond it.

The report did not ignore all overreach. It noted that the business category included entities participating in the UN Global Compact or using certified environmental-management systems that the public might not automatically call “eco”. Intel, Vale and Unilever appeared as examples. The panel treated those businesses as only part of one category and concluded that the public would generally associate the string with the broader community described in the application. The overreach was acknowledged but judged not substantial.

Uniqueness then received the maximum point. The evaluator treated other ordinary uses of “eco” as expressions of the same environmental concept rather than as a different significant meaning. The word could therefore identify a community it did not formally name and still be unique for CPE purposes. The conclusions were not logically identical: nexus asked whether the string closely described the community without substantial overreach; uniqueness asked whether it carried another significant public meaning beyond that environmental identification.

This semantic hinge carried large consequences. A descriptive word did not need to be the community’s institutional name. It needed to be close enough to the applicant-defined constituency and not significantly meaningful elsewhere. That enabled a broad environmental identifier to support priority even though many included actors did not call themselves “eco” and no single organisation owned the term.

Little Birch and Minds + Machines attacked precisely this judgement in their 22 October 2014 reconsideration request. They argued that “eco” was broader than the proposed community, that some qualifying businesses would not ordinarily be regarded as environmental actors and that the definition overreached. These were the requesters’ allegations, not findings adopted by ICANN. Their procedural importance lies elsewhere: they disputed the evaluator’s application of the criterion, not its failure to mention the criterion. That classification later placed the challenge on the merits side of the reconsideration boundary.

Registration promises scored before operation began

Big Room received all four points for registration policies. The panel found that eligibility was limited to members of the defined community; name-selection rules served the community purpose; content and use rules required registrants to create an ECO Profile; and the proposed enforcement system combined complaint handling, possible referral to dispute resolution and an opportunity for a registrant to seek the opinion of an independent arbiter approved by the registry.

The profile proposal connected the claimed community to the future operation of the namespace. Registrants would disclose memberships, accreditation, certification, reporting and environmental commitments. Eligibility would not depend merely on choosing a green-sounding domain name. The applicant proposed to require a qualifying status and a public profile through which claimed credentials and commitments could be presented.

At the CPE stage these were promises, not evidence from a functioning registry. The panel evaluated the specificity and coherence of a proposed governance system. A maximum score did not prove that future eligibility checks would be uniform, that every profile would be accurate, that every complaint would receive a reasoned outcome or that a registry-approved arbiter would be independent in every practical sense. It established that the application contained policies satisfying the Guidebook’s ex ante test.

This separation between design and enforcement is essential. The policies helped Big Room obtain priority before they were contractual obligations. After ICANN and Big Room entered the registry agreement, section 2.19 and Specification 12 carried defined community commitments into the contract. CPE assessed whether the proposed restrictions deserved points; the agreement later determined which duties bound the registry, which compliance and dispute routes applied, and what contractual remedies were available.

Support was not authority to represent

The panel’s support score is the strongest evidence against the claim that CPE simply ratified Big Room’s account of universal environmental representation. Big Room received one of two points. The evaluator found substantial, verified support from relevant organisations, but it did not find that Big Room was itself a recognised community institution, had documented authority to represent the community, or possessed support from a single institution clearly recognised by the whole defined community as its representative.

The report distinguished dedication from representative authority. IUCN and the UN Global Compact could help demonstrate that institutions were mainly dedicated to parts of the environmental field. That did not mean the community reciprocally recognised either institution as authorised to speak for all categories in Big Room’s definition. The breadth that helped establish size and organisation made central representation harder to prove.

Three forms of power must be kept separate. Endorsement shows approval or participation. Recognition concerns whether a constituency treats an institution as representative. Control determines who can make the binding decision. Big Room had extensive support, but the CPE panel did not infer a comprehensive mandate from that support. Environmental organisations did not set the scoring criteria, appoint the evaluators, accept the result, sign the registry agreement on ICANN’s behalf or authorise the root-zone change.

The one-point support score therefore limits what the 14-point result can bear. The panel found enough relevant backing for partial credit. It did not declare Big Room the political representative of environmentalism. What Big Room secured was priority under ICANN’s application framework, followed later by contractual status as registry operator.

Opposition mattered through classification, not vote counting

The maximum opposition score preserved the pass. The panel acknowledged that letters of opposition had been submitted, but awarded two points because it treated them as irrelevant under the CPE rules. The report and the later BGC determination described the letters as coming from individuals or groups of negligible size, or from communities outside the application that had no association with the applied-for string.

The Applicant Guidebook and CPE Guidelines did not establish a plebiscite. The evaluator had to consider the size of an opposing group, the reasons for its opposition and whether it belonged to a community explicitly or implicitly addressed by the application. Public participation supplied evidence. It did not give each letter equal weight or each correspondent a vote over the score.

The arithmetic demonstrates why classification mattered. Big Room’s four main scores were 4, 3, 4 and 3. Within endorsement, it received one point for support and two for opposition. If the opposition sub-score had been one rather than two, the total would have been 13 and the application would not have crossed the threshold. That is a mathematical consequence of the published score, not a conclusion that any particular objector was necessarily entitled to be treated as a relevant, non-negligible group.

The requesters argued that the report did not identify which letters it had assessed or explain the classification applied to each. In their view, that omission made the two-point result impossible to test. The BGC determination answered at the level of procedure. It found that the panel had stated the governing test, answered the mandatory questions and was not subject to a rule requiring every objector to be named in the report. It also noted that opposition material was publicly available in application comments and ICANN correspondence.

Both positions describe different dimensions of the record. Inputs may be publicly accessible while the decisive inference remains hard to audit. A reader could find letters without knowing precisely which evaluator treated which group as negligible, which community was deemed outside the application’s reach or how a borderline classification was resolved. Transparency of submissions did not itself create accountability for the judgement that converted those submissions into two points.

Reconsideration opened a door that did not lead to rescoring

Little Birch and Minds + Machines filed Reconsideration Request 14-46 on 22 October 2014. They asked ICANN not to award a passing score, to reverse the “Will Not Proceed” consequences for the competing applications and to restore the contention set. Little Birch also filed a Documentary Information Disclosure Policy request for CPE-related records.

They were directly affected and were permitted to invoke reconsideration. Access to the mechanism, however, did not determine the standard of review or the available remedy. Under the BGC’s reading of the then-applicable Bylaws, a third-party panel determination could be challenged where the provider failed to follow established policy or procedure, or where ICANN staff failed to follow policy or procedure in accepting the result. Reconsideration was not a general substantive review of CPE reports.

The 18 November 2014 determination applied that boundary claim by claim. The requesters said Big Room had described a common interest rather than a cohesive community. The BGC found that the panel had identified and applied the relevant community-establishment test; the requesters were disputing the conclusion. They said “eco” had broader meanings and substantially overreached. The BGC again treated the argument as disagreement with the panel’s analysis. They said the opposition treatment lacked sufficient detail. The BGC found no rule requiring the report to identify each objector and no failure to answer the mandatory CPE questions.

The disclosure process did not produce a merits rehearing. According to the determination, ICANN responded on 31 October with links to public material and said other responsive documents were either not held or subject to non-disclosure conditions. ICANN invited supplemental submissions by 11 November; none was filed by that date. The BGC denied reconsideration and pointed to the Ombudsman if the requesters believed the process had been unfair. It did not identify the Ombudsman route as an appellate power capable of recalculating the score.

Because the request concerned staff action, the BGC treated its determination as final under the Bylaws then in force, without further Board consideration. The practical result was not that the CPE judgement became true beyond dispute. It became durable inside an accountability architecture that separated process error from merits disagreement and placed the .ECO arguments on the latter side.

This is the difference between review access and an enforceable remedy. The requesters filed, received a public determination and obtained reasons. But the questions capable of changing the result—whether the stated community was too broad, whether “eco” substantially overreached and whether particular opposition should have counted—were not open for fresh adjudication merely because another answer was plausible.

Visibility without ordinary merits accountability

The .ECO decision was not secret. The application, criteria, guidelines, public comments, CPE report and reconsideration determination were published. The report supplied a score for each criterion and a narrative rationale. Losing applicants could identify the precise points they contested.

Publication and accountability nevertheless do different work. Transparency reveals a decision and some of the evidence around it. Accountability requires an authority with power to test the contested inference against a standard and grant a remedy when the inference fails. In .ECO, no ordinary appellate body stood ready to decide whether the community was excessively delineated, whether “eco” overreached or whether a named opponent should have reduced the score.

The provider’s internal quality controls acted before publication. The BGC could address failure to follow established policy or procedure. The IRP could test whether Board action complied with ICANN’s Articles and Bylaws. None was designed as a general second CPE panel. That design protected finality and limited the ability of disappointed competitors to turn every evaluation into another full hearing. It also concentrated legitimacy in the first evaluator’s reasons, especially where one point determined whether three other applications survived.

The .ECO case therefore presents a system with considerable visibility but narrow correctability. The record allowed observers to understand how the score was assembled. The available mechanisms did not guarantee a decision-maker empowered to revisit the merits-sensitive classifications that assembled it.

The winner did not control the timetable

CPE priority did not give Big Room command over the next stage. On 20 February 2015, Big Room filed Reconsideration Request 15-2, challenging what it described as ICANN staff’s failure to end a Cooperative Engagement Process connected to the losing applicants’ dispute. Big Room said the CEP had begun on 3 December 2014, that its application was on hold and that the process had lasted more than 70 days—over five times the expected period.

Those were Big Room’s allegations, not findings that the CEP was unlawful or abusive. Their evidentiary value is narrower. They show that a successful CPE applicant did not control application holds, accountability scheduling or the transition to contracting. ICANN controlled whether the application remained paused while a challenge developed.

Big Room asked ICANN to terminate the CEP, reject any later IRP and remove the hold so the application could proceed through contracting, testing and delegation. The request did not produce a published determination on the requested relief. ICANN’s 2015 annual report on accountability mechanisms records that Big Room withdrew Request 15-2. The underlying dispute continued into independent review.

The episode prevents a simple account in which community priority immediately delivered operational control. It also exposes a genuine design conflict. Review must be capable of stopping an erroneous exclusion before reliance hardens through contract and delegation. Yet delay itself can alter competitive value, allowing a challenger to impose costs even when the eventual review standard is narrow. Finality and accountability are therefore not abstract opposites; they allocate time, bargaining power and launch risk among applicants.

Independent review criticised the architecture but left .ECO intact

The official chronology contains a small date discrepancy. ICANN’s response to the .ECO claimants says their Independent Review Process request was submitted on 13 March 2015, while the final declaration states 15 March. On 12 May 2015, the .ECO proceeding was consolidated with the separate .HOTEL dispute; the final declaration was issued on 12 February 2016.

The IRP panel was not a de novo CPE evaluator. Under the then-applicable Bylaws, it examined whether ICANN’s Board, including the Board Governance Committee, had acted consistently with ICANN’s Articles and Bylaws. For .ECO, that meant reviewing the BGC’s treatment of Reconsideration Request 14-46 and the institutional conduct surrounding it, not deciding from the beginning how many points Big Room deserved.

The panel did not reduce the review to mechanical box-ticking. It treated the BGC’s task as requiring attention to how the provider had applied the published policy, not merely whether the report had named the correct criterion. On the .ECO record, however, it found that the reconsideration request principally challenged substantive judgements and that the BGC had examined both the standards and the panel’s application of them. ICANN therefore prevailed on the individual .ECO claims.

The declaration then separated systemic criticism from case-specific relief. It recorded that the EIU did not compare the outcome of one CPE with other CPE results and that ICANN had no comparative quality-review process of its own. The panel considered concerns about apparent inconsistency to have some merit, especially where .ECO’s pass depended on one point. It also expressed concern that EIU determinations were treated as presumptively final in practice, while reconsideration did not provide substantive review and ICANN’s core values had not been contractually passed through to the evaluator as governing standards.

Those observations did not become an order to rescore .ECO. The panel described the individual challenge as an attempted appeal through a mechanism not designed to supply one and declared ICANN the prevailing party. On 10 March 2016, the ICANN Board accepted the panel’s findings and noted its suggestions, recognised the concerns and directed New gTLD Program reviews to consider the consistency and predictability of CPE and third-party evaluations. It did not reopen Big Room’s score.

Diagnosis and remedy diverged. The IRP could identify institutional risk in an exclusionary, threshold-sensitive system and make clear that BGC review was not exhausted by confirming that a criterion had been mentioned. It could identify the need for stronger comparative controls. It still did not replace the EIU’s environmental-community judgement merely because the scoring framework permitted another reasonable answer.

The result illustrates a recurrent feature of institutional review. A claimant may establish that an architecture has weaknesses without proving that the individual decision must be vacated. The organisation can promise better disclosure, closer supervision or more predictable future assessments while withholding the remedy that would return the claimant to contention.

Contract converted application promises into obligations

The CPE report did not itself make Big Room the registry operator in the root. The next legally important instrument was the .ECO registry agreement dated 8 July 2016. Section 1.1 designated Big Room as registry operator for .ECO, but expressly made that designation subject to the requirements and approvals necessary for delegation and root-zone entry.

This was the point at which procedural priority took contractual form. CPE had resolved contention and allowed Big Room to continue. The agreement created reciprocal rights and duties. Big Room obtained contractual status as the operator, subject to the agreement’s term, conditions and termination provisions. ICANN obtained contractual compliance and enforcement rights against the registry, while specified dispute procedures supplied additional routes for testing community-restriction performance.

The agreement also carried the community character of the application into operation. Section 2.19 required policies concerning naming, eligibility and use in conformity with the community purpose, required opportunities for the community to discuss and participate in policy development, and bound the registry to the Registry Restrictions Dispute Resolution Procedure. Specification 12 in the agreement incorporated community eligibility rules, ECO Profile requirements, complaint processes, suspension and takedown mechanisms, and a Community Eligibility Dispute Resolution Process.

The contract did not retrospectively prove that the CPE panel had drawn the community correctly. It performed a different task: it turned promises that had earned points into covenants against which registry conduct could be measured. A proposed profile requirement first supported a CPE score; after contracting, the corresponding obligation could be monitored and enforced under the agreement.

Even then, community participation did not become collective registry control. Members could supply input, qualify for registrations, file complaints or use dispute mechanisms. Big Room remained the legal counterparty and registry operator. ICANN retained contractual powers. The supporting environmental organisations did not gain direct authority to change the root, replace the operator, compel a particular compliance sanction or rewrite the agreement.

The resulting operating position was therefore held by Big Room under contract, not by an undefined global environmental public. The constituency supplied the justification for priority and the subject of continuing obligations. The legal capacity to operate the string belonged to the contracted corporation, subject to the agreement and the remaining delegation conditions.

Delegation was a separate administrative and technical act

Contracting still did not place .ECO into the root. The IANA delegation report dated 25 August 2016 recorded that the New gTLD application process was complete, the proposed sponsoring organisation matched the contracted party, contacts had been confirmed, technical conformance had been completed and other processing requirements had been satisfied.

Those checks did not revisit whether the EIU had correctly identified an environmental community. The IANA processing function verified the delegation request after programme conditions had been met, including the checks required before transmission into the then-operative root-zone authorisation and implementation workflow. It confirmed eligibility, the match between applicant and contracted party, contacts, technical conformance and other processing. It relied on the completed ICANN process rather than reopening contention.

The IANA delegation record for .ECO, showing a last-updated date of 29 April 2026, lists Big Room Inc. as the sponsoring organisation, records a registration date of 18 August 2016 and links to the delegation report. The record documents that the institutional chain reached the operational root and continues to identify Big Room as sponsor. It is not an IANA endorsement of every factual inference in the 2014 CPE report.

The sequence is therefore not semantic housekeeping. It identifies distinct authorities and distinct remedies. The EIU assessed priority. ICANN staff accepted and administered the result. The BGC and IRP reviewed limited questions of procedure and institutional compliance. ICANN contracted with the surviving applicant. IANA processed the delegation after programme and technical checks. Calling all of this an “award” conceals who could change what at each stage.

The chain of authority

Date Institutional act What it changed—and what it did not
4 June 2012 ICANN published the operative Applicant Guidebook Module 4. Fixed the 14-point threshold and the consequence for direct contenders; did not determine that Big Room qualified.
12 March 2014 ICANN invited Big Room to CPE, as recorded on the CPE status page. Opened the priority route for the community-based application; did not make standard applicants CPE participants.
6–7 October 2014 The EIU completed its 14-point report, and ICANN published the completed result. Resolved priority within the contention set; did not create a registry agreement or root entry.
22 October–18 November 2014 Little Birch and Minds + Machines filed Request 14-46; the BGC denied it. Confirmed that reconsideration could test policy and procedure, but would not operate as general merits rescoring.
2014–2015 Big Room challenged a CEP-related application hold through Request 15-2 and later withdrew the request. Showed that the CPE winner did not control application holds or the accountability timetable.
12 February–10 March 2016 The IRP declaration rejected the .ECO claim while criticising consistency controls; the Board accepted the panel’s findings and noted its suggestions. Left the individual score intact while directing attention to systemic predictability; did not grant a merits rehearing.
8 July 2016 ICANN and Big Room entered the .ECO registry agreement. Designated Big Room as contracted operator and incorporated specified community commitments into enforceable contractual terms; delegation still remained conditional.
18–25 August 2016 The root record registered .ECO on 18 August, and the IANA delegation report followed on 25 August. Documented the live delegation and the completed eligibility, identity, contact, technical and processing checks; did not reassess the CPE merits.

The corresponding allocation of power is equally divided.

Actor Power actually exercised Institutional limit
Big Room Defined the proposed community, assembled evidence, elected CPE, proposed registration rules and later signed the registry agreement. Could not set the CPE threshold, score its own application, end review activity unilaterally, authorise delegation or change the root.
Environmental supporters and qualifying institutions Supplied endorsements, affiliations, certification systems, organisational history and evidence of cohesion. Support did not amount to a universal representative mandate, a veto over scoring or direct control of the registry.
EIU CPE panel Classified the community, nexus, policies, support and opposition, and issued the 14-point report. Did not sign the registry agreement, operate .ECO or implement the root-zone change.
ICANN organisation Administered the Board-approved framework, selected and managed the provider, accepted and published the result, controlled application holds and handled the route towards contracting. Staff did not supply a de novo merits appeal, and acceptance of the score did not itself create a registry agreement or a root entry.
Board Governance Committee and Board The BGC decided Reconsideration Request 14-46; the Board later considered the IRP declaration and directed programme reviews to address consistency and predictability. Neither body recalculated the CPE score, and the Board’s 2016 resolutions did not themselves create the registry agreement or delegate .ECO.
IRP panel Tested whether the Board, including the BGC, had acted consistently with ICANN’s Articles and Bylaws, upheld ICANN on the .ECO claims and recorded systemic concerns. Did not sit as a second CPE panel and did not order Big Room’s application to be rescored.
Losing standard applicants Filed applications, contributed arguments and evidence, and invoked accountability mechanisms after exclusion. Could not participate as CPE candidates or obtain de novo scoring merely by presenting a different merits view.
IANA processing function Verified delegation eligibility, the match to the contracted party, contacts, technical conformance and other processing before the change entered the then-operative authorisation and implementation workflow. Did not choose among the applications or decide whether Big Room represented an environmental community.

What .ECO actually establishes

The .ECO case does not show that ICANN discovered one uncontested environmental community and handed that community a domain. It shows how a governance system made a contested constituency administratively legible. Big Room defined membership through institutions, certifications, missions and professional ties. The EIU accepted those boundaries, found sufficient cohesion and historical depth, connected “eco” to the constituency without treating it as the constituency’s formal name, credited detailed registration restrictions and classified the opposition as irrelevant. Those judgements produced exactly 14 points.

The score became exclusionary because ICANN’s prior rules attached elimination to it. Losing applicants could contribute to the wider record and use accountability mechanisms, but they could not obtain an ordinary merits appeal. Reconsideration treated their central arguments as substantive disagreement. Independent review upheld the BGC’s conduct while identifying broader weaknesses in comparative consistency and provider supervision. Review existed; a routine remedy capable of revisiting the score did not.

Big Room then passed through two additional gates. The registry agreement transformed application promises into contractual obligations and designated Big Room—not an abstract environmental public—as operator, subject to delegation requirements. IANA later confirmed the approved party and technical readiness and processed the root-zone request. The operational delegation is the end of that chain, not a new judgement about environmental representation.

The case’s bounded lesson is not that expert scoring should be replaced by endless litigation. It is that the legitimacy of an exclusionary expert judgement depends on the record the evaluator must expose, the errors a reviewer may correct, the speed with which relief can arrive and the degree to which comparable decisions must confront one another. In .ECO, a 14-point total, vulnerable to any one-point reduction, converted an application-defined community into priority. Contract and delegation later converted that priority into a registry right.