Greeting RPM IRT members,

Thanks to everyone that was able to attend our last meeting. Please take a moment to share your availability for the next 4 RPM IRT meetings and review the suggested action items / next steps provided below.

Availability:

Please use these doodle poll links to share your availability:

Meeting 11: https://doodle.com/meeting/participate/id/elMPzZ6a (17:00 - 18:00 UTC)

Meeting 12 https://doodle.com/meeting/participate/id/e51XnWve (17:00 - 18:00 UTC)

Meeting 13: https://doodle.com/meeting/participate/id/elMNQ85a (17:00 - 18:00 UTC)

Meeting 14:https://doodle.com/meeting/participate/id/azxyPx8d (17:00 - 18:00 UTC)

Action Items:

During meeting #10, the group discussed the need to seek further input from various groups to enhance clarity and accessibility of the Claims Notice in Exhibit A and B. In its implementation guidance, the Working Group advises that the IRT use appropriate flexibility and consider whether it believes it will be helpful to solicit input from resources internal and/or external to the ICANN community as the IRT deems necessary and appropriate.

• We invite RPM IRT members to engage with the stakeholder groups they represent to ask for any additional input on Claims Notice Language and Educational Materials where they believe it is appropriate. Please provide any input by June 20th. Following this, we will work with the ICANN communications team to assess the documents and share with the RPM IRT for its review prior to Meeting #12.

• Please also review proposed edits related to URS Rules - Section 12 “Default” prior to meeting #11

Next Steps:

• ICANN will assemble a summary of the discussion, community positions, ICANN assessment, and proposed next steps related to the discussion on URS Rules Section 3.3 and amendments to URS complaints.
• ICANN will also assemble the process/workflow to show how/where complaints amendments fit into the overall URS Complaint process to help inform the discussion.
• ICANN will distribute these documents with the RPM IRT for consideration and discussion. If a consensus is not reached during the next RPM IRT call, we will suggest asking Susan Payne to identify if this is something that needs to be taken to the GNSO Council per the GDD Policy Implementation Framework (Section 3E):  As such, the IRT is expected to serve as a resource to staff on the background and rationale of the policy recommendations and return to the GNSO Council for additional guidance as required.

Thank you,

Sherwood Moore