(d) Amendments to the The DT notes that Sec 17.3 No new procedures or Assumptions: CSC Charter shall not be requires “simple majority of changes to the GNSO The reference to effective unless ratified by … GNSO Council”, and Operating Procedures simple majority of the vote of a simple suggests that GNSO and/or ICANN Bylaws. The GNSO Council refers majority of each of the Operating Procedures decision to approve to the default voting ccNSO and GNSO Councils define that as a majority of amendments to the CSC threshold of simple pursuant to each such Council, or a majority of charter will be put before majority of each organizations’ procedures. each house. the GNSO Council as a house. Prior to any action by the motion for consideration Coordination with ccNSO and GNSO, any Threshold for approval is a the ccNSO in relation recommended changes to simple majority vote of each to any possible the CSC Charter shall be house, which per Section amendments is subject to a public 11.3-I of the ICANN Bylaws anticipated. comment period is the default voting threshold. ARTICLE 18 IANA NAMING No recommended action, See #11 See #11 FUNCTION REVIEWS noting that GNSO SECTION 18.2 FREQUENCY Supermajority is defined in OF PERIODIC IFRS Bylaws: (c) In the event a Special “ (A) two-thirds (2/3) of the IFR is ongoing at the time a Council members of each Periodic IFR is required to House, or (B) three-fourths be convened under this (3/4) of the Council Section 18.2, the Board members of one House and shall cause the convening a majority of the Council of the Periodic IFR to be members of the other delayed if such delay is House.” approved by the vote of (i) a supermajority of the ccNSO Council … and (ii) a GNSO Supermajority. SECTION 18.6 No recommended action, No new procedures or Assumptions: RECOMMENDATION TO noting that GNSO changes to the GNSO In those instances AMEND THE IANA Supermajority is defined in Operating Procedures where there is a NAMING FUNCTION Bylaws: and/or ICANN Bylaws reference to GNSO
(d) Amendments to the CSC Charter shall not be effective unless ratified by the vote of a simple majority of each of the ccNSO and GNSO Councils pursuant to each such organizations’ procedures. Prior to any action by the ccNSO and GNSO, any recommended changes to the CSC Charter shall be subject to a public comment period The DT notes that Sec 17.3 requires “simple majority of … GNSO Council”, and suggests that GNSO Operating Procedures define that as a majority of Council, or a majority of each house. No new procedures or changes to the GNSO Operating Procedures and/or ICANN Bylaws. The decision to approve amendments to the CSC charter 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: The reference to simple majority of GNSO Council refers to the default voting threshold of simple majority of each house. Coordination with the ccNSO in relation to any possible amendments is anticipated. ARTICLE 18 IANA NAMING FUNCTION REVIEWS SECTION 18.2 FREQUENCY OF PERIODIC IFRS (c) In the event a Special IFR is ongoing at the time a Periodic IFR is required to be convened under this Section 18.2, the Board shall cause the convening of the Periodic IFR to be delayed if such delay is approved by the vote of (i) a supermajority of the ccNSO Council … and (ii) a GNSO Supermajority. No recommended action, noting that GNSO Supermajority is defined in Bylaws: “ (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House.” See #11 See #11 SECTION 18.6 RECOMMENDATION TO AMEND THE IANA NAMING FUNCTION No recommended action, noting that GNSO Supermajority is defined in Bylaws: No new procedures or changes to the GNSO Operating Procedures and/or ICANN Bylaws Assumptions: In those instances where there is a reference to GNSO
proposed-revisions-gnso-op-procedures-bylaws-staff-report-docx-16may17-en.docx