ICANN/GNSO GNSO Email List Archives

[council]


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

RE: [council] Motions for 17 Dec Council Meeting


Thanks for the correction Stephane.  Not sure how I missed your second of
motion 3.
 
Regarding the Council Operating Procedures requirement that motions should
be submitted 8 days prior to a Council meeting, that requirement would apply
to motion 2, motion 3 and motion 4.  In all three cases the Coucil would
need to agree to an exception to the procedures requirement or we will have
to delay action on all three topics.
 
Chuck


  _____  

From: Stéphane Van Gelder [mailto:stephane.vangelder@xxxxxxxxx] 
Sent: Monday, December 14, 2009 8:43 AM
To: Gomes, Chuck
Cc: GNSO Council
Subject: Re: [council] Motions for 17 Dec Council Meeting


Hi Chuck, 

Your description is incorrect. I had seconded motion 3 on December 6.

Further, it is my assessment of the 8 day notice requirement set out by
article 3.3 of the GNSO operating rules and procedures that motion 4,
proposed by Wolf on Dec 13, cannot be submitted for our Dec 17 meeting.

I am happy to be corrected if this assessment is wrong.

Thanks,

Stéphane


Le 13 déc. 2009 à 14:22, Gomes, Chuck a écrit :


For our 17 Dec Council meeting, the following four motions listed below with
their status are posted at
<https://st.icann.org/gnso-council/index.cgi?17_december_motions>
https://st.icann.org/gnso-council/index.cgi?17_december_motions):

1.      Motion To Approve Tool Kit of Services Recommendations for GNSO
Constituencies and Stakeholder Groups (amended 4 Dec 09) - moved & seconded 

2.      Motion to Approve the Alternative Proposal recommended by the
Special Trademark Issues Review Team - needs to be moved and seconded 

3.      Motion to delay decision regarding initiation of a Vertical
Integration PDP - needs to be seconded 

4.      Proposed Motion on Support for a PDP Work Team Face to Face Meeting
- needs to be seconded

At this point, only motion 1 above is ready for action.  So we need someone
to make motion 2 and, if that happens, we will need a second.  We also need
seconds on motions 3 & 4. 
 
Chuck


Attachment: smime.p7s
Description: S/MIME cryptographic signature



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