Sent on behalf of CoChairs Please find below the main conclusions of our deliberations during call #77. The updated document is attached. a. Discussed changes in the escalation timelines by simplifying some decision steps in the process, while ensuring that the issues remain widely discussed within the Community (tracked changes are shown below on page 3). 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. d. Discussions focused on whether to keep the conference call (or a Webinar) as a standard instead of optional step (although not requiring decisions at the end of the call) => This point remains to be finalized. 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 confirmed 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. Former paragraph 62 is therefore removed. 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 decisional participant in the Empowered Community, this change would require a change to the Fundamental Bylaws. Best regards Mathieu, Thomas, León