(d) Following the delivery GNSO representative on the No new procedures or Assumptions: of a Rejection Action EC will act in accord with changes to the GNSO A template to be Petition Notice to the EC instructions approved by Operating Procedures developed for a Administration pursuant to majority of each house. and/or ICANN Bylaws. All Rejection Action Section 2.2(c)(i) of this decisions (including Supporting Petition Annex D, the Rejection PROCESS NOTES: whether to support a which will include the Action Petitioning (d) Contact EC Rejection Action Petition) following information: Decisional Participant shall Administration and other will be put before the GNSO (A) Supporting contact the EC Decisional Participants to Council as a motion for rationale, (B) Contact Administration and the determine whether any consideration Threshold for information, (C) other Decisional others support. approval is a simple Statement re: Participants to determine (i) Providing written notice majority vote of each conference call, (D) whether any other to the EC Administration, house, which per Section Statement re: forum, Decisional Participants other Decisional Participant 11.3-I of the ICANN Bylaws (E) Citing PDP support the Rejection and Secretary. is the default voting Standard Bylaw Action Petition. (A) Supporting rationale. threshold. Statement. (i) If the Rejection Action (B) Contact information. The first part of this Petitioning Decisional (C) Statement re: process is only Participant obtains the conference call. triggered if the GNSO support of at least one (D) Statement re: forum. received a petition other Decisional (E) Citing PDP Standard and accepts it Participant (a “Rejection Bylaw Statement. according to its Action Supporting procedures. Notice of Decisional Participant”) … acceptance must the Rejection Action include rationale, etc. Petitioning Decisional as set forth in 2.2ciA. Participant shall provide Then the GNSO will written notice, to include: need to determine the (A) a supporting rationale process that it would in reasonable detail; follow to become a (C) a statement as to Supporting Decisional whether or not the Participant if it Rejection Action receives notice of a Petitioning Decisional petition from another Participant and/or the DP.
(d) Following the delivery of a Rejection Action Petition Notice to the EC Administration pursuant to Section 2.2(c)(i) of this Annex D, the Rejection Action Petitioning Decisional Participant shall contact the EC Administration and the other Decisional Participants to determine whether any other Decisional Participants support the Rejection Action Petition. (i) If the Rejection Action Petitioning Decisional Participant obtains the support of at least one other Decisional Participant (a “Rejection Action Supporting Decisional Participant”) … the Rejection Action Petitioning Decisional Participant shall provide written notice, to include: (A) a supporting rationale in reasonable detail; (C) a statement as to whether or not the Rejection Action Petitioning Decisional Participant and/or the GNSO representative on the EC will act in accord with instructions approved by majority of each house. PROCESS NOTES: (d) Contact EC Administration and other Decisional Participants to determine whether any others support. (i) Providing written notice to the EC Administration, other Decisional Participant and Secretary. (A) Supporting rationale. (B) Contact information. (C) Statement re: conference call. (D) Statement re: forum. (E) Citing PDP Standard Bylaw Statement. No new procedures or changes to the GNSO Operating Procedures and/or ICANN Bylaws. All decisions (including whether to support a Rejection Action Petition) will be put before the GNSO Council as a motion for consideration Threshold for approval is a simple majority vote of each house, which per Section 11.3-I of the ICANN Bylaws is the default voting threshold. Assumptions: A template to be developed for a Rejection Action Supporting Petition which will include the following information: (A) Supporting rationale, (B) Contact information, (C) Statement re: conference call, (D) Statement re: forum, (E) Citing PDP Standard Bylaw Statement. The first part of this process is only triggered if the GNSO received a petition and accepts it according to its procedures. Notice of acceptance must include rationale, etc. as set forth in 2.2ciA. Then the GNSO will need to determine the process that it would follow to become a Supporting Decisional Participant if it receives notice of a petition from another DP.
proposed-revisions-gnso-op-procedures-bylaws-staff-report-docx-16may17-en.docx