Hello All, To follow up my original message about the reason for cancelling the meeting, please see a series of follow-up questions to ICANN Compliance on page of 11 of our working document here: https://docs.google.com/document/d/1SQWM4qVGm-JuueGa5VdyLbCcZWkXiG1m0eczWtzO... We have tried to capture the essence of this team’s conversation last week and distill them into a series of questions. Note, the purpose of the questions is to provide ICANN Compliance with a sense of what this team will want to speak about and to prepare as they see fit. However, the Compliance folks joining next week’s meeting understand that their participation is intended to be conducted as a dialogue, so questions will not be limited to just what is shared in advance. Please review the draft questions and provide any input you may have by 23:59 UTC on 27 May, after which we will share with compliance. To reiterate, the questions are mere guidance/advance notice, so don’t feel that the questions need to be perfect, nor exhaustive. Hope this all makes sense and if you have any questions, please do not hesitate to ask! Best, Steve From: Marika Konings <marika.konings@icann.org> Date: Wednesday, May 25, 2022 at 1:01 AM To: Steve Chan <steve.chan@icann.org>, "gnso-dnsabuse-smallteam@icann.org" <gnso-dnsabuse-smallteam@icann.org> Subject: Re: [gnso-dnsabuse-smallteam] 25 May Meeting Cancelled In addition, we also wanted to give you some advance warning on the expected next steps in relation to the input review document. The staff support team has gone through the notes of the conversation to date and identified proposed follow up questions for the team’s consideration which aim to facilitate the development of possible recommendations (see attached). Following the review of the compliance responses and the engagement with our ICANN Compliance colleagues, we would go back to the input review document and focus on the questions identified in yellow. Note that for each of the comments, a short overview of the small team’s discussion has also been included that is intended to show those that provided the input how it was considered. Of course, following the conversation with Compliance, further updates to this document may be in order, but we wanted to already give you a preview so you can keep this in the back of your mind as you review the Compliance responses and prepare for the discussion. Eventually we will upload this document as a google doc so you can provide any additions / edits you may have, but for now, please focus your attention on the Compliance responses and possible follow up questions to Compliance. Best regards, Marika From: gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam-bounces@icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Wednesday, 25 May 2022 at 00:39 To: "gnso-dnsabuse-smallteam@icann.org" <gnso-dnsabuse-smallteam@icann.org> Subject: [gnso-dnsabuse-smallteam] 25 May Meeting Cancelled Hello All, You will have just seen that the meeting on 25 May was just cancelled. Apologies for the late notice. The reason for cancellation is that staff was working with our ICANN Compliance colleagues to have them join an upcoming small team call to have a dialogue. Based on their availability, they will be joining our 1 June call. In the meantime, we can refine some follow-up questions before the end of this week to aid them in their preparation, acknowledging of course additional questions will likely arise during the course of the meeting itself. Stay tuned for draft questions, where your input will of course be welcomed and encouraged. Best, Steve Steven Chan Senior Director, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...>