Registry Voluntary Commitments Balancing Innovation and Compliance

As the 2026 round of the new gTLD program takes shape, Registry Voluntary Commitments, or RVCs, have emerged as a powerful but complex mechanism for applicants to distinguish their proposals while simultaneously ensuring adherence to public interest expectations. RVCs are self-imposed, binding obligations that go beyond the standard terms of the Registry Agreement, offering applicants a way to customize the operational, policy, or content-related aspects of their proposed top-level domain in response to community concerns, legal sensitivities, or strategic positioning. They provide a bridge between the innovation that applicants seek to bring to the DNS and the compliance obligations that ICANN and the broader internet governance ecosystem require to maintain stability, trust, and equity.

Introduced formally in response to the shortcomings of Public Interest Commitments (PICs) in the 2012 round, RVCs are now defined and governed by specific sections of the 2026 gTLD Applicant Guidebook and incorporated into the Registry Agreement as enforceable terms. The key distinction between RVCs and PICs lies in the level of applicant initiative—RVCs are wholly proposed by the applicant and not prompted or required by ICANN. However, once accepted into the Registry Agreement, they become binding and enforceable by ICANN’s Contractual Compliance department, placing legal and operational obligations on the registry operator.

Applicants use RVCs for a variety of purposes. Some RVCs are employed to limit registration eligibility, such as restricting domain ownership to members of a specific professional community, geographic region, or legal category. Others are used to impose content or use restrictions, such as prohibiting the use of domains within the gTLD for illegal services, disinformation, or unlicensed financial activities. Still others are designed to bolster transparency and trust through operational guarantees, including commitments to regular abuse reporting, proactive audits, or higher-than-required service level agreements.

The voluntary nature of RVCs allows applicants to craft highly tailored proposals that can differentiate their application in competitive contention sets. For example, an applicant for a .med TLD might propose RVCs that require registrants to be licensed medical professionals, validated through a global credentialing database. This kind of RVC not only enhances user trust but can also provide an edge during Community Priority Evaluation or mitigate the risk of objections from governments or international organizations concerned about public health and safety.

However, the power to define RVCs comes with significant responsibility. ICANN requires that all RVCs be specific, measurable, and enforceable. Vague language or open-ended commitments will not be accepted into the contract and can result in costly delays during the application review process. Applicants must be prepared to demonstrate the feasibility of their commitments, including operational plans, technical resources, compliance procedures, and, where applicable, independent verification mechanisms. Failure to fulfill an RVC after delegation can trigger compliance investigations, breach notices, and ultimately the suspension or termination of the registry agreement.

Because of these risks, crafting RVCs demands a strategic balance between ambition and realism. Overcommitting to rigorous restrictions or extensive oversight mechanisms may appeal to evaluators or communities during the application phase, but can become operationally unsustainable once the gTLD is live. Conversely, proposing minimal or superficial RVCs may fail to satisfy stakeholders or adequately address potential objections. Legal teams, policy advisors, and registry services providers must collaborate closely during the drafting process to ensure that commitments are both impactful and executable.

The enforceability of RVCs has been enhanced for 2026 through a strengthened compliance framework. ICANN’s Contractual Compliance team is now equipped with more granular auditing capabilities and automated monitoring tools that can flag potential violations of registry obligations. Registries subject to RVCs may be required to submit periodic compliance reports or undergo third-party audits to demonstrate adherence. Additionally, stakeholders who believe an RVC has been breached can file a formal complaint, triggering an investigative process that may involve both ICANN and external evaluators.

Transparency is another critical component of the RVC process. All RVCs proposed by applicants are published in full in the public application portal, allowing for public review, comment, and objection. During the objection period, parties may challenge the sufficiency, fairness, or practicality of proposed RVCs, and applicants may be asked to modify their commitments in response. This process serves to uphold the legitimacy of the RVC system and ensure that voluntary commitments are not used as public relations tools but as enforceable public interest safeguards.

In many cases, RVCs also serve to preempt regulatory or political opposition. Governmental Advisory Committee (GAC) members and intergovernmental organizations often express concern about gTLDs that could impact sensitive sectors such as finance, healthcare, education, or intellectual property. Well-structured RVCs can mitigate these concerns and help avert GAC Advice or Early Warnings that might otherwise jeopardize the application. In this way, RVCs are not only legal tools but also instruments of diplomacy and stakeholder engagement.

From a broader perspective, RVCs represent a shift in ICANN’s governance model toward more applicant-driven accountability. While ICANN retains final oversight, the responsibility for crafting meaningful commitments rests with the applicant. This aligns with the multistakeholder ethos of the ICANN model, allowing for bottom-up policy customization within a consistent contractual framework. For applicants, the ability to define RVCs is both an opportunity to innovate and a mandate to operate with foresight, integrity, and transparency.

As the 2026 round unfolds, successful applicants will be those who leverage RVCs strategically, using them not just to satisfy ICANN requirements, but to build enduring trust with users, regulators, and the broader internet community. Balancing innovation and compliance in this context requires not only legal precision and technical capacity, but a clear vision of the gTLD’s purpose and the societal values it seeks to uphold. When used effectively, RVCs are not mere regulatory appendages—they are foundational commitments that can define the character and credibility of a new space on the internet.

You said:

As the 2026 round of the new gTLD program takes shape, Registry Voluntary Commitments, or RVCs, have emerged as a powerful but complex mechanism for applicants to distinguish their proposals while simultaneously ensuring adherence to public interest expectations. RVCs are self-imposed, binding obligations that go beyond the standard terms of the Registry Agreement, offering applicants…