Discontinuation of third level domain registrations for the .name TLD [pdf]

Registry Services Evaluation Policy (RSEP) Request April 15, 2026 Registry Operator VeriSign, Inc. Request Details Case Number: 01581614 This Registry Services Evaluation Policy (RSEP) request form should be submitted for review by ICANN org when a registry operator is adding, modifying, or removing a Registry Service for a TLD or group of TLDs. The RSEP Process webpage provides additional information about the process and lists RSEP requests that have been reviewed and/or approved by ICANN org. If you are proposing a service that was previously approved, we encourage you to respond similarly to the most recently approved request(s) to facilitate ICANN org’s review. Certain known Registry Services are identified in the Naming Services portal (NSp) case type list under “RSEP Fast Track” (example: “RSEP Fast Track – BTAPPA”). If you would like to submit a request for one of these services, please exit this case and select the specific Fast Track case type. Unless the service is identified under RSEP Fast Track, all other RSEP requests should be submitted through this form. | 2 1. PROPOSED SERVICE DESCRIPTION 1.1. Name of proposed service. Discontinuation of third level domain registrations for the .name TLD. 1.2. Provide a general description of the proposed service including the impact to external users and how it will be offered. Currently, third level domain names may be registered in the .name TLD. This RSEP seeks to discontinue third level domain name registrations due to declining usage and limited registrar support of the service. Upon discontinuation, no new third level domain names will be registered and existing third level domain names will be terminated. 1.3. Provide a technical description of the proposed service. Verisign currently registers third level domain names for the .name TLD. For example, string.string.name. ''String'' means any set of allowed characters. Upon discontinuation of third level domain name registrations, EPP transactions will no longer accept any new registrations at the third level for the .name TLD and existing third level domain name registrations will be deleted. 1.4. If this proposed service has already been approved by ICANN org, identify and provide a link to the RSEP request for the same service that was most recently approved. Registrations of third level domain names originated as part of the original 2001 .name Registry Agreement between Global Name Registry (GNR) and ICANN. ICANN did not previously approve an RSEP for this service. 1.5. Describe the benefits of the proposed service and who would benefit from the proposed service. Discontinuation of third level domain name registrations for the .name TLD will increase efficiency for the operation of the .name TLD. 1.6. Describe the timeline for implementation of the proposed service. Following ICANN’s approval of the RSEP, Verisign will provide registrars with a minimum of 90- days prior notice of the discontinuation of third level domain name registrations. Upon expiration | 3 of the notice period, new third level domain name registrations will no longer be accepted for the .name TLD and existing third level domain names will be deleted. Reminder Notice: Verisign will provide an additional reminder notice to registrars at least 30 days prior to discontinuation. Verisign will provide the registrar with customer service support throughout the process. 1.7. If additional information should be considered with the description of the proposed service, attach one or more file(s) below. 1.8. If the proposed service adds or modifies Internationalized Domain Name (IDN) languages or scripts that have already been approved in another RSEP request or are considered pre-approved by ICANN org, provide (a) a reference to the RSEP request, TLD(s), and IDN table(s) that were already approved or (b) a link to the pre-approved Reference Label Generation Rules (LGR). Otherwise, indicate “not applicable.” Not applicable. 2. SECURITY AND STABILITY 2.1. What effect, if any, will the proposed service have on the life cycle of domain names? None. There will not be any effect on the life cycle of domain names. 2.2. Does the proposed service alter the storage and input of Registry Data? No. There will not be an alteration to the storage and input of Registry Data. 2.3. Explain how the proposed service will affect the throughput, response time, consistency or coherence of responses to Internet servers or end systems. There will be no effect on the throughput, response time, consistency or coherence of responses to Internet servers or end systems. 2.4. Have technical concerns been raised about the proposed service? If so, identify the concerns and describe how you intend to address those concerns. | 4 No. Not applicable. 2.5. Describe the quality assurance plan and/or testing of the proposed service prior to deployment. The discontinuation of the service will be internally tested prior to discontinuation. 2.6. Identify and list any relevant RFCs or White Papers on the proposed service and explain how those papers are relevant. Not applicable. 3. COMPETITION 3.1. Do you believe the proposed service would have any positive or negative effects on competition? If so, please explain. No, there will be no effect on competition. 3.2. How would you define the markets in which the proposed service would compete? Not applicable. There will be no effect on the domain name market. 3.3. What companies/entities provide services or products that are similar in substance or effect to the proposed service? None. 3.4. In view of your status as a Registry Operator, would the introduction of the proposed service potentially affect the ability of other companies/entities that provide similar products or services to compete? Not applicable. 3.5. Do you propose to work with a vendor or contractor to provide the proposed service? If so, what is the name of the vendor/contractor and describe the nature of the services the vendor/contractor would provide. | 5 No. Not applicable. 3.6. Have you communicated with any of the entities whose products or services might be affected by the introduction of your proposed service? If so, please describe the communications. No. Not applicable. 3.7. If you have any documents that address the possible effects on competition of the proposed service, attach them below. ICANN will keep the documents confidential. 4. CONTRACTUAL PROVISIONS 4.1. List the relevant contractual provisions impacted by the proposed service. This includes, but is not limited to, Consensus Policies, previously approved amendments or services, Reserved Names, and Rights Protection Mechanisms. Section 7.2, Section 7.3(a), Appendix 5A, Appendix 7, Appendix 8A, and Appendix 11 to the .name Registry Agreement reference third level domain name registrations. As discussed with ICANN during the consultations, Verisign will seek revisions to these provisions following discontinuation of the service for existing registrars. 4.2. What effect, if any, will the proposed service have on the reporting of data to ICANN? Upon discontinuation of the service, third level domain name registrations will no longer be reported in the .name ICANN Monthly Transactions Report. 4.3. What effect, if any, will the proposed service have on Registration Data Directory Service (RDDS)?* None. 4.4. What effect, if any, will the proposed service have on the price of a domain name registration? None. | 6 4.5. Will the proposed service result in a change to a Material Subcontracting Arrangement (MSA) as defined by the Registry Agreement? If so, identify and describe the change. Please note that a change to an MSA requires consent from ICANN org through the MSA change request process. The RSEP request must be approved prior to submitting the MSA change request. No. 5. AUTHORIZATION LANGUAGE 5.1. A Registry Agreement (RA) amendment is required when the proposed service: (i) contradicts existing provisions in the RA or (ii) is not contemplated in the RA and, therefore, needs to be added to Exhibit A of the RA and/or as an appropriate addendum/appendix. If applicable, provide draft language (or a link to previously approved RA amendment language) describing the service to be used in an RA amendment if the proposed service is approved. If an RA amendment is not applicable, respond with “N/A” and provide a complete response to question 5.2.* For examples or for IDN services, you may refer to the webpage for standard RA template amendments for commonly requested Registry Services. References to third level domain name registrations in Section 7.2, Section 7.3(a), Appendix 5A, Appendix 7, Appendix 8A, and Appendix 11 of the .name Registry Agreement must remain until the termination of all third-level domain name registrations. Following ICANN’s approval of the RSEP, Verisign will be authorized to discontinue third-level domain name registrations. No amendment will be required until the service has been discontinued. 5.2. If the proposed service is permissible under an existing provision in the Registry Agreement, identify the provision and provide rationale. If not applicable, respond with “N/A” and provide a complete response to question 5.1. Not applicable 6. CONSULTATION 6.1. ICANN org encourages you to set up a consultation call through your Engagement Manager prior to submitting this RSEP request. This is to help ensure that necessary information is assembled ahead of time. | 7 Identify if and when you had a consultation call with ICANN org. If you did not request a consultation call, provide rationale. Verisign met with ICANN on October 15, 2025,November 4, 2025, and December 16, 2025. 6.2. Describe your consultations with the community, experts, and/or others. This can include, but is not limited to, the relevant community for a sponsored or community TLD, registrars or the registrar constituency, end users and/or registrants, or other constituency groups. What were the quantity, nature, and