Sent on behalf of CoChairs Please find below the main conclusions of our deliberations during call #75. The updated document is attached. 1. Address concern expressed by many that escalation timelines are too tight and aggressive by simplifying some decision steps in the process, while ensuring that the issues remain widely discussed within the Community. a. Jordan Carter is tasked to make a proposal along these lines (Note: Text in yellow highlights below should be considered “Pending proposal from Jordan Carter to adjust”) b. Make it mandatory for petitioning party to reach out to SO/ACs to socialize relevant information before Community Forum. c. Removing the mandatory community conference call will allow for extension of timeline if so requested by an SO or AC. Additionally, should the petitioning group need a call, ICANN will provide resources upon request. 2. Acknowledging concern raised by ALAC and others regarding the thresholds adjustment in case the number of Decisional Participant is lower (paragraph 62 – page 12), the group is considering the option to lower the requirement of support for Fundamental Bylaw change only. a. Since the Fundamental Bylaw change process is a requirement for “approval” and not a “rejection” option, this would preserve the requirement for stronger protection of Fundamental Bylaws. (see page 11) b. Note was made that this approach was still raising some concerns 3. The use of percentage for thresholds can be suggested as guidelines for discussion basis in the event of the creation of new SO/ACs but there would need to be a conscious decision, depending on the circumstances. a. Clarify that if such a new SO/AC were to become a decision participant in the Empowered Community, this change would follow the Fundamental Bylaw change process Second reading is planned for Thursday, 14 January. Best regards Mathieu, Thomas, León