ICANN/GNSO GNSO Email List Archives


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

RE: [council] Point for Discussion

  • To: <ross@xxxxxxxxxx>, "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Subject: RE: [council] Point for Discussion
  • From: "Mike Rodenbaugh" <mxr@xxxxxxxxxxxxx>
  • Date: Thu, 12 Jul 2007 11:11:37 -0700
  • Cc: "GNSO Council" <council@xxxxxxxxxxxxxx>
  • Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:x-mimeole:content-class:mime-version: content-type:content-transfer-encoding:subject:date:message-id: in-reply-to:x-ms-has-attach:x-ms-tnef-correlator:thread-topic: thread-index:references:from:to:cc:return-path:x-originalarrivaltime; b=kENWBBSGDP4DlmbvtBLs5FAyX80OrhqBdLtF9n3bNUYZVX4UE/Wzf/1Wct5wZk22
  • In-reply-to: <46965FFB.4040602@tucows.com>
  • References: <046F43A8D79C794FA4733814869CDF0701E63D70@dul1wnexmb01.vcorp.ad.vrsn.com> <46965FFB.4040602@tucows.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcfEqAaL6ErrXWE3SyKCdVaTlZFGrAAA8tfQ
  • Thread-topic: [council] Point for Discussion

Ross, why the limitation that proxy must be passed 'prior to the start
of the meeting'?  I have seen several times where a Councilor was at a
meeting but needed to leave before it ended, and sought at that point to
give a proxy (which I believe we have accepted that proxy vote on at
least a couple occasions).

Mike Rodenbaugh

Sr. Legal Director

Yahoo! Inc.


NOTE:  This message may be protected by attorney-client and/or work
product privileges, if you are not the intended recipient then please
delete this message and all attachments and notify me as soon as
possible.  Thanks.

-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Ross Rader
Sent: Thursday, July 12, 2007 10:08 AM
To: Gomes, Chuck
Cc: GNSO Council
Subject: Re: [council] Point for Discussion

I don't know that this level of rigor is required or necessary. The only

problem with the previous proxy arrangements was that they weren't 
permitted under ICANN's bylaws. I don't believe that there was any 
indication of abuse, or other problems associated with this method, 
other than the fact that it wasn't technically permissable.

I would like to see proxy's come back, but I don't think that we need to

construct anything more elaborate governing their use than we previously

used. i.e. a proxy can only be assigned by the person who holds the vote

and that the GNSO Secretariat needs to be made aware of the assignment 
by the person passing the proxy prior to the start of the meeting.

Gomes, Chuck wrote:
> I fully understand the reason for eliminating proxy voting on the
> Council and support it, but I would like to propose the following for
> consideration by the Council.
> It seems to me that no constituency should be denied any of their
> in cases where the constituency as a whole has taken a position on an
> issue and one of their Council representatives cannot participate in a
> meeting.  In such a case, it seems reasonable to allow any one
> constituency representative to case all the votes for the constituency
> provided an officer of the constituency confirms that the vote indeed
> reflects the wishes of the full consituency as determined through the
> constituencies established processes.  As I envision this, it would
> apply in cases where a vote was announced in advance, a constituency
> considered the choices and the constituency as a whole provided
> direction to its reps regarding how to vote; otherwise, we would
> be back to proxy voting as previously used.
> I am not suggesting this because of any recent or anticiapted issue
> rather think that it is a procedure we should define before we
> such a situation.
> Thoughts?
> I am not suggesting this as an agenda item for tomorrows meeting but
> simply one for list discussion.  Depending on the discussion that
> follows, we could put this item on a future agenda.
> Chuck Gomes
> "This message is intended for the use of the individual or entity to
> which it is addressed, and may contain information that is privileged,
> confidential and exempt from disclosure under applicable law. Any
> unauthorized use, distribution, or disclosure is strictly prohibited.
> you have received this message in error, please notify sender
> immediately and destroy/delete the original transmission." 


Ross Rader
Director, Retail Services
Tucows Inc.

t. 416.538.5492

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