Dear Working Group members, Please find below the action items and discussion notes from today’s meeting. These high-level notes are designed to help Working Group members navigate through the content of the call and are not a substitute for the chat room or the recording. The meeting recording and transcripts will soon be available at: https://community.icann.org/x/CtTRAw. Kind regards, Emily ====================================== 1) Welcome/SOIs - no updates 2) Work Track Updates - WT1 - next meeting is today at 20:00 UTC. The group will review progress and next steps for the WT and then focus on RSP Program requirements document. - WT2 - next meeting scheduled for this Thursday at 21:00 UTC, which will likely focus on Global Public Interest. This will be the list topic to introduce in this WT. The final session before ICANN59 will likely focus on Vertical Integration. - Question - what is the status of WT discussion on VI? - Response - the topic was introduced - focus: were anticipated benefits realized? If not, how can they be? Were possible anticipated harms observed? If so, how can they be mitigated? - WT3 - recent conversations focused on Community Applications and CPE. The next meeting will focus on Accountability Mechanisms. It will be on June 6 at 20:00 UTC. - Question - what is the scope of work around Accountability Mechanisms for this group? - Response - Want to take a broad look initially at accountability mechanisms in the gTLD Program and whether they are sufficient. The current measures mostly look at process rather than substance. Some may want to see mechanisms that also go to the substance of a decision. - WT4 - Last call was on Thursday, included a presentation from Patrik Fältström on SSAC Reports and Advisories. Upcoming call will take place next Thursday 8 June at 20:00 UTC. Overall plan for WTs: - The issues have been introduced through "blue sky" conversations in the Work Tracks. As groups finish this cycle, they will go through a second cycle to go through CC2 comments and come to their initial views. There will be a third pass before it comes back to the full group -- WTs will determine whether there is consensus for changing something and what should be changed. This will be documented for the full group to discuss further. WTs will go dormant, but the full group may ask WTs to revisit certain topics at a later point. 3) Update - Community Comment 2 - 25 comments received, cross section of the community submitted input. - Staff is preparing a summary document to be ready for 5 June document deadline for ICANN59. 4) Update and Discussion – GDD response to select questions from GDD Summit - Question raised at GDD Summit - what information does ICANN org need to take next steps towards subsequent procedures? Information requested from ICANN org: -- Will applications will be processed in rounds or first-come first-served? -- RSP Certification/Accreditation – Is the WG recommending that there will a program? - Time needed to prepare for upcoming procedures depends on the answer to these questions. - Once final recommendations are available, they will go the Board and if approved, will go to ICANN org for implementation. - Next step for Continuous Data-Driven Analysis of Root Server System Stability (CDAR) report – is ICANN Board consideration. - Results of Board consideration of the CDAR Report will impact this PDP. - The report will likely be considered in the Board's June meeting, but Trang will confirm. - Concern raised about first-come first-served approach to application processing -- this issue should be considered carefully with pros and cons explored. Chat excerpt: Ken Stubbs: First come- first served can be easily "gamed" Greg Shatan: I also have deep concerns regarding first come, first served. - This is one of the pending CC1 issues and the topic of a drafting team. Nothing has yet been decided. All are welcome to join and participate in drafting teams. 5) Drafting Team Update – Framework for Community Engagement and Predictability (https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H81...) - This document is still in draft form and needs additional feedback from WG members. - This is a form of change control document. - This framework seeks to provide a predictable and clear way to handle changes if they come up after program launch or in implementation. - It may be helpful to have a discussion about the scope of the document. - Outstanding question to address: once the IRT completes its work, who is the right party to address changes and how they will be handled. - There is some guidance in Bylaws and Operating Procedures on how to handle changes at this stage. - Is it prescribed when an IRT ends? - When is it appropriate for a change to go out for public comment? - What would be potential parameters around "freezing" changes at a certain point? - Question: would the WG like feedback from ICANN org from an implementation feasibility perspective? - Response: feedback is welcome at any time in the document. - The topic of application change requests may be something for this WG to consider. 6) AOB