EPP Pre-Registration Verification

1.1. Problem Statement

The current EPP protocol lacks mechanisms for registrars to submit pre-registration data to the registry for quality verification. This gap leads to potential issues with abusive domain registrations, which can harm the integrity of the top-level domain (TLD). ## Use Case Description¶

A registrant wants to register domain names within a TLD registry via a registrar. To ensure the quality of registrations and prevent abusive domains, the registrar uses the proposed EPP extension to submit pre-registration data of the registrant to the registry. The registry, equipped with AI/ML techniques or services, analyzes this data to assign a registrant quality score back to the registrar. Based on this score, the registrar can decide whether to accept, reject or put on hold the registration request.¶

1.2. Importance and Benefits

Addressing the quality of the registrant data before the actual registration process occurs brings many benefits. Adding a pre-registration process benefits the domain registration ecosystem by: - Potentially reducing the number of malicious registration and frauds and reducing operating costs to registrar and registry in responding to the abuse. - Ensuring the quality of domain registrations is crucial to maintaining the trust and reputation of the TLD. Abusive registrations can lead to various issues, including spam, phishing, and other malicious activities. - The proposed extension enables registries to proactively identify and block abusive registrations, thereby improving the overall quality of domain names within the TLD. This can lead to a safer and more reliable internet for end-users. - And contributing to a safer internet.¶

1.3. Scope of the Extension - Verification

This EPP extension focuses on enabling registrars to submit pre-registration data to the registry and receive a registrant quality score based on abuse AI/ML analysis. It does not address other aspects of domain registration, such as pricing or dispute resolution.¶

4.1. Extension Overview

5.1. New EPP Commands

This extension introduces new EPP commands to facilitate pre-registration data submission and quality verification. The following commands are defined within the extension: ### "create" Command Extension Command Name: "create" (Extended) Purpose: To create a new domain registration while including additional XML elements for registrars to submit pre-registration data. Registrars can provide information such as the intended use of the domain and other relevant details. XML Element: <pre-registration-data> - This element encapsulates the pre-registration data submitted by the registrar. Usage: Registrars initiate the "create" command with the pre-registration data, which is then stored by the registry for later analysis. ### "verify" Command¶

Command Name: "verify" (New) Purpose: To trigger the quality verification process for pre-registration data that has been submitted. Registrars can initiate this command after an initial "create" request. XML Element: N/A Usage: After pre-registration data is submitted through the "create" command, registrars can use the "verify" command to request the registry's AI/ML analysis and obtain a registrant quality score.¶

5.2. XML Schema Definitions

To support these new EPP commands, the extension defines the XML schema elements necessary for encapsulating pre-registration data, ensuring interoperability between EPP clients and servers.¶

TBD¶

6.1. Extended "create" Command for Pre-Registration and Quality Verification

This section outlines the extension of the existing "create" EPP command to accommodate the pre-registration data submission and quality verification process. The extended "create" command enables registrars to provide additional information related to the intended use of the domain name, facilitating quality assurance within the top-level domain (TLD).¶

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
       <create>
         <!-- Domain creation data -->
         <domain:create>
           <!-- Domain details -->
         </domain:create>
         <!-- Pre-Registration Data -->
         <pre-registration-data>
           <!-- Pre-registration information -->
         </pre-registration-data>
       </create>
     </command>
   </epp>

6.2. Introduction of New Verify EPP Commands

New "verify" Command: A new EPP command, "verify" will be introduced to trigger the quality verification process on the submitted pre-registration data. Registrars can use this command after the initial "create" request. It's important to note that the time to respond to the verify command is important to take in account, should be in the order of seconds and not minutes.¶

6.3. Command Flow Overview

Command Flow: The process begins with a registrar initiating a "create" command with additional pre-registration data. The registry, upon receiving the request, stores the data for further analysis. Once the data is collected, the registrar can initiate the "verify" command to trigger the quality verification process, which results in the assignment of a quality score. By mapping the EPP verify commands to the new registration process, it demonstrate how the new extension fits into the existing EPP framework and how it can facilitate the pre-registration data submission and quality verification.¶

7.1. Pre-Registration Data Submission Flow

The command flow within the EPP protocol extension for pre-registration and quality verification is a series of interactions between the registrar and the registry. This section outlines the steps involved in submitting pre-registration data and initiating the quality verification process:¶

Step 1: Registrar Initiates "create" Command¶

The process begins when a registrar initiates a modified "create" command, extending the EPP protocol. This command is used to request the creation of a new domain registration.¶

Step 2: Registrar Includes Pre-Registration Data¶

Within the "create" command, the registrar includes the <pre-registration-data> XML element. This element encapsulates the pre-registration information, such as the intended use of the domain and any other relevant data.¶

Step 3: Registry Receives and Stores Pre-Registration Data¶

The registry, upon receiving the "create" command, stores the pre-registration data associated with the domain name in question. This data is queued for subsequent quality verification.¶

7.2. Quality Verification Flow

After pre-registration data is successfully submitted through the "create" command, the quality verification process can be initiated by the registrar. Here's how the flow continues:¶

Step 4: Registrar Initiates "verify" Command¶

After the pre-registration data has been stored, the registrar initiates the "verify" command, a new EPP command introduced by this extension.¶

Step 5: Registry Triggers Quality Verification¶

Upon receiving the "verify" command, the registry's system is triggered to initiate the quality verification process. This process involves AI/ML analysis of the pre-registration data.¶

Step 6: AI/ML Analysis and Quality Score Calculation¶

The registry's AI/ML algorithms analyze the pre-registration data to assess its quality. This analysis considers factors such as the nature of the registration, the intended use of the domain, and other relevant data. Based on the analysis, the system calculates a registrant quality score.¶

Step 7: Registry Provides Quality Score¶

The registry sends the registrant quality score as part of the "verify" command response to the registrar. The score indicates the perceived quality of the registration, with values ranging from 0 for non-abusive registrations to 100 for potentially abusive ones.¶

Step 8: Registrar Takes Action Based on Quality Score¶

Depending on the quality score received, the registrar can make informed decisions regarding the acceptance, rejection, or further review of the domain registration request.¶

8.1. Score 0 - 20 (Non-Abusive):

8.2. Score 21 - 40 (Low Suspicion):

8.3. Score 41 - 60 (Moderate Suspicion):

8.4. Actionable Actions:

• The registration raises moderate suspicion.¶

• Some elements in the registration data seem incongruent or questionable.¶

• Investigate further and consider additional verification steps.¶

• Suspend the registration at the Registry? (after Registrar registration)¶

8.5. Score 61 - 80 (High Suspicion):

8.6. Score 81 - 99 (Very High Suspicion):

8.7. Score 100 (Absolutely Malicious):

8.8. Error Handling

TBD¶

8.9. Registration Timing Considerations

This process has to be quick, if too slow a timer must be defined to mark the registration verification as incomplete, need a specific workflow¶