Dear IRT, Attached is a completed draft of the Registration Data Policy including the last two outstanding sections. Section 4.0: Policy Effective Date reflecting the 6+12 plan for the 18-month implementation timeline. Section 10.6: Urgent Request reflecting the solution supported at the IRT meeting last week. (see email below) I believe we now have a good policy that is aligned with all 34 recommendations we will work together to implement. EPDP Phase 1 recommendations (29) May 2019 EPDP Phase 2 Priority 2 Recommendations (4) June 2021 Supplemental Recommendation (1) March 2022 As we discussed at our last IRT meeting, we don’t plan on more IRT meetings before we publish our policy in August 2023. We’ll notify you of the publication date after we have coordinated with our publication team. We may have more IRT meetings after we publish to coordinate and collaborate our implementation, but that decision will come later. For now, we will focus on getting this policy published. If you have questions or comments, I request they be submitted in separate emails with Subject line defining the topic. It will help us to collect the information as we address them together. Thank you all once again and I hope you all support the attached policy language for publication and implementation. Gratefully your, Dennis Chang From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces@icann.org> on behalf of "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy@icann.org> Reply-To: Dennis Chang <dennis.chang@icann.org> Date: Friday, July 21, 2023 at 8:40 AM To: "irt.regdatapolicy@icann.org" <irt.regdatapolicy@icann.org> Subject: Re: [IRT.RegDataPolicy] RegData IRT Good News. Urgent Request requirement. IRT supported solution found! Dear IRT, If you haven’t heard already, we did it! We found a solution to Urgent Request supported by IRT at our 90 minutes focused working session this week. Thank you so much for not giving up and working as a team to find this solution. It was impressive to see people still listening to one another, appreciating the different views, and truly collaborating to build on ideas to find the compromised solution. A great demonstration of One Team against the problem. What was that solution? * 24 hours. Respond in 24 hours with the info or an explanation for more time needed. * 2 Business Days. No more than 2 Business Days to Respond. How did this happen? First, thanks to Roger and RrSG for the planting the seed with using both 24 hours and 2 business days in the solution. Instead of outright rejecting it, Laureen and others suggested that we build on it. Thomas came in with a key ingredient – the explanation. Initially, we discussed all the options but created this new one listening to the “interest” behind the positions. Business Days was important because of the business realities in various regions around the world. While Calendar Days sets global time consistency, the team agreed that cultural sensitivity to regions was more important. The dread of “silence” with undetermined timeline using “Business Days” was solved with the promise of a response in 24 hours with an explanation. Thanks to Gabriel expressing the “dread” so eloquently. Overall, it was an exciting finale overcoming the toughest challenge for us. As promised, we’ll draft the policy language using the IRT supported requirements and comeback to you, but I wanted to send you this quick note to express my sincere gratitude for wonderfully responding. I thank those guests that joined to support us too. I noted Ashley, RrSG Chair and Becky, ICANN Board and others supporting us behind the scenes. Please convey our sincere appreciation to your team back home too. THANK YOU! Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet