ICANN/GNSO GNSO Email List Archives

[council]

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

Re: [council] Motion re Extension of Public Comment Periods

  • To: "GNSO Council" <council@xxxxxxxxxxxxxx>
  • Subject: Re: [council] Motion re Extension of Public Comment Periods
  • From: "Carlos Affonso Pereira de Souza" <caffsouza@xxxxxxxxx>
  • Date: Wed, 5 Nov 2008 06:10:16 -0200
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=hIjwssp+FItmoewyOWlMKQS0fs87pSS4o5oGNT/c7L8=; b=SmKjuOi0HMRsMJzAq0he64e5ed4yZ8gGaANTl4HXnNuEQ7qlp/fSwBakqpliu4IM2l 1tkEspVwaBrHTU1BHtDhQkly1Qi8/aqS4aT89u893mLYnUFF945s3odhjk9c45I4MHdc C+6CcGlkBkgJxpiAAy/+vEokttODxFgVMQrTg=
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=QQkL83MTPDSn+O3+j/56G2J2NhYuRbtYuFXAKULUZ9luxytPHxwKm9XpfkypGuUckc NJ69VXlBWv4GMCJ3mWfFZSYnLQQEAzG4T/Cqj3YuXyGJyA7ijiKItVF+X0B/4NXJEPJR tzqD5bY78Bss+9N4zgIxKebCj/iOyY9b/4JzU=
  • In-reply-to: <046F43A8D79C794FA4733814869CDF07026BDDA9@dul1wnexmb01.vcorp.ad.vrsn.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <4615AB3A9C1D46AB9C834C74BED0CCAA@hp62301a> <B57AB60904BF48F39DCD710114D14707@hp62301a> <046F43A8D79C794FA4733814869CDF07026BDDA9@dul1wnexmb01.vcorp.ad.vrsn.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
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 >>>