with the Board’s timeframes currently implementation of GAC referenced in the GNSO Consensus Advice and (ii) Operating Procedures in the EC did not prevail in relation to submission of such Community IRP. Each motions as well as Board Recall Petition shall scheduling of meetings to include a rationale setting meet its obligations under forth the reasons why such the timelines outlined in the individual seeks to recall ICANN Bylaws as a the Board. The process set Decisional Participant and forth in this Section 3.3 of 2) add a provision to clarify this Annex D is referred to that all petitions concerning herein as the “Board a director removal Recall Process.” process submitted by an (b) A Decisional Participant individual must be that has received a Board submitted directly to the Recall Petition shall either GNSO Council. For this accept or reject such purpose, the GNSO Council Board Recall Petition will develop a clear process during the period and rules for the submission beginning on the date the of such petitions, including Decisional Participant any requirements for the received the Board Recall criteria to be included in a Petition (“Board Recall petition. These rules would Petition Date”) and ending be added to the GNSO at 11:59 p.m. (as Operating Procedures as an calculated by local time at annex once available. the location of ICANN’s principal office) on the date that is the 21st day after the Board Recall Petition Date (the “Board Recall Petition Period”). (i) If, in accordance with Section 3.3(b) of this
with the Board’s implementation of GAC Consensus Advice and (ii) the EC did not prevail in such Community IRP. Each Board Recall Petition shall include a rationale setting forth the reasons why such individual seeks to recall the Board. The process set forth in this Section 3.3 of this Annex D is referred to herein as the “Board Recall Process.” (b) A Decisional Participant that has received a Board Recall Petition shall either accept or reject such Board Recall Petition during the period beginning on the date the Decisional Participant received the Board Recall Petition (“Board Recall Petition Date”) and ending at 11:59 p.m. (as calculated by local time at the location of ICANN’s principal office) on the date that is the 21st day after the Board Recall Petition Date (the “Board Recall Petition Period”). (i) If, in accordance with Section 3.3(b) of this timeframes currently referenced in the GNSO Operating Procedures in relation to submission of motions as well as scheduling of meetings to meet its obligations under the timelines outlined in the ICANN Bylaws as a Decisional Participant and 2) add a provision to clarify that all petitions concerning a director removal process submitted by an individual must be submitted directly to the GNSO Council. For this purpose, the GNSO Council will develop a clear process and rules for the submission of such petitions, including any requirements for the criteria to be included in a petition. These rules would be added to the GNSO Operating Procedures as an annex once available.
proposed-revisions-gnso-op-procedures-bylaws-staff-report-docx-16may17-en.docx