<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Avenir, sans-serif;">
<div>
<div>
<div>
<div>
<div><u><font face="Avenir">Sent on behalf of CoChairs </font></u></div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div><u><font face="Avenir"><br>
</font></u></div>
<div><font face="Avenir">Please find below the main conclusions of our deliberations during call #77. The updated document is attached.</font></div>
</div>
</span></div>
</span></div>
</span>
<div><br>
</div>
</div>
<div><font face="Avenir,sans-serif">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). </font></div>
<div><font face="Avenir,sans-serif">b. Make it mandatory for petitioning party to reach out to SO/ACs to socialize relevant information before Community Forum.</font></div>
<div><font face="Avenir,sans-serif">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.</font></div>
<div><font face="Avenir,sans-serif">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. </font></div>
<div><font face="Avenir,sans-serif">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. </font></div>
<div><font face="Avenir,sans-serif">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)</font></div>
<div><font face="Avenir,sans-serif">b. Former paragraph 62 is therefore removed. </font></div>
<div><font face="Avenir,sans-serif">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.</font></div>
<div><font face="Avenir,sans-serif">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. </font></div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Avenir, sans-serif; font-size: 12px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Avenir, sans-serif; font-size: 12px;">
<div><font face="Avenir">Best regards</font></div>
<div><font face="Avenir"><br>
</font></div>
<div><font face="Avenir">Mathieu, Thomas, León</font></div>
<div><font face="Avenir"><br>
</font></div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Avenir, sans-serif; font-size: 12px;">
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
</body>
</html>