October 2025 - RPM-IRT - lists.icann.org

Re: Update on Implementation of URS Recommendation #12 (Group 3)
by Antonietta Mangiacotti Oct. 8, 2025

Oct. 8, 2025

Hi Roger, Thank you for your message. We are currently checking internally regarding your question on Registrar access to Registry URS Contacts in NSp. We’ll get back to you as soon as we have more clarity. Best, Antonietta From: rcarney--- via RPM-IRT <rpm-irt(a)icann.org> Reply-To: "rcarney(a)godaddy.com" <rcarney(a)godaddy.com> Date: Tuesday, October 7, 2025 at 12:50 PM To: "rpm-irt(a)icann.org" <rpm-irt(a)icann.org> Subject: [RPM-IRT] Re: Update on Implementation of URS Recommendation #12 (Group 3) Good Afternoon, Thanks Antonietta for the continued updates as we make progress. I will admit that I do not access NSp unless I am told to, so I wanted to get clarity on Registrar access to Registry URS Contacts. Specifically, do/should Registrars have access to Registry URS Contacts in NSp? I don't think this is technically required by Rec 12/URS Procedures paragraph 4, but it is the only link that this not mentioned below between the three parties (Provider/Registry/Registrar). Thanks Roger ________________________________ From: Antonietta Mangiacotti via RPM-IRT <rpm-irt(a)icann.org> Sent: Tuesday, October 7, 2025 1:25 PM To: rpm-irt(a)icann.org <rpm-irt(a)icann.org> Cc: Eduardo Duarte <eduardo.duarte(a)icann.org> Subject: [RPM-IRT] Update on Implementation of URS Recommendation #12 (Group 3) Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 3 recommendations. This group includes one recommendation, URS Final Recommendation #12: “The Working Group recommends that the ICANN org, Registries, ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 3 recommendations. This group includes one recommendation, URS Final Recommendation<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> #12: “The Working Group recommends that the ICANN org, Registries, Registrars, and URS Providers take appropriate steps to ensure that each other’s contact details are up to date in order to effectively fulfill the notice requirements set forth in the URS Procedure paragraph 4.” Below is a summary of the work that was undertaken to ensure all relevant parties have access to accurate and current contact information in order to ensure the efficacy of the URS process. 1. URS Providers → Registrars (New Process) On 30 September 2025, ICANN org launched a new process to allow URS Providers to download, on a daily basis, the Registrar URS Primary and Secondary contact information by downloading a Comma-Separated Values (CSV) file containing the relevant details. The new file will be updated every six hours with the latest contact information available to ensure that URS Providers have up-to-date information. This process is facilitated through the Naming Services portal<https://urldefense.com/v3/__https:/www.icann.org/en/contracted-parties/accr…> (NSp), where new URS contact roles—specifically, URS Primary and Secondary Contacts—were introduced. These fields were pre-populated using the registrar’s Uniform Domain Name Dispute Resolution (UDRP) Primary and Secondary contact data. ICANN org communicated the creation of these new roles to the Registrars on 27 May 2025<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/contracted-pa…>. Registrars were also reminded that per the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/t…>, Accredited Registrars are required to maintain the URS contact information up to date for the purpose of receiving URS communications. Registrars who wish to review or make any changes to their URS Primary or Secondary contact information in the NSp, can submit a Contact Update Request in the portal. In addition, please note that the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/t…> already included the steps for this process (see page 7). Since the process has now been created, there is no need to update the existing requirements. 1. Registries → Registrars (New Process) Registry Operators will also be able to access the Registrar URS Primary and Secondary contact information saved in NSp. The communication sent to registrars regarding the Registrar URS Contact Information—now available to URS Providers and gTLD Registry Operators—will be posted here<https://urldefense.com/v3/__https:/www.icann.org/en/contracted-parties/comm…>. 2. URS Providers → Registries (Existing Process) URS Registry Operator contact information is already available in NSp, and URS Providers currently have the ability to download these details. In addition, the functionality mentioned above to submit contact update requests for URS roles already exists for Registry Operators; therefore, a new process for URS Providers to obtain up to date URS Registry Operator contact information is not being developed. However, the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/t…> will need to further be revised to reflect the existing process, and will be shared with the IRT for review. In addition, please note that the process for URS Providers to access Registrars’ URS contact information (see item #1) was modeled after this existing process used for URS Registry Operator contacts. Please note that ICANN communicates with contracted parties and URS Providers regarding URS-related matters through established channels, including direct correspondence via account managers. Additionally, both ICANN and contracted parties can access the URS Providers' contact information through the URS page on the ICANN website, which provides links to the various URS Provider websites: https://www.icann.org/urs-en<https://urldefense.com/v3/__https:/www.icann.org/urs-en__;!!Hj18uoVe_Lnx!s7…>. Please let us know if you have any questions related to the information above. Thank you! Best, Antonietta

1 0

Update on Implementation of RPM Phase 1 Recommendations
by Antonietta Mangiacotti Oct. 8, 2025

Oct. 8, 2025

Dear RPM IRT, We wanted to provide a written update on the progress of implementing the RPM Phase 1 Recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpm-phase…>. Additionally, we’d like to clarify that although an RPM IRT session was initially scheduled for ICANN84, we’ve concluded that, given the current stage of our work, it would be more productive to connect individually while in Dublin. Accordingly, we will not be holding a formal session, but we will be on site and are happy to meet informally if you’d like to discuss any of the items below in more detail. As you may be aware, we have completed implementation of the recommendations in Groups 2 and 3, which focused on developing educational materials to support RPM users and updating URS contact data. However, work on some of the remaining recommendation groups is still ongoing, as outlined below. Group 1 – Updates to RPM Procedural Documents * TM-PDDRP: As noted in our message on 2 May 2025<https://lists.icann.org/hyperkitty/list/rpm-irt@icann.org/thread/5VLXHHIMEJ…>, the revised TM-PDDRP is now available here<https://www.icann.org/pddrp-en>. * URS: While the URS Rules<https://docs.google.com/document/u/1/d/1dC3BIYxnIb2zZks1AOnrUNEkQJCzi8EKaCA…> and Procedure<https://docs.google.com/document/u/1/d/1qY-NdwBTULoRaXoE6MQEOj_-61sBbpH_Y_t…> are ready for publication, the URS High Level Requirements<https://docs.google.com/document/d/1mDCOzxDCeGJSCK76a_lW7WMiiBAGUHAbXznYBtF…> still require the following updates: 1) OpenPGP Requirements: Updating the OpenPGP requirements in the URS High Level Requirements to align with the IETF’s recently adopted OpenPGP standard in RFC 9580. ICANN org’s technical services team is currently working with URS Providers to assess the complexity of implementing these changes. 2) URS Registry Contact Process: Reflecting the current process that allows URS Providers to download up-to-date URS Registry Operator contact information. Although already in practice, this had not been incorporated into the URS High Level Requirements. Once the revisions above are incorporated into the IRT version<https://docs.google.com/document/d/1mDCOzxDCeGJSCK76a_lW7WMiiBAGUHAbXznYBtF…> of the URS High Level Requirements, we will share the updated URS High Level Requirements with you for review. After that, we will move forward with publishing the URS Rules, Procedure, and High Level Requirements. Publishing all three documents — the URS Rules, Procedure, and URS High Level Requirements — together will ensure consistency and clarity across the full set of requirements. ➤ Estimated Timing: We anticipate sharing the redlines for your review and publishing the URS Rules, Procedure, and High Level Requirements by Q1 2026. * TMCH Requirements: Because the Next Round team is working on additional updates to the TMCH Requirements (e.g., terminology updates for consistency with the Base Registry Agreement, Launch Program adjustments, and other efficiency/operational enhancements<https://icann.zoom.us/rec/play/2aK3B9qdweAsp4l7uvt4qoEujym6-9Jj6hD7udkS4oEq…>), publication of the revised TMCH Requirements will be postponed to Q1 2026 to ensure they are available prior to the opening of the next round. Bundling these changes together will ensure a more comprehensive and streamlined update. Please note: The agreed-upon changes<https://docs.google.com/document/d/1qCYlcGzrMoVLlyRIIhZJIsS0DrAZCUpKOSVDLUl…> with the RPM IRT—specifically, those resulting from Trademark Claims Final Recommendations 2, 5, and 6—will remain unchanged. ➤ Estimated Timing: We anticipate publishing the revised TMCH Requirements Q1 2026. Group 2 – Development of RPM Educational Materials ✅ Complete (See our note from 25 April 2025<https://lists.icann.org/hyperkitty/list/rpm-irt@icann.org/thread/36Y2L2O553…>) Group 3 – Development of URS Contact Data Process ✅ Complete (See our note from 7 October 2025<https://lists.icann.org/hyperkitty/list/rpm-irt@icann.org/thread/P3GV2ETNPF…>) Group 4 – Collection of RPM Data * TMCH Data: As noted in our 21 May 2025<https://lists.icann.org/hyperkitty/list/rpm-irt@icann.org/thread/A7MHBNLYZI…> update, we collaborated with the TMCH Validation Provider (Deloitte) to include the number of abused labels in the TMCH Monthly Reports<https://newgtlds.icann.org/en/about/trademark-clearinghouse/registries-regi…> published on ICANN.org. ➤ Estimated Timing: This data point will first appear in the July 2025 report, which will be published here<https://newgtlds.icann.org/en/about/trademark-clearinghouse/registries-regi…> in November 2025 due to contractual requirements that delay publication until three months after the end of the reporting month. * Trademark Claims Data Reporting: ICANN org is actively working to define the key data points to be included in the Trademark Claims data reports, determine an appropriate reporting frequency, and identify the tool or platform to be used for publishing the data. ICANN org will also work with ICANN-accredited registrars to begin publishing periodic reports—at least annually—on the number of Trademark Claims Notices sent to prospective registrants. ➤ Estimated Timing: We anticipate sharing a proposal for this work with the RPM IRT by Q1 2026. * Publication and Search of URS Determinations: ICANN org collaborated with URS Providers to develop a proposal to standardize the publication and search of URS determinations that aligns with the operational capabilities of the URS Providers. The proposal includes an agreed upon common set of data fields used by all providers and using consistent terminology (e.g., “Disputed Domain Name(s)”). ➤ Estimated Timing: Providers are requested to implement these changes by 30 January 2026. * Survey of Trademark Owners’ and Registrants’ Experience with RPMs: On 22 August 2024, ICANN org issued a request for proposal (RFP<https://www.icann.org/en/announcements/details/icann-request-for-proposal-d…>) to select provider(s) to survey domain name registrants, Internet end-users, and trademark holders. The surveys have since been conducted, and the resulting reports are currently pending publication. ➤ Estimated Timing: These reports are scheduled for publication Q4 2025. Group 5 – New Compliance Mechanism(s) * ICANN org is currently drafting a proposed process for handling complaints related to non-compliance by URS Providers, Registrars, or Registries with their procedural obligations under the URS Rules and Procedure. This includes identifying appropriate metrics for assessing compliance and consulting with relevant internal departments. ICANN org is also engaging with URS Providers to understand what complaint-handling mechanisms they already have in place, which will help inform the development of an effective and coordinated approach. ➤ Estimated Timing: The new process is expected to be shared with the RPM IRT and published in Q1 2026. Given the estimated timelines above, we expect to conclude work on most of the listed items by Q1 2026. For additional information, please also refer to the RPM Phase 1 Estimated Timeline<https://docs.google.com/presentation/d/12YPqNvEnnLR4UaqZWCSm89we6k1EjOqvOjW…> and the Implementation Plan<https://icann-community.atlassian.net/wiki/spaces/RPMIRT/pages/108757543/Im…>. Please feel free to reach out with any questions or to schedule time with us. Thank you! Best, Antonietta

1 0

Update on Implementation of URS Recommendation #12 (Group 3)
by Antonietta Mangiacotti Oct. 7, 2025

Oct. 7, 2025

Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 3 recommendations. This group includes one recommendation, URS Final Recommendation<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpm-phase…> #12: “The Working Group recommends that the ICANN org, Registries, Registrars, and URS Providers take appropriate steps to ensure that each other’s contact details are up to date in order to effectively fulfill the notice requirements set forth in the URS Procedure paragraph 4.” Below is a summary of the work that was undertaken to ensure all relevant parties have access to accurate and current contact information in order to ensure the efficacy of the URS process. 1. URS Providers → Registrars (New Process) On 30 September 2025, ICANN org launched a new process to allow URS Providers to download, on a daily basis, the Registrar URS Primary and Secondary contact information by downloading a Comma-Separated Values (CSV) file containing the relevant details. The new file will be updated every six hours with the latest contact information available to ensure that URS Providers have up-to-date information. This process is facilitated through the Naming Services portal<https://www.icann.org/en/contracted-parties/accredited-registrars/resources…> (NSp), where new URS contact roles—specifically, URS Primary and Secondary Contacts—were introduced. These fields were pre-populated using the registrar’s Uniform Domain Name Dispute Resolution (UDRP) Primary and Secondary contact data. ICANN org communicated the creation of these new roles to the Registrars on 27 May 2025<https://itp.cdn.icann.org/en/files/contracted-parties-communications/nsp-ch…>. Registrars were also reminded that per the URS High-Level Technical Requirements<https://newgtlds.icann.org/sites/default/files/tech-requirements-21feb24-en…>, Accredited Registrars are required to maintain the URS contact information up to date for the purpose of receiving URS communications. Registrars who wish to review or make any changes to their URS Primary or Secondary contact information in the NSp, can submit a Contact Update Request in the portal. In addition, please note that the URS High-Level Technical Requirements<https://newgtlds.icann.org/sites/default/files/tech-requirements-21feb24-en…> already included the steps for this process (see page 7). Since the process has now been created, there is no need to update the existing requirements. 1. Registries → Registrars (New Process) Registry Operators will also be able to access the Registrar URS Primary and Secondary contact information saved in NSp. The communication sent to registrars regarding the Registrar URS Contact Information—now available to URS Providers and gTLD Registry Operators—will be posted here<https://www.icann.org/en/contracted-parties/communications>. 2. URS Providers → Registries (Existing Process) URS Registry Operator contact information is already available in NSp, and URS Providers currently have the ability to download these details. In addition, the functionality mentioned above to submit contact update requests for URS roles already exists for Registry Operators; therefore, a new process for URS Providers to obtain up to date URS Registry Operator contact information is not being developed. However, the URS High-Level Technical Requirements<https://newgtlds.icann.org/sites/default/files/tech-requirements-21feb24-en…> will need to further be revised to reflect the existing process, and will be shared with the IRT for review. In addition, please note that the process for URS Providers to access Registrars’ URS contact information (see item #1) was modeled after this existing process used for URS Registry Operator contacts. Please note that ICANN communicates with contracted parties and URS Providers regarding URS-related matters through established channels, including direct correspondence via account managers. Additionally, both ICANN and contracted parties can access the URS Providers' contact information through the URS page on the ICANN website, which provides links to the various URS Provider websites: https://www.icann.org/urs-en. Please let us know if you have any questions related to the information above. Thank you! Best, Antonietta

2 1