<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Motion deadline per operating procedures
- To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Subject: RE: [council] Motion deadline per operating procedures
- From: "Rosette, Kristina" <krosette@xxxxxxx>
- Date: Wed, 1 Dec 2010 12:20:14 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
- In-reply-to: <20101201165947.5705.qmail@mm02.prod.mesa1.secureserver.net>
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AcuReV9U/B5IxvncRaa8gpDFOEDuRwAAjD7w
- Thread-topic: [council] Motion deadline per operating procedures
Because Section 3.3 says "days", the motion was timely as long as it was
submitted on the 30th, which it was.
If, going forward, the Council wishes to adopt Tim's interpretation, we should
amend Section 3.3 to change "8 days" to "192 hours". Unless and until such an
amendment, my motion was timely.
________________________________
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of Tim Ruiz
Sent: Wednesday, December 01, 2010 12:00 PM
To: council@xxxxxxxxxxxxxx
Subject: [council] Motion deadline per operating procedures
The relevant paragraph in section 3.3 of our operating procedures
clearly states that motions must be submitted "...no later than 8 days
before the GNSO Council meeting." Given that our meeting is scheduled to
begin at 1900 UTC on the 8th, neither of the motions submitted yesterday
by Mary and Kristina met the deadline of 1900 UTC the 30th.
Again, given that ICANN involves one or more days of travel for many of
us, and that any 8 day period also includes at least one weekend, I
think it is crucial that motions are submitted as soon as possible and
the deadline should be strictly observed.
Tim
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|