I want echo Sarah’s comments. Working with this team of dedicated, passionate individuals has been a great opportunity. A special thank you to ICANN staff who always strive towards compromise and progress and provided the team with levels of expertise and support that can’t be matched. All the best, Beth From: IRT.RegDataPolicy <irt.regdatapolicy-bounces@icann.org> on behalf of Sarah Wyld via IRT.RegDataPolicy <irt.regdatapolicy@icann.org> Date: Friday, August 11, 2023 at 9:13 AM To: Dennis Chang <dennis.chang@icann.org>, Roger D Carney via IRT.RegDataPolicy <irt.regdatapolicy@icann.org> Subject: [EXTERNAL] Re: [IRT.RegDataPolicy] Next steps with Policy Language for publicationin August 2023. CAUTION: This email came from outside your organization. Don’t trust emails, links, or attachments from senders that seem suspicious or you are not expecting. ________________________________ Hello Dennis and everyone on the IRT and IPT teams, What exciting news, it's so great that we have successfully concluded this implementation work. Thank you all so much for this educational and wonderfully challenging and fulfilling experience as we worked together to implement these policy recommendations. I have appreciated collaborating with and learning from you, and look forward to working together on other projects in the future. All the best, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld@tucows.com<mailto:swyld@tucows.com> From: Dennis Chang via IRT.RegDataPolicy<mailto:irt.regdatapolicy@icann.org> Sent: August 7, 2023 7:19 PM To: Roger D Carney via IRT.RegDataPolicy<mailto:irt.regdatapolicy@icann.org> Subject: [IRT.RegDataPolicy] Next steps with Policy Language for publicationin August 2023. Dear IRT, On 24 July 2023, we posted the complete Registration Data Policy language after the IRT meeting where we found a compromised solution to the Urgent Request. (24 July 2023 version<https://protect-us.mimecast.com/s/ir90CQWBo7hlNQYFxwJeu?domain=community.ica...>) We have offered an opportunity for IRT to propose an alternate set of language that could be better in terms of reflecting our agreement and alignment to the recommendation. As of 2 Aug 2023, we received one submission for an alternate policy language regarding Urgent Request. Based on the comments received, it’s clear that the 24 July 2023 version is the one that we should stay with. I have consulted with our GNSO Council Liaison, Sebastien Ducos, and confirmed that we’ve followed our implementation process fully and there is no need for escalation to the GNSO Council. FYI Seb is currently on holiday but was very kind to take my call to support us. This may be a good time for us to be reminded of the IRT Instructions<https://protect-us.mimecast.com/s/cV9eCR6Dp1i0g6xHNCNHx?domain=docs.google.c...> in the IRT workbook when we began our work. Therefore, we believe we are now complete with our policy language and proceeding to ICANN org internal briefing/reviews. We will follow up with IRT afterwards. I am truly grateful to this IRT for resolving the toughest policy requirement item (referred to some as the “unresolvable?") at the IRT to avoid escalation and delays. It’s a demonstration of how well this IRT has worked together towards a common goal. Thank you again for your amazing dedication and support as we continue to strive to achieve our goal of August 2023 Publication. -- Gratefully yours, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<https://protect-us.mimecast.com/s/ErZ4CVOKwQSkPJYsy4RNG?domain=icann.org> One World – One Internet