Registry Service Evaluation Process RSEP Demystified

The Registry Service Evaluation Process, or RSEP, is a critical procedural mechanism within ICANN’s governance framework that enables registry operators to propose new services or changes to their existing services under a generic top-level domain (gTLD) contract. Given the foundational importance of stability, security, and competition in the DNS, any modification to how a registry operates—including innovations in service delivery, business models, or technical architecture—must be reviewed with rigor. The RSEP exists to ensure that these changes are consistent with ICANN policies, do not undermine interoperability or fair competition, and maintain the trustworthiness of the domain name system. Though vital to adaptive evolution in the registry space, the RSEP process is often perceived as opaque or cumbersome, particularly for those outside registry operations. Understanding its structure, criteria, and implications is key to appreciating how innovation is governed within the TLD ecosystem.

When a registry operator wishes to implement a new service or materially change the operation of an existing one—such as introducing a new fee structure, changing the DNS resolution behavior, offering new kinds of domain locking services, or enabling registry-level privacy features—they must submit a detailed proposal through the RSEP. This submission includes a comprehensive description of the proposed change, a rationale for why it is being pursued, and an assessment of its potential impacts on competition, security, stability, and registry operations. Importantly, the proposal must align with the obligations set forth in the operator’s Registry Agreement with ICANN, particularly Specification 6, which deals with functional and performance specifications.

Upon submission, ICANN performs an initial evaluation of the request to determine whether the proposed change constitutes a “registry service” as defined in the agreement and whether it might raise significant concerns under the DNS’s security, stability, or competition frameworks. This initial review typically occurs within a 15-day window. If ICANN determines that the change is not material or raises no such concerns, the request may be approved and implemented without further process. However, if the proposal is deemed to require deeper analysis, ICANN escalates the request into a full evaluation, which may include public comment, consultations with relevant stakeholders, and, in some cases, referral to the Registry Services Technical Evaluation Panel (RSTEP).

The RSTEP is a standing body of technical experts with the responsibility of analyzing proposed registry services that may impact DNS stability or security. The panel conducts a thorough, objective review of the technical implications of the proposed change, considering factors such as potential for misuse, failure modes, load on root servers, or systemic interactions with existing protocols. If the RSTEP determines that the proposed service presents significant risk, it can recommend mitigation strategies, modifications, or even rejection. Conversely, if the service is deemed safe and stable, the panel’s findings can expedite the approval process.

Another major concern considered in the RSEP is the potential impact on competition. ICANN has a mandate, derived from its agreements with the U.S. Department of Commerce and its own bylaws, to promote fair competition within the domain name industry. As such, proposals that would provide exclusive access to registry services, create barriers for registrars, or confer market advantages that conflict with established competition law principles are closely scrutinized. In certain cases, ICANN may consult with antitrust authorities or subject the proposal to additional review if competition concerns arise. For example, a registry seeking to offer a vertically integrated service with an affiliated registrar must ensure that this does not violate cross-ownership or equal access requirements applicable to that TLD.

Transparency is a hallmark of the RSEP. Once a request is accepted for evaluation, ICANN posts the proposal on its website along with supporting documentation and tracks its status publicly. This allows community stakeholders, including registrars, civil society groups, and technical experts, to monitor and comment on proposals that may affect their operations or interests. Public input can be particularly influential in shaping the outcome of an RSEP, especially if significant concerns are raised during the comment period. ICANN staff and the Board are expected to weigh this input carefully, balancing the interests of innovation with those of public trust and systemic stability.

There is also an interdependency between the RSEP and broader policy development processes. In some cases, a registry’s proposal may touch on issues under consideration within the GNSO’s policy-making channels. When this occurs, ICANN may defer approval or condition implementation on the resolution of policy ambiguities. For instance, if a registry proposes a new service involving registration data usage and the community is actively engaged in developing policy on RDAP access, the proposal may be placed on hold pending a harmonized solution. This ensures coherence between operational changes and the broader policy framework governing the DNS.

From a strategic perspective, the RSEP allows registries to innovate while providing a measured mechanism for oversight and accountability. Many value-added services that are now commonplace—such as registry lock, domain bundling, DNSSEC enhancements, and IDN implementation—have emerged through this process. At the same time, ICANN uses the RSEP as a lever to manage systemic risk and to ensure that no single registry’s operational changes inadvertently destabilize the global DNS. The process also reflects a broader commitment to the multistakeholder model, as it integrates technical evaluation, community input, contractual review, and public interest considerations into a single procedural framework.

One area of ongoing discussion is how to improve the efficiency and predictability of the RSEP without sacrificing rigor. Registry operators have expressed concerns about process delays, ambiguous criteria, and inconsistent handling of similar proposals. In response, ICANN has periodically reviewed its procedures to streamline timelines, clarify evaluation thresholds, and provide more detailed guidance to applicants. The development of standardized service categories and pre-approved extension templates may offer further ways to reduce friction, particularly for changes that are routine or have known precedents.

In conclusion, the Registry Service Evaluation Process is a cornerstone of operational governance in the DNS, offering a structured path for innovation while safeguarding the system’s integrity. It embodies the principle that the freedom to evolve must be matched with the responsibility to ensure security, stability, and fairness. For those navigating the TLD ecosystem, understanding how the RSEP works is essential—not only to launching new services but also to maintaining compliance, fostering trust, and contributing to the ongoing evolution of internet infrastructure. As the domain name industry continues to grow in complexity and global significance, the RSEP will remain a vital instrument of balanced, transparent, and responsive governance.

The Registry Service Evaluation Process, or RSEP, is a critical procedural mechanism within ICANN’s governance framework that enables registry operators to propose new services or changes to their existing services under a generic top-level domain (gTLD) contract. Given the foundational importance of stability, security, and competition in the DNS, any modification to how a registry…