RPM-IRT

Download

rpm-irt@icann.org

March 2026

2 participants
1 discussions

Update on Implementation of URS Rec #8 (Group 5)
by Antonietta Mangiacotti March 3, 2026

March 3, 2026

Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 5 recommendations. This group includes one recommendation, URS Final Recommendation<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpm-phase…> #8: “The Working Group recommends that the ICANN org establishes a compliance mechanism or mechanisms to ensure that URS Providers, Registries, and Registrars operate in accordance with the URS rules and requirements and fulfill their role and obligations in the URS process. The Working Group recommends that such compliance mechanism(s) should include an avenue for any party in the URS process to file complaints and seek resolution of noncompliance issues. As implementation guidance, the Working Group recommends that the IRT consider: * Investigating different options for potential compliance mechanism(s), such as ICANN Compliance, other relevant department(s) in ICANN org, a URS commissioner at ICANN org, a URS standing committee, etc. * Developing metrics for measuring performance of URS Providers, Registries, and Registrars in the URS process.” Below is a summary of the work that was undertaken to implement a compliance process for handling complaints concerning potential non-compliance by URS Providers, registries, or registrars with their procedural obligations under the URS Rules and Procedure. URS Complaint Process and Metrics Overview As part of implementing this recommendation, ICANN org drafted a document<https://itp.cdn.icann.org/en/files/registry-operators/urs-complaint-process…> titled “URS Complaint Process and Metrics Overview.” This document has been published on the URS homepage<https://www.icann.org/en/contracted-parties/registry-operators/services/rig…> at ICANN.org and outlines the processes for addressing complaints related to non-compliance by URS Providers, registries, or registrars. This document is intended to clarify the distinct processes ICANN uses to assess and respond to URS-related complaints and to enhance transparency regarding how reported issues are reviewed and addressed. It is also intended to serve as an informational resource for any party involved in the URS process who is seeking guidance, assistance, or additional information on the URS complaint process at ICANN. URS Complaint Process for URS PROVIDER Non-Compliance ICANN org has established a new complaint process enabling parties involved in the URS process to submit complaints concerning non-compliance by URS Providers with their procedural obligations. Complaints regarding URS Providers may now be submitted via the URS homepage<https://www.icann.org/en/contracted-parties/registry-operators/services/rig…> on ICANN.org by selecting the new “Uniform Rapid Suspension (URS) Provider Complaint” link, or they may continue to be submitted directly via the Global Support Center<https://www.icann.org/en/help#global-support-centers> page. Both webpages have also been updated to include a dedicated section for submitting such complaints, which are routed through a newly established internal process. In addition, performance metrics for URS Providers – such as the number of complaints received and the nature of the complaints – will be published on the URS homepage as data becomes available. Further details are provided in the URS Complaint Process and Metrics Overview document<https://itp.cdn.icann.org/en/files/registry-operators/urs-complaint-process…>. URS Complaint Process for REGISTRAR or REGISTRY OPERATOR Non-Compliance Complaints submitted through this mechanism are handled through ICANN’s Contractual Compliance processes. ICANN Contractual Compliance already maintains a dedicated form<https://icann-nsp.my.site.com/compliance/s/urs> for complaints regarding registry operator non-compliance with the URS procedure. The Generic Registrar Complaint Form<https://icann-nsp.my.site.com/compliance/s/generic-registrar> should continue to be used for registrar-related complaints and includes a category for URS-related concerns. Both forms are routed to the appropriate ICANN Contractual Compliance team for review and resolution. More details about ICANN's Contractual Compliance approach and processes may be found here<https://www.icann.org/resources/pages/approach-processes-2012-02-25-en>. However, to enhance clarity and accessibility, the “Dispute Resolution Policies & Procedures” section of the ICANN Compliance complaint submission page<https://www.icann.org/compliance/complaint> has been updated to include a link to the Generic Registrar Complaint Form beneath the Registry URS Complaint Form link. The “About URS Compliance” page<https://www.icann.org/resources/pages/urs-2013-10-31-en> has also been updated to reference registrar-related complaints and to link to the Generic Registrar Complaint Form. These updates are intended to reduce confusion regarding enforcement and to make clear that concerns or complaints relating to URS obligations, including those involving registrars, will be reviewed and addressed through the appropriate compliance channels. ICANN Compliance also continues to publish URS-related metrics for registries and registrars on the ICANN Compliance page<https://compliance-reports.icann.org/compliance/dashboard/report-list.html>. These metrics include the number of complaints received, the number of complaints closed prior to a first inquiry or notice, and the number of complaints closed by closure code (i.e., the reason for closure). Additional details regarding these processes and associated metrics are available in the URS Complaint Process and Metrics document<https://itp.cdn.icann.org/en/files/registry-operators/urs-complaint-process…>. Please also note that we plan to provide an update next month on the status and/or completed items in Group 4 related to the Overarching Data Collection recommendation<https://icann-community.atlassian.net/wiki/download/attachments/108757543/R…>. We hope this update is helpful. Please do not hesitate to reach out if you have any questions regarding the information above. Thank you! Best, Antonietta

2 3