I’m really sorry but I said I cannot do that time, I have an IRP-IOT meeting at 1800 UTC on a Tuesday which I chair (not always every week, but often enough that this is not a possible slot for me).

 

Susan Payne
Head of Legal Policy
Com Laude
T +44 (0) 20 7421 8250
Ext 255

 

 

 

Follow us on LinkedIn and YouTube

From: Antonietta Mangiacotti via RPM-IRT <rpm-irt@icann.org>
Sent: 14 January 2025 14:52
To: rpm-irt@icann.org
Subject: [RPM-IRT] Re: [RPM IRT] RPM IRT Updates & Scheduling for Future Meetings

 

Dear RPM IRT,

 

We’d like to follow up on our previous email to inform you that the RPM IRT meetings will now be scheduled biweekly on Tuesdays at 18:00 UTC. As a result, Meeting #14 will take place on Tuesday, 21 January, instead of this week. The invitation will be sent out later this week.

 

Additionally, please find the agenda for the call below, which is also available on the wiki:

 

PROPOSED AGENDA


  1. Review updated RPM implementation timeline
  2. Discuss publication of educational materials (Groups 2)
  3. Continue discussion on next steps on RPM Recommendation URS-1 regarding the scope of amendments to a complaint (URS Rules Section 3(b)(iii))
  4. Continue reviewing the revised Trademark Claims Notice
  5. AOB

 

Please let us know of any questions.

 

Thank you!

 

Best,

Antonietta

 

From: Antonietta Mangiacotti <antonietta.mangiacotti@icann.org>
Date: Monday, January 6, 2025 at 4:47 PM
To: "
rpm-irt@icann.org" <rpm-irt@icann.org>
Subject: [RPM IRT] RPM IRT Updates & Scheduling for Future Meetings

 

Dear RPM IRT,

 

Happy New Year! I hope you all had a restful and enjoyable holiday break.

 

As we prepare to reconvene this month, we would like to provide a recap of the progress made with the work related to the following RPM implementation groups:

 

Group 1: Currently, there are two open implementation items in this group:

 

 

As a reminder, due to the lack of consensus within the IRT regarding the language for URS Rule 3(b), the next step, as per the IRT Principles and Guidelines, is to raise the issue with the GNSO Council liaison at the next IRT meeting. The liaison will assess the level of consensus and determine whether the matter should be brought to the GNSO Council for their consideration at their 13 February meeting. Consequently, the RPM implementation timeline, which had originally targeted the completion of Group 1 items by December 2024, will need to be revised.

 

 

Group 2: All final edits/comments to the educational materials were requested by 6 December 2024, and the document is now considered final. At our next IRT Meeting #14, staff will discuss with the IRT whether it makes sense to proceed with the publication of the educational materials now, or whether it would be preferable to wait until the revised RPM documents (such as the URS and RPM Requirements) are finalized, allowing us to publish everything together as initially planned.

 

Group 3: Staff is currently working with the relevant internal departments on the implementation of URS Recommendation 12, the only recommendation in this group, which calls for stakeholders involved in the URS process to review and update contact data. We will provide an update to the RPM IRT once the details regarding the implementation of this recommendation are finalized.

 

Meeting Schedule:

As mentioned before the holiday break, we would like to establish a recurring schedule for RPM meetings going forward and propose holding them every other week. Please take a moment to review the available options below for Meeting #14 (which will also serve as the time for future IRT meetings) and indicate your availability here: https://doodle.com/meeting/participate/id/eE1G60le

 

 

Lastly, the proposed agenda and materials for RPM IRT Meeting #14 are also available on the wiki page.

 

If you have any questions or need further clarification, please don’t hesitate to reach out to us.

 

Best,

Antonietta & Karen

 


The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com