What are the Fundamental Obligations of Registry Operators in relation to Registrars?

In the ICANN ecosystem, the relationship between a Registry Operator (the entity managing the TLD, like .com or .app) and Registrars (the companies that sell domains to the public, like GoDaddy or Namecheap) is strictly governed by the Base Registry Agreement (Base RA).

The "Fundamental Obligations" are designed to ensure a competitive, fair, and stable domain name market.

1. Non-Discriminatory Access

This is the "Golden Rule" of the registry-registrar relationship. A Registry Operator must treat all ICANN-accredited registrars equally.

• Equal Treatment: You cannot offer a lower wholesale price or better technical support to one registrar while charging others more.
• Uniform Terms: All registrars must sign the same Registry-Registrar Agreement (RRA).
• Fair Promotion: If you offer a "sale" or marketing incentive, it must be available to every accredited registrar who wishes to participate.

2. The Registry-Registrar Agreement (RRA)

A Registry cannot simply make up its own rules on the fly.

• ICANN Approval: Any RRA must be consistent with the Base RA. If a Registry wants to make "substantive" changes to its RRA, it must submit those changes to ICANN for a review period (and often a public comment period).
• Transparency: The RRA must clearly outline the technical requirements, payment terms, and compliance standards the registrar must meet.

3. Technical Interoperability (The Shared Registration System)

Registries are obligated to provide a stable Shared Registration System (SRS) that registrars use to register and manage domains.

• EPP Standard: Registries must support the Extensible Provisioning Protocol (EPP), the industry-standard "language" used for domain transactions.
• Performance Specifications: The Registry must meet strict "Service Level Agreements" (SLAs). For example, the SRS must be available 99.4% to 99.9% of the time to ensure registrars can always process orders.

4. Data Handling and WHOIS/RDAP

Registries must maintain an accurate database of all registered domains and provide access to that data.

• Registration Data Directory Services (RDDS): Registries must provide a publicly queryable database (via WHOIS or the newer RDAP protocol) so that registrars and the public can verify domain ownership and status.
• Data Escrow: Registries must regularly "back up" their registration data with a third-party escrow provider. This ensures that if the Registry fails, the registrars (and their customers) don't lose their domains.

5. Vertical Integration Safeguards

If a company owns both a Registry and a Registrar (known as Vertical Integration), there are strict "Code of Conduct" obligations:

• Anti-Abuse: The Registry cannot use its "insider" data to give its own registrar an unfair advantage (e.g., seeing which domains are being searched for and registering them first).
• Separation of Systems: The Registry must maintain clear boundaries to ensure that its wholesale operations don't unfairly subsidize its retail arm.