ICANN ICANN Email List Archives

[gnso-operating-procedures-2009]


<<< Chronological Index >>>    <<< Thread Index >>>

RSG Position on Recommendations For Updated GNSO Council Operating Procedures

  • To: "gnso-operating-procedures-2009@xxxxxxxxx" <gnso-operating-procedures-2009@xxxxxxxxx>
  • Subject: RSG Position on Recommendations For Updated GNSO Council Operating Procedures
  • From: "Clarke D. Walton" <clarke.walton@xxxxxxxxxxxxxx>
  • Date: Fri, 16 Oct 2009 13:33:24 -0400

October 16, 2009


Registrar Stakeholder Group Position on Recommendations For Updated GNSO 
Council Operating Procedures


BACKGROUND

In October 2009, the Registrar Stakeholder Group ("RSG") was asked to provide 
feedback regarding the Recommendations for Updated GNSO Council Operating 
Procedures ("Recommended GNSO Operating Procedures").  This Position Paper 
captures the overall sentiment expressed by the RSG Members who provided 
feedback about this matter.  Due to time constraints, however, no formal vote 
regarding this Position Paper was taken.

RSG POSITION

The RSG recognizes that establishing updated operating procedures consistent 
with  the ICANN Bylaws is a key step toward seating the new GNSO Council and 
the RSG appreciates the work of the GNSO Council Operations Work Team in 
drafting the Recommended GNSO Operating Procedures.

The RSG supports the Recommended GNSO Operating Procedures provided, however, 
that the suggested substitute language regarding Voting Thresholds in Section 
4.2 is adopted.[i] Specifically, the suggested substitute language that the RSG 
wishes to be incorporated in the GNSO Operating Procedures is as follows:

"Unless otherwise specified in these procedures or in the ICANN Bylaws, to pass 
a motion or other action, greater than 50% of the eligible voters in each House 
must cast affirmative votes. For all votes taken, the number of eligible voters 
in each House shall be fixed to the number of seats allocated in the Bylaws 
(a.k.a. the denominator) and is not affected by the number of members present 
or absent at the meeting in which the motion or other action is initiated. 
Council members are permitted to abstain in any vote, but must provide a reason 
which shall be recorded in the minutes along with the abstention."

CONCLUSION

The opinions expressed by the RSG in this Position Paper should not be 
interpreted to reflect the individual opinion of any particular RSG Member.



________________________________

[i] One RSG Member objected to the suggested substitute language, noting that 
the suggested substitute language may slow down ICANN 's work progress.   This 
objection should be considered a minority view.

Attachment: RSG Position - Updated GNSO Council Operating Procedures FINAL.pdf
Description: RSG Position - Updated GNSO Council Operating Procedures FINAL.pdf



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy