<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Motion re Extension of Public Comment Periods
- To: <icann@xxxxxxxxxxxxxx>, "GNSO Council" <council@xxxxxxxxxxxxxx>
- Subject: RE: [council] Motion re Extension of Public Comment Periods
- From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
- Date: Wed, 5 Nov 2008 03:36:24 -0500
- In-reply-to: <8E2EC54C4ED348239688D293E52A84F8@hp62301a>
- List-id: council@xxxxxxxxxxxxxx
- References: <4615AB3A9C1D46AB9C834C74BED0CCAA@hp62301a> <B57AB60904BF48F39DCD710114D14707@hp62301a> <046F43A8D79C794FA4733814869CDF07026BDDA9@dul1wnexmb01.vcorp.ad.vrsn.com> <251baf130811050010k531687far507084ec0dd36833@mail.gmail.com> <8E2EC54C4ED348239688D293E52A84F8@hp62301a>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: Ack/HkSkwhZBzugPSTmNcfxpDylB5wAAD8GwAADCboA=
- Thread-topic: [council] Motion re Extension of Public Comment Periods
Looks good to me.
Chuck
________________________________
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Mike Rodenbaugh
Sent: Wednesday, November 05, 2008 3:17 AM
To: 'GNSO Council'
Subject: RE: [council] Motion re Extension of Public Comment
Periods
Thanks Kristina, Chuck and Carlos for the comments with which I
agree. Here is v.3 of the suggested resolution language:
RESOLVED:
The GNSO Council strongly urges ICANN Staff to extend, for
seven days, any public comment periods which overlap with any of the
seven days of an ICANN meeting.
________________________________
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Carlos Affonso
Pereira de Souza
Sent: Wednesday, November 05, 2008 12:10 AM
To: GNSO Council
Subject: Re: [council] Motion re Extension of Public Comment
Periods
Agreed. Thats why we could work with "suspend" as to indicate
that as soon as the meeting starts the clock stops running for comment
periods.
2008/11/5 Gomes, Chuck <cgomes@xxxxxxxxxxxx>
I am not sure we should restrict it to only comment periods that
would end during an ICANN meeting. It seems to me that any comment
period that overlaps an ICANN meeting should be extended.
Chuck
________________________________
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Mike Rodenbaugh
Sent: Wednesday, November 05, 2008 2:48 AM
To: 'GNSO Council'
Subject: RE: [council] Motion re Extension of Public
Comment Periods
Thanks all for considering this late-breaking motion.
Here is an amended version of the "Resolved" paragraph -- to clarify
'extension' vs. 'suspension...
RESOLVED:
The GNSO Council strongly urges ICANN Staff to extend,
for seven days, any public comment periods which would otherwise end
during the seven days of an ICANN meeting.
________________________________
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Mike Rodenbaugh
Sent: Tuesday, November 04, 2008 10:46 PM
To: GNSO Council
Subject: [council] Motion re Suspension of Public
Comment Periods
Hi all: several Councilors would like to introduce and
pass this motion today, whilst we have several different, significant
and ongoing public comment periods. Therefore I make the motion...
Whereas, ICANN's meetings require the full attention of
GNSO Councilors and many other GNSO participants.
Whereas, ICANN has many ongoing public comment periods
of significant interest to many GNSO Councilors and participants.
Whereas, ICANN's typical comment periods are already
difficult for many members of the ICANN community, particularly those
that must consult with members of their Constituency and/or member
organization(s).
RESOLVED:
The GNSO Council strongly urges ICANN Staff to extend
all public comment periods which would otherwise end during an ICANN
meeting, for seven days.
Mike Rodenbaugh
Rodenbaugh Law
PO Box 7775 #55819
San Francisco, CA 94120
+1.415.254.4590
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|