Summary

  • The European Broadcasting Union (EBU) could elect Community Priority Evaluation because it had filed .RADIO as a community application and was in contention with three standard applicants. That procedural option did not give EBU the score, a contract or delegation. The Economist Intelligence Unit controlled the evaluation; ICANN published and applied the resulting report; and the report’s disclaimer separated a successful CPE result from the final outcome of the application.
  • Afilias Limited, BRS Media, Inc. and Tin Dale, LLC could oppose the application, seek records, file Reconsideration Request 14-41 and later initiate Independent Review. Those channels created participation and review access, but not a de novo right to have the Board Governance Committee re-score .RADIO. The BGC asked whether ICANN or its evaluator had contradicted an established policy or procedure. It treated the scoring objections as substantive disagreement and found no remediable contradiction. At the same meeting, it set aside the .GAY evaluation because 54 support letters had not been verified. That comparison supports a narrow procedural distinction: a proved failure to follow a required step could produce a new evaluation; disagreement with evaluative judgement could not.
  • The durable governance of .RADIO began after the application dispute. The 21 July 2016 Registry Agreement imposed Article 2.19, Specification 12 and the Registry Restrictions Dispute Resolution Procedure. Specification 12 made continuing eligibility, intended-use validation, investigations, suspension, registrar controls and independent appeal contractual duties. The assignment effective 5 January 2026 transferred the agreement, expressly including Specification 12, to Digity, LLC. PTI’s IANA naming-function process then issued a transfer report on 25 February, and the February root-zone audit records the completed Administrative Contact and Organisation update on 26 February. In its 24 July 2026 response to BRS Media, ICANN said an assignee must take the Registry Agreement as it stands, that Specification 12 cannot be abandoned through assignment, and that alleged non-compliance belongs in Contractual Compliance or the RRDRP rather than a reopening of CPE.
  • Those post-delegation routes are not interchangeable. A registrant contesting an individual denial or suspension is promised the Specification 12 appeal. A qualifying established institution seeking an operator-level remedy under the RRDRP must first submit the required registry-restriction problem report, allow that initial process to conclude, and then prove the procedure’s standing and merits elements before an approved provider. Separately, the live register.radio notice says its domain services will end at 09:00 UTC on 31 August and its domains will move to Sav.com, while the current registration agreement still identifies COREhub as the registrar. The notice was live on 31 July 2026 but omits the year; this article therefore treats the announced cut-over as 31 August 2026 while preserving that omission as a source limitation. That registrar and retail-service transition is distinct from the January contractual assignment and from the later PTI/IANA process that updated the sponsoring-organisation record. The February audit records no .RADIO nameserver or DS change, so it should not be described as a second delegation or as a technical transfer of the DNS service.

Two decisions on one day

On 20 January 2015, the Board Governance Committee considered two challenges to Community Priority Evaluation reports. The first came from the three standard applicants competing with EBU for .RADIO. They argued that the evaluator had misapplied the criteria, that the application should not have prevailed and that ICANN should reverse the resulting status changes. The BGC denied their request. Its meeting minutes recorded that the challengers had not shown a contradiction of an established ICANN policy or procedure, and that the determination was final because the challenged conduct was staff action or inaction.

The second challenge concerned .GAY. There, the BGC concluded that the evaluator had failed to verify 54 letters of support—one letter accompanied by 53 attachments—even though the applicable process required verification. The committee set aside that report and ordered a new evaluation by different evaluators. The contrast matters more than either score. It shows the operational boundary of reconsideration at that stage of the new-gTLD programme.

The BGC was not powerless, but its power was corrective rather than appellate: it could respond to a demonstrable departure from procedure, not substitute its own view whenever an applicant disputed an evaluator’s judgement.

That same distinction reappeared in a different form after .RADIO moved beyond contention. The Registry Agreement executed on 21 July 2016 contained rules on eligibility, use, validation, suspension and appeal that were much more concrete than the earlier dispute over who should win priority. A decade later, the assignment to Digity, LLC expressly included Specification 12. The institutional question had changed. Before contracting, rival applicants were trying to reopen an evaluation. After contracting, registrants and qualifying institutions would have to use the remedies attached to the registry’s own obligations.

The sequence separates powers often blurred in new-gTLD disputes. The evaluator decided priority; the BGC tested policy and procedure; and ICANN controlled contracting. At the delegation stage, the IANA root-zone management function processed and validated the request, while authorisation and Root Zone Maintainer implementation remained separate functions. After delegation, the registry validated applications and imposed first-instance measures, Specification 12 required an independent provider for registrant appeals, and ICANN retained registry-level contractual remedies. No institution controlled every stage.

Four applicants, but only one could elect community priority

EBU’s 2012 .RADIO application record identifies application 1-1083-39123 and records that it ultimately prevailed and was delegated. The same application-phase page also warns that its data may no longer describe the registry after delegation, an important caution in a case that later involved a change of registry operator.

EBU applied as a community applicant. Afilias Limited, BRS Media, Inc. and Tin Dale, LLC submitted standard applications for the same string. That classification created an asymmetric procedural option. Under the CPE process, Community Priority Evaluation was available only where a community application was in a contention set and the community applicant elected to use it. EBU could therefore request an evaluation that its standard-application rivals could not request on their own behalf.

The option was neither a vote nor a presumption of victory. It opened an independent assessment under the Applicant Guidebook. Failure returned the application to contention; meeting the threshold could give it priority. The mechanism did not create ownership of the word “radio”, confer sectoral regulatory authority or guarantee a Registry Agreement.

That separation is essential because the application itself made broad claims about the addressed community and about the applicant’s institutional position. EBU’s public application proposed a restricted namespace for broadcasters, internet radio operators, radio amateurs, radio professionals, companies supplying radio goods and services, and other categories connected to the sector. It described intended governance arrangements, eligibility conditions and enforcement mechanisms. Those statements were evidence of the commitments EBU offered and of the case it asked the evaluator to accept.

They were not independent proof that EBU represented every group included in the proposed community.

Community designation therefore allocated agenda-setting power rather than final decision power. EBU alone could activate CPE, but it could not set the score. Its competitors could not prevent the election, but they could place opposition and argument before the evaluator. ICANN designed the route and would later apply the status consequences, but it outsourced the criterion-by-criterion assessment. The resulting structure made the evaluator decisive at the contention gate while leaving the surrounding actors with different, narrower forms of participation.

Participation entered the record; control stayed with the evaluator

The CPE process page records EBU’s invitation on 19 February 2014 and completion of the evaluation on 10 September. The process allowed relevant application comments, support and opposition submitted within the specified period to be considered. That created an evidentiary channel for competitors and claimed community members. It did not make them co-decision-makers.

The distinction can be seen in the way the CPE report treated support and opposition. The panel evaluated whether supporting organisations represented a majority of the addressed community and whether relevant opposition existed. It did not conduct a plebiscite of every person or institution that might use radio, nor did it assign veto rights to objectors. It interpreted the record under the Guidebook criteria and attributed institutional weight to the materials it considered relevant.

The report also drew a useful line around EBU’s position. It did not treat EBU itself as the recognised institution of the entire proposed community. Instead, it concluded that organisations supporting the application represented a majority of that community. That finding was still contestable as an evaluative judgement, but it was not identical to accepting EBU’s institutional self-description. The panel was assessing an application against programme rules, not constituting a new global radio authority.

For the standard applicants, participation could influence the evidence but not control the method by which it was weighed. They could submit opposition and later argue that the evaluator had given it insufficient weight. They had no vote over the evaluator’s conclusions, no entitlement to cross-examine supporters within the CPE process and no automatic route to a merits appeal. This was a feature of the outsourced evaluation structure: the process invited evidence from affected parties while reserving the act of evaluation to a provider selected under ICANN’s programme architecture.

The benefit was decisional separation: ICANN’s Board and staff did not perform the scoring. The cost was evidentiary. Access to the evaluator’s internal process depended on the records ICANN required, received and retained, a limitation that became visible when the losing applicants tried to prove procedural error.

The CPE report changed contention status, not the root

The 10 September 2014 report recorded a score of 14 out of 16, the threshold required to prevail. The exact arithmetic is less important here than its procedural effect. The report accepted the application’s delineation and nexus sufficiently to pass, found its registration policies aligned with the claimed community purpose and credited enough support to overcome the relevant-opposition inquiry. It also noted commitments that would later reappear in contractual form: restricted eligibility, intended-use requirements, validation, random checks, suspension and an appeal mechanism.

A prevailing CPE result resolved the contention set in EBU’s favour. For the three standard applications, that meant they would not continue through the ordinary contention-resolution path while the successful community application advanced. This was an executable status consequence. It altered which applicants could proceed, and it created the immediate injury asserted in Reconsideration Request 14-41.

Yet the CPE report expressly disclaimed a broader legal effect. It stated that the evaluation result did not necessarily determine the final outcome of the application and did not waive or amend the Applicant Guidebook or any Registry Agreement. That language prevented the evaluation from being treated as a self-executing licence. EBU had won a priority determination, not a contract. ICANN still had to complete application processing and decide whether to enter the Registry Agreement.

A delegation request then had to pass IANA-function processing and validation, the applicable authorisation step, and technical implementation by the Root Zone Maintainer.

Each stage tested a different object. CPE tested priority; contracting established operator rights and duties; and delegation processing tested the proposed manager, contacts and technical arrangements. Authorisation and technical implementation remained separate functions. Success at the first gate reduced competitive uncertainty without displacing the later legal and operational requirements.

It also meant that the losing applicants’ remedy had to match the stage at which they claimed error. They were not yet challenging an operating registry’s breach of its eligibility rules. They were challenging an evaluation that had changed application status. Their requested relief was therefore aimed at stopping EBU’s advance and restoring the contention set, not at suspending a registration or compelling registry compliance.

The challengers sought a status remedy, not only an explanation

Afilias, BRS Media and Tin Dale filed Reconsideration Request 14-41 after the CPE result. Their original 25 September 2014 request is important because it identifies the practical consequences they believed required immediate correction. They said EBU had moved towards contracting while their own applications had been placed in a status indicating that they would not proceed.

The requesters did not ask merely for more explanation. They sought a sequence of executable measures: suspension of further consideration while their documentary request was resolved; suspension of any award of .RADIO to EBU; reconsideration of the prevailing evaluation; reversal of the status effects on the three standard applications; and restoration of the contention set to an active state. Those were requests by interested parties, not findings by ICANN, but they reveal the institutional stakes. A successful reconsideration could have reopened competition for the string.

Their claims attacked the evaluator’s treatment of the proposed community, the nexus between the string and the community, registration policies, support and opposition. They also argued that ICANN supplied insufficient information to test the evaluation. A revised request, dated 10 November and treated in the final determination as submitted on 11 November, added a challenge to ICANN’s response under the Documentary Information Disclosure Policy.

The requested remedy helps distinguish application status from delegation. At that point, no .RADIO Registry Agreement had been executed and no root-zone delegation had occurred. Reversing the CPE would not have removed an operating top-level domain from the DNS. It would have restored competing applications to the programme’s contention machinery. Conversely, allowing the report to stand did not itself insert .RADIO into the root. It cleared EBU to continue through later stages.

The applicants therefore had a direct economic and procedural interest in the outcome, but that interest did not define the standard of review. Reconsideration was not designed as an automatic second hearing on every disputed evaluative judgement. To obtain the relief they sought, the requesters had to connect the adverse result to a contradiction of established policy or procedure. That evidentiary burden made their access to the underlying CPE record central.

DIDP showed the custody cost of evaluator independence

On 26 September 2014, the requesters submitted a Documentary Information Disclosure Policy request. They sought contracts, guidance, internal material and information about the evaluator and its work. The theory was straightforward: if reconsideration depended on demonstrating procedural error, the applicants needed enough of the process record to identify one.

ICANN’s 24 October 2014 response disclosed some information, pointed to material already public and withheld other records under applicable nondisclosure conditions. It stated that ICANN had one contract with the Economist Intelligence Unit but did not publish that contract because of confidentiality. More significantly, ICANN said its Board and staff were not involved in evaluating the criteria, assigning scores or carrying out the panel’s underlying analysis. EIU coordinated the panel, and ICANN did not collect or maintain individual panel work papers.

That position protected the formal independence of the evaluator. It also narrowed the evidentiary field available through ICANN’s disclosure policy. A document-access mechanism cannot produce records that the institution says it neither possesses nor maintains. The challengers could obtain the published report, programme rules and some surrounding records, but not a complete archive of individual evaluator deliberations from ICANN.

This is not simply a transparency complaint. It is an allocation-of-authority problem. Outsourcing can separate substantive judgement from the institution whose staff administers the programme. Unless the contract and record-retention design require the provider to preserve and transmit process evidence, the same separation can limit later accountability. The decision-maker may be independent in one sense while its internal record is unavailable to the body asked to review whether procedure was followed.

The distinction between access and remedy becomes sharp here. DIDP offered a route to ask ICANN for documentary information. It did not compel EIU to create new records, transfer records outside ICANN’s custody or disclose every item covered by confidentiality. Reconsideration offered a route to allege policy or procedural contradiction. It did not shift the burden of proof merely because the challengers found the documentary record incomplete.

A better-retained record would not necessarily have changed the .RADIO outcome. It could, however, have allowed the requesters to test specific procedural events rather than rely primarily on the published report and their disagreement with its conclusions. The .GAY decision later showed why that mattered: a concrete failure to verify support letters could be remedied, while an assertion that evidence had been weighed incorrectly remained a merits dispute.

Reconsideration supplied a forum but capped the remedy

The BGC’s 20 January 2015 determination framed the issue under the then-applicable ICANN Bylaws. For a challenge to staff action or inaction, reconsideration asked whether the action contradicted established ICANN policy or whether staff failed to take required action. The committee did not treat itself as a general appellate tribunal for a new assessment of the community-priority criteria.

That standard controlled the outcome. The requesters argued that the evaluator had reached the wrong conclusions on community delineation, nexus, policies, support and opposition. The BGC treated those points as substantive disagreement with the report. It would not replace the evaluator’s assessment merely because other applicants could offer a competing interpretation of the same material.

The determination also rejected the expanded DIDP challenge on two grounds. First, it treated that portion of the revised request as one day outside the then-applicable 15-day filing period. Second, it concluded that the disclosure response did not independently violate an established policy or procedure. Timeliness therefore mattered, but it was not the only reason the documentary claim failed.

This is the practical meaning of review access without de novo re-scoring. The requesters could file, receive a reasoned determination and point to alleged defects. They could not require the BGC to repeat the CPE from the beginning and assign its own scores. The remedy ceiling was built into the function of reconsideration. It was capable of setting aside an action where a procedural contradiction was proved; it was not an unrestricted merits appeal.

The BGC also identified the Ombudsman as another route for concerns about fairness and process. The same meeting authorised an own-motion Ombudsman review of Community Priority Evaluation. That route expanded institutional scrutiny, but it did not give the .RADIO applicants a guaranteed status remedy. An Ombudsman can investigate and recommend; an applicant seeking restoration of a contention set still needs a decision-maker with authority to change the operative status.

The committee’s determination was final within the reconsideration process because the challenged conduct was attributed to staff action or inaction. The minutes recorded that no further Board or New gTLD Program Committee consideration would follow. Suzanne Woolf abstained because of a consulting relationship with Donuts, the parent of Tin Dale. That conflict management supported the integrity of the committee’s process, but it did not alter the scope of review.

Finality here must be described precisely. The BGC’s decision ended Request 14-41; it did not erase every possible accountability route. The applicants later initiated Independent Review. Nor did the BGC declare that every substantive conclusion in the CPE report was objectively correct. It held that the challengers had not shown the kind of policy or procedural contradiction that reconsideration could remedy.

.GAY demonstrated that the procedural ceiling was real, not absolute

The same-day treatment of Reconsideration Request 14-44 provides the most disciplined counterfactual. In the .GAY matter, the BGC found that EIU had failed to verify 54 support letters as required. This was not a disagreement about how much weight the letters deserved after verification. It was a demonstrable omission in the prescribed process. The minutes record that the committee set aside the CPE report and directed that a new evaluation be conducted by different evaluators.

The comparison prevents two opposite overstatements. It would be wrong to say the BGC could never disturb a CPE report. It did so when a concrete procedural failure was established. It would also be wrong to infer that the BGC had authority to re-weigh any contested evaluation. The remedy in .GAY followed a verified process defect, not a broad reconsideration of the merits.

Applied to .RADIO, the counterfactual is bounded. Had the challengers shown that required support or opposition evidence was not verified, that a mandatory procedural step was skipped or that the evaluator used a method contrary to an established rule, the BGC’s own conduct suggests that it could have set aside the report and required a new evaluation. The available determination says they did not make that showing. Their claims were treated as disputes over the evaluator’s substantive conclusions and over ICANN’s documentary response.

This comparison also exposes the importance of record architecture. The .GAY defect could be identified and proved. In .RADIO, ICANN’s position that it did not collect or maintain individual panel work papers narrowed the material from which a similar defect might have been reconstructed. That does not prove that a hidden defect existed. It shows that procedural review is only as testable as the record that survives.

The BGC said EIU had reviewed other situations and found no similar failures. That statement is evidence of what the committee was told and did, not a universal guarantee about every evaluation. The institutional lesson remains narrower: reconsideration could produce an executable remedy when a breach of established procedure was identified, but the burden rested on the challenger to connect the adverse result to such a breach.

Independent Review ended without a merits declaration

The three applicants did not stop with reconsideration. In October 2015 they commenced an Independent Review Process challenging ICANN’s treatment of .RADIO. The official IRP docket records the filing and subsequent procedural documents.

The proceeding did not produce a declaration on the merits. The claimants withdrew the case on 18 May 2016, and the International Centre for Dispute Resolution closed its administration on 31 May. The public docket supports no conclusion about why they withdrew, whether the parties settled or what terms might have accompanied the withdrawal. Silence is not evidence of agreement, concession or vindication.

The absence of a merits declaration matters because it leaves the BGC determination as the completed institutional ruling on the reconsideration claim. Independent Review remained available as a separate accountability mechanism, but in this case it did not alter the CPE result or provide a public interpretation of ICANN’s obligations. The contention result therefore stood, and EBU proceeded towards contracting.

This is another instance in which access and remedy must be separated. Initiating an IRP gave the applicants a forum and imposed procedural obligations on ICANN. A withdrawn proceeding, however, creates no adjudicated remedy. It did not restore the standard applications, order a new CPE or invalidate the application. The next legally consequential document was not an accountability declaration but the Registry Agreement.

Contracting, root registration and delegation were separate acts

ICANN and EBU executed the .RADIO Registry Agreement on 21 July 2016. Article 1 designated EBU as the registry operator subject to the requirements and approvals necessary for delegation and entry into the root. The agreement created enforceable contractual obligations, but it did not itself validate, authorise or implement a root-zone change.

The surviving primary records use several dates that describe different things. The IANA root record gives 22 September 2016 as the registration date. The September root-zone audit, however, lists the .RADIO delegation request as submitted on 30 September and still pending on 1 October. The delegation report dated 7 October records EBU as the proposed manager and confirms programme completion, a match to the contracting party, contact confirmations, technical conformance and other processing. The October audit records the multi-part .RADIO change as completed on 12 October.

The dates therefore cannot be compressed into a single “award”, and the root-record registration date should not be treated as the technical implementation timestamp. CPE cleared contention in September 2014. The Registry Agreement created operator duties in July 2016. The audit trail shows a delegation request entering processing on 30 September and a change affecting contacts, DS records, metadata, sponsorship and nameservers completing on 12 October. The 7 October report documents completed checks; its date does not by itself identify who made the root-file edit or when that edit became effective.

The authority chain was also more divided than the word “IANA” suggests. ICANN’s 2016 report on parallel root-zone-management testing describes the pre-transition production workflow: ICANN received, processed and validated change requests; the United States National Telecommunications and Information Administration supplied root-zone authorisation; and Verisign, as Root Zone Maintainer, implemented the authorised change and published the updated signed root-zone file. The IANA functions contract expired on 1 October, and ICANN’s post-transition account says PTI was performing the IANA functions from that date. A later ICANN account says the transition removed the United States authorisation step, while a 20 October operational update says ICANN and Verisign were still switching to the systems designed without that role. The .RADIO request entered processing on 30 September and was recorded as completed on 12 October. The selected records therefore do not establish the request-specific authorisation hand-off during that transition interval, and the 7 October report date cannot supply it by inference.

ICANN controlled whether it would contract and on what terms. The IANA root-zone management function processed and validated the delegation request. In both the documented pre-transition architecture and the post-transition design, Root Zone Maintainer implementation was a separate technical act; the public records reviewed here do not justify assigning a request-specific United States authorisation to .RADIO after 1 October. EBU could not turn a CPE report into a delegated top-level domain by unilateral action. Nor could the losing applicants use their old application status as a direct means of controlling those later checks.

By the delegation stage, the operative question was whether the proposed manager and technical arrangements met the required conditions, not whether the BGC should re-score the application.

The sequence also limits what can be claimed about the source of .RADIO’s restrictions. The CPE report recognised proposed policies, but the report’s disclaimer denied that it amended the Registry Agreement. The binding source after July 2016 was the executed contract. Completion of the delegation chain then made the namespace operational under that contract. The authority to reject or suspend a registration arose from the registry’s contractual policy regime, not from the evaluator continuing to supervise the application.

Article 2.19 converted community claims into operator duties

Article 2.19 of the Registry Agreement required the operator to maintain registration policies and practices consistent with the community-based nature of the application. Those policies had to conform to the application’s commitments concerning naming conventions, community membership and use. The operator also had to establish and enforce registration and dispute-resolution procedures and comply with the Registry Restrictions Dispute Resolution Procedure.

The provision further required operation of the TLD in a manner that allowed the community to discuss and participate in the development and modification of registration policies. That language allocated participation rights, not a contractual veto. It did not say that every broadcaster, amateur operator, supplier or professional could block a policy change, appoint the registry operator or approve individual registrations.

The distinction is particularly important after the 2026 assignment, because a commitment to community participation does not establish that EBU or the World .Radio Advisory Board retained operational control once Digity became the contracting party and was later listed as sponsoring organisation in the IANA Root Zone Database.

Article 2.19 did something the application and CPE report could not do alone: it made continued conformity a duty owed under the Registry Agreement. A failure to operate the namespace consistently with the specified community restrictions could therefore become a matter of contractual compliance. The operator’s commitments were no longer merely reasons why the CPE panel had awarded points.

Specification 7 supplied a further layer of dispute and remedy architecture. It incorporated minimum rights-protection mechanisms and required the registry to implement remedies imposed through applicable ICANN processes. It also connected registry obligations to the Registry–Registrar Agreement, allowing operational controls to be transmitted to the registrar channel. The exact allocation depended on the contract and implementing policies, but the core point is that enforcement had to move through legal relationships among ICANN, the registry, registrars and registrants rather than through the CPE evaluator.

Specification 12 allocated validation, enforcement and appeal

Specification 12 is the most detailed statement of how .RADIO’s community restrictions were supposed to work after delegation. It required the operator to “implement and comply” with the policies set out there. That imperative language made the restrictions part of the bargain with ICANN.

Eligibility was continuing, not merely a gateway at the moment of registration. A registrant had to be a bona fide member of the defined radio community. Its actions and proposed use had to be generally accepted as legitimate and beneficial to the values of that community, proportionate to the role and importance of the domain name, and undertaken in good faith. The conditions had to be fulfilled at registration and thereafter.

The specification linked the strength of validation to the likely significance of the name. The more important the string, or the more strongly an ordinary user might assume an authoritative connection, the stronger the validation was expected to be. This was an attempt to calibrate scrutiny rather than apply a single documentary threshold to every registration.

Applicants also had to state their intended use. A false intended-use statement could indicate bad faith and provide a basis for suspension. The operator was authorised to pre-identify eligible actors through associations and other recognised bodies, perform post-registration validation and conduct statistically targeted random checks. It also had to integrate complaints and validation information into a system capable of tracking issues over time.

Name selection and actual use were connected to the applicant’s nexus to the radio community. A registrant could not rely on nominal membership alone if the chosen name or use created a misleading implication of authority. Content and use remained subject to the same community conditions after registration. This continuing-use feature distinguished .RADIO from a purely documentary eligibility screen.

The specification gave the registry first-instance enforcement power. It could conduct targeted random investigations, follow up complaints and use registry data and other evidence to assess compliance. Compliance officers were expected to give enhanced attention to applicants with a poor record, including relevant histories under the Uniform Domain Name Dispute Resolution Policy or Uniform Rapid Suspension system. The operator could reject an application where the intended use was illegitimate or harmful to the community purpose and could suspend a domain where a false intended-use statement indicated bad faith.

Registrar controls extended the enforcement chain. The registry could restrict a registrar from accepting new .RADIO registrations, require investigation of the registrar’s existing inventory or impose post-validation requirements. Those tools addressed conduct at a distribution intermediary rather than only at the individual registrant. They also made the registry’s relationship with registrars a practical site of governance.

Administrative measures were not supposed to be unreviewable. Specification 12 required an appeal mechanism, with the registry acting at first instance and an independent alternative dispute-resolution provider hearing the appeal. The appeal was to be based on a charter approved by EBU and the World .Radio Advisory Board.

That clause allocated a role in designing the appeal framework, but the public documents identified for this article do not disclose the current charter, the present membership or voting rules of the advisory board, the identity and published procedure of a current appeal provider, or how those functions were reassigned after Digity became operator.

The absence of those records in the available official account does not nullify the contractual duty. It limits what can be said about observed operation. The agreement proves that an appeal had to exist. The record reviewed here does not prove that a particular registrant used it, received relief or encountered a consistent and independent process. Contractual design and enforcement history are separate evidentiary questions.

A registrant appeal and an RRDRP complaint protect different interests

The appeal promised in Specification 12 operates at the registrant level. It gives a person or organisation subjected to a registry administrative measure a route beyond the registry’s first-instance decision. The Registry Restrictions Dispute Resolution Procedure protects a different interest: its parties are a harmed established institution and the community-based registry operator, and it tests operator compliance with the community restrictions in the Registry Agreement. It is not a general merits appeal for a disappointed registrant, former applicant or commercial competitor.

A formal RRDRP complaint is not the first step. The procedure requires initial allegations to pass through a Registry Restriction Problem Report System. The operator receives the report and must take reasonable steps to investigate and, where warranted, remedy the reported non-compliance. The RRDRP Rules require a complainant approaching an approved provider to prove that the report was filed, the initial process concluded and the claimed non-compliance is continuing. Dissatisfaction with the operator’s response does not itself establish standing.

ICANN’s current RRDRP page operationalises the initial stage through an “RRDRP Form”. ICANN reviews the report for completeness, a claim involving at least one restriction and the reporter’s good standing; a qualifying report goes to the operator; and a formal provider complaint may follow if non-compliance is still alleged. The page does not say the form legally replaces the RRPRS named in the procedure. It is therefore safest to describe the live form as ICANN’s current intake for the required problem report. Nor do the primary materials say that every general Contractual Compliance submission automatically counts as that prerequisite.

Standing and merits remain separate. The complainant must be an established institution with an ongoing relationship to a defined community consisting of the restricted population the TLD supports, and it must have completed the prior report stage. It must then prove a defined community, a strong association between that community and the string, a violation of the contractual restrictions, and measurable harm to both the complainant and the community. The burden is a preponderance of the evidence. The published rule does not add “systemic” as a freestanding standing or merits threshold.

The remedies reflect the parties. Because registrants are generally not parties, an expert ordinarily cannot recommend deletion, transfer or suspension of their registrations, except for registrations held by specified operator insiders or entities under common control. The expert may recommend prospective remedial measures, suspension of new registrations and, in extraordinary circumstances involving malice, termination of the Registry Agreement. Damages are unavailable, and ICANN retains authority over the contractual remedy.

Either RRDRP party may seek a de novo appeal on the existing record, with a limited route for qualifying additional evidence. That express appellate design contrasts with Reconsideration Request 14-41, where the BGC did not conduct a de novo CPE re-scoring. If an RRDRP expert finds breach, ICANN must notify the operator and provide the contractual opportunity to cure; further escalation remains with ICANN.

The routes therefore answer different questions. Specification 12 asks whether an administrative measure was correctly applied to a registrant. RRDRP asks whether a qualifying institution can prove operator non-compliance and measurable institutional and community harm. Contractual Compliance addresses conduct that maps to an ICANN contract duty. The official sources reviewed here do not identify a published .RADIO-specific RRDRP determination, compliance enforcement notice or Specification 12 appeal decision. That is a bounded documentary finding, not proof that no private report, complaint or appeal has occurred.

The 2017 launch policy showed operational implementation

The .RADIO launch policy filed with ICANN provides dated evidence that the contractual model was translated into registration operations. It governed launch phases running from 23 August to 31 October 2017 and anticipated general availability on 15 November.

The policy stated that applicants were bound by registry, registrar and ICANN requirements. It repeated that eligibility had to exist at registration and continue throughout the life of the domain. Applicants needed a legitimate connection to the radio community, a good-faith intended use and a name proportionate to their role. A false intended-use declaration could justify suspension.

Validation was not limited to self-certification. The policy called for claims to be examined individually and required documentary proof appropriate to the applicant category. Amateur-radio applicants could be asked for licences, club membership or a link to a call sign. Professionals had to show identity and involvement in the sector. Companies could be asked for company registration and evidence of radio-related activity. During the landrush phase, a request could be rejected where the necessary connection was not proved.

This policy is stronger evidence of implementation than the 2012 application because it was issued after contracting and in preparation for launch. It shows how eligibility and proof were expected to operate in practice. It is still not a complete enforcement history. A policy can be adopted without every investigation being public; a power to suspend does not prove that a suspension occurred; and an appeal clause does not show that an independent provider heard a case.

The date also matters. The 2017 policy predates the 2026 assignment. It cannot, without further documentation, establish every element of current practice under Digity. A current registration policy, Registry–Registrar Agreement, appeal charter and operator authority map would be needed to test whether implementation remains aligned with Specification 12 after the transfer. The official record proves the baseline obligation and a historical operational translation, but it does not supply continuous public observation of every later enforcement choice.

The 2026 assignment moved the operator and carried the obligations

Effective 5 January 2026, EBU assigned the .RADIO Registry Agreement to Digity, LLC. The instrument records EBU’s request for consent on 28 July 2025 and ICANN’s conditional consent on 19 December. It defines the assigned agreement to include Specification 12, transfers EBU’s rights and obligations, requires Digity to assume accrued and contingent liabilities, and substitutes Digity for EBU for all purposes of the Registry Agreement.

The document also states that EBU remains bound by the agreement. That may preserve liability or continuing commitments; it does not prove that EBU retained daily operational authority. A current charter, policy or post-assignment instrument would be needed to establish any continuing approval or enforcement power.

PTI’s IANA naming-function process then handled a separate sponsoring-organisation transfer. Its 25 February 2026 transfer report records the contracting-party match, contact confirmations, technical conformance and other checks before transmission for authorisation and implementation. The February root-zone audit records one .RADIO request affecting the Administrative Contact, Organisation and Technical Contact as withdrawn on 20 February, followed by a completed Administrative Contact and Organisation change on 26 February. The current root record, last updated on 27 July 2026, lists Digity as sponsoring organisation and CORE Association as technical contact. ICANN’s current agreement page likewise names Digity as operator and identifies a community agreement containing Specification 12.

Those records describe distinct functions. Digity is the Registry Agreement counterparty and the organisation listed by IANA as sponsor; CORE Association is the listed technical contact; neither fact identifies the registrar used by a particular registrant. PTI’s current root-zone role is to accept and validate change requests, while the Root Zone Maintainer implements validated changes to the DNS root-zone file. The February audit does not record a .RADIO nameserver or DS change in the completed request. It therefore supports an administrative sponsorship and contact update, not a claim that PTI itself edited the DNS root-zone file or that .RADIO was delegated anew. ICANN’s later statement that community consultation or evidence of support or non-objection forms part of a community-TLD assignment describes an input and transition safeguard, not a permanent community veto.

The January assignment moved the contract; the February IANA process validated the follow-on sponsorship request, after which the root record was updated. Neither process rewrote the eligibility regime. Specification 12 travelled through the assigned Registry Agreement, making continuity a matter of contract rather than EBU’s institutional reputation. The unresolved question is operational: whether current policies, validation practice and appeal materials make the successor’s exercise of that authority visible.

The registrar transition is a different transfer

A second 2026 transition appears at the retail layer. On the live register.radio homepage at publication, a notice said domain services would end at 09:00 UTC on 31 August and all domains would transfer to Sav.com. It did not print a year. Because the notice was live on 31 July 2026 and described a future cut-over, this article treats the date as 31 August 2026 while preserving the omission as a source limitation.

The service’s current registration agreement identifies COREhub S.R.L.U. as the registrar providing register.radio services. It permits discontinuation of .RADIO registrations or renewals on reasonable notice, with transfer to another registrar, and says the agreement ends when a name transfers away. Until the announced cut-over, those terms support describing COREhub as registrar for registrations held through that storefront; Sav.com is the announced destination for that portfolio.

The notice does not purport to transfer every .RADIO registration, assign the Registry Agreement or change the sponsoring organisation listed in IANA’s Root Zone Database. It supports a registrar and retail-service transfer for names handled through register.radio. The documents do not specify the account-migration mechanics, pricing, credentials or support arrangements after cut-over.

The public wording is also stale: the same terms still name EBU as registry operator, while ICANN names Digity as the contracting operator and IANA lists it as sponsoring organisation. That does not undermine the signed assignment, but it demonstrates the need for versioned retail terms. COREhub’s registrar role must also remain distinct from CORE Association’s listed technical-contact role. Similar names do not merge legal responsibility.

The 2026 challenge shifted from scoring to contract enforcement

The operator assignment did not end criticism by a former applicant. On 16 April 2026, BRS Media sent ICANN’s Board a formal letter about CPE and post-delegation safeguards. It alleged that restrictive promises could be used to gain priority and later diluted or separated from operational control. It asked ICANN to enforce Specification 12, prevent conversion to an open model, revisit earlier CPE outcomes and strengthen the next-round rules. Those were allegations and policy requests, not findings of breach, and the letter did not revive Reconsideration Request 14-41 or the withdrawn IRP.

ICANN’s 24 July 2026 response to BRS Media separated the application-stage dispute from the contractual regime. It described CPE as an optional contention-resolution mechanism, not the source of community status. A successful community application must carry community registration policies in Specification 12 whether or not CPE resolved contention. ICANN did not re-evaluate the 2014 score; it treated CPE as a completed allocation event and Specification 12 as the current legal object.

On assignment, ICANN said the successor must assume the Registry Agreement as it stands and cannot revise or abandon Specification 12 through assignment. The identified route for changing those commitments is the Community gTLD Change Request Procedure. Only the registry operator may initiate a request. ICANN publishes a qualifying request for comment, and the procedure excludes changes that would remove the community policies, excessively broaden or narrow eligibility or name-selection rules, or significantly harm the TLD community. Community input can influence the record; it is not contractual approval power.

The response also pointed to Contractual Compliance and the RRDRP. A registrant or community member may complain to Compliance about Specification 12 performance. A qualifying RRDRP complainant must first complete the registry-restriction problem-report stage and then prove the procedure’s standing and merits elements before an approved provider. If an expert finds breach, ICANN issues the breach notice and provides the contractual opportunity to cure. The expert decides the complaint; ICANN controls contractual enforcement; the operator receives the cure opportunity.

The primary material does not say that a general Compliance complaint automatically satisfies the RRDRP prerequisite. ICANN’s live RRDRP page directs initial reporters to an RRDRP Form and describes provider escalation only after the report reaches the operator and non-compliance is still alleged. The two routes should therefore not be treated as interchangeable without confirmation from ICANN.

A 20 May 2026 response to fTLD Registry Services added that Specification 12 is reviewed when a community TLD is selected for a full-scope Registry Agreement audit, while not every TLD is selected in every cycle. That establishes an available supervisory tool, not that .RADIO was audited or found compliant. Both letters state ICANN org’s interpretation; neither adjudicates BRS Media’s allegations.

ICANN also said there is no current mechanism for a community TLD to become open or unrestricted or abandon the commitments fixed at contracting. That supports contractual continuity. It does not establish that every Digity validation decision is correct, that the independent appeal is discoverable, that the 2017 policy remains the present operating manual, or that the register.radio registrar transfer will be seamless.

The 2026 correspondence therefore produced no finding against .RADIO and none of the remedies BRS Media requested. It clarified the current gate. A registrant uses the Specification 12 appeal for an individual measure. A qualifying institution uses RRDRP only after the prior report and only on the defined elements. Contractual Compliance addresses duties in the Registry Agreement, and ICANN controls breach, cure and escalation. The old contention set supplies history, not the present cause of action.

What the record proves—and what it does not

The official record supports a segmented chain of authority. EBU elected CPE; EIU scored the application; ICANN applied the contention result. The losing applicants could oppose, seek documents, request reconsideration and initiate Independent Review, but they obtained neither a de novo re-scoring nor a public IRP declaration. ICANN later contracted for community restrictions. The IANA root-zone management function processed and validated the delegation request, and Root Zone Maintainer implementation remained a separate act.

Because the request straddled the 1 October transition, the selected records do not identify a request-specific authorisation hand-off. After delegation, the registry received first-instance validation and enforcement power, Specification 12 required an independent registrant appeal, qualifying institutions received RRDRP access, and ICANN retained contractual remedies.

In 2026, the assignment moved the Registry Agreement to Digity and expressly carried Specification 12. The IANA transfer process then validated the proposed manager and contacts, while the February audit records the completed Organisation and Administrative Contact update on 26 February. The register.radio notice concerns a third event at the registrar layer. These acts have different objects and should not be compressed into one transfer.

The record does not prove that EBU politically represented everyone associated with radio, that the BGC endorsed every substantive CPE finding, or why the IRP was withdrawn. The .GAY disposition supports only the narrower procedural comparison: a proved failure to perform required verification could justify a new evaluation. It does not establish a general right to consistent outcomes across different applications.

Nor does the public record identify a current published appeal charter, independent provider, .RADIO-specific appeal result, RRDRP determination or Contractual Compliance sanction. The live register.radio notice omits the year of its announced 31 August cut-over, and the terms still identify EBU as operator while naming COREhub as registrar. The signed assignment resolves the contractual-operator question, while ICANN’s agreement page and IANA’s root record show the current contracting and sponsorship entries; the retail documents do not reveal all post-transfer implementation details.

The disciplined conclusion is institutional. CPE cleared the contention set; reconsideration offered process review but no fresh merits hearing; the Registry Agreement transformed selected application promises into duties; and a separate delegation chain—processing and validation, authorisation, then Root Zone Maintainer implementation—made the namespace operational. Assignment later carried the contractual duties to Digity, while the sponsorship update and the registrar transition changed different records and relationships.

What remains uncertain is how visibly the current validation, appeal, problem-report and compliance routes operate when a decision is contested.