ICANN/DNSO
DNSO Mailling lists archives

[council]


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

RE: [council] Proposed alteration to Schedule for the rounds of Convention Style Voting


I suggest the revised time line must include among other things, ensuring that the candidates fully  disclose
all conflicts,  including professional and voluntary relationships with contracted ICANN parties covering the past two years, presently, and any going forward engagements/agreements, or endeavors, then this revised time line makes sense and I support it. 

All candidates should disclose ALL relationships with ICANN, as well. 

However, of significant priority should be the disclosure of agreements with, representation of, or contracts, or agreements, for remuneration of any kind, including reimbursement of expenses, or any non monetary compensation, with any contracted party, or any entity such as a foundation or other entity, who has provided funding for participation or representation at ICANN  meetings, or meetings or hearings related to ICANN. These kinds of full and frank disclosures help to ensure that the Council is aware of conflicts. 

Candidates should disclose fully any conflicts which may require them to recluse themselves from voting on any topics.  The candidate should not make a decision on their own about whether they will need to recluse themselves. They should disclose any remuneration they have received to attend ICANN meetings, who the remuneration is from, and identify remuneration for participating in other events where they participated in events addressing ICANN, including sponsorship of any kind they have received from outside parties.

Also, IF a candidate has had their travel/expenses paid to ICANN meetings, this should be disclosed. This would include reimbursement from a trade association or an employer or outside sources.  This will help to create a transparent platform of information for all candidates.  

This will also inform all regarding the level of participation and experience in Icon's processes. 

Marilyn 


 

-----Original Message-----
From: Neuman, Jeff [mailto:Jeff.Neuman@Neustar.us]
Sent: Wednesday, March 05, 2003 9:10 PM
To: 'Bruce Tonkin'; council
Cc: DNSO.SECRETARIAT@dnso.org; Louis Touton
Subject: RE: [council] Proposed alteration to Schedule for the rounds of
Convention Style Voting


I fully support Bruce's suggestion on the time line.

Jeff

-----Original Message-----
From: Bruce Tonkin [mailto:Bruce.Tonkin@melbourneit.com.au]
Sent: Wednesday, March 05, 2003 8:59 PM
To: council
Cc: DNSO.SECRETARIAT@dnso.org; Louis Touton
Subject: [council] Proposed alteration to Schedule for the rounds of
Convention Style Voting




Hello All,

We now have at least 6 nominations for the ICANN Board seats.  It is good we
have so many good candidates willing to serve on the ICANN Board.

We are attempting to vote via a convention style process over the next
couple of weeks with the aim to finalise the election for seat 14 at the
ICANN meeting in Rio.

Given that it may take a few rounds to decide the final result, the process
proposed below allows for several rounds of voting within the 14 day voting
period.

Now I propose that the first round we handled over a 7 day period, instead
of the suggested 5 day period described below.  ie the first round would
start on 6 March and finish on 13 March.   This effectively combines the
first two rounds in the schedule below.

The reasons for this are:

(1) The council needs sufficient time to consider the suitability of the
candidates.  Most of the candidates have only just been nominated.
This may involve consultation within constituencies and the wider community,
and also may involve council members asking questions of the candidates.

(2) We have three new members of council in the past week, and a fourth new
member is in the process of being appointed by the registrar constituency.
These new members need some time to familiarize themselves with the issues,
and review the candidates.

If we do not reach a conclusion by the end of the 14 day voting period, then
I propose that we hold the necessary additional rounds of voting at the
ICANN meeting in Rio on 25 March 2003 - prior to the beginning of the
council meeting.  I would rather not rush the voting process during the
initial stages of voting, to ensure a conclusion at the end of the 14 day
period.

Please post any concerns or objections you have with this process within the
next 24 hours.
If there are no objections then we will run with the schedule below with the
exception that the first round will occur over 7 days (from 6 March to 13
March), which will provide for 4 rounds of voting (instead of 5).

Regards,
Bruce Tonkin




> [To: council@dnso.org]
> 
> Dear Council Members,
> 
> Please note the Schedule for the rounds of Convention Style voting.
> Further notification will be sent when the nominations have closed on
> Thursday 11:00 UTC.
> 
> The GNSO Council will vote by e-mail between March 6 and 
> March 20, 2003 and
> the vote will be confirmed at the GNSO Council meeting in Rio 
> de Janeiro on
> March 25, 2003
> 
> For other places see http://www.timeanddate.com/worldclock/
> 
> Each GNSO Council member will be sent an individual ballot 
> which must be
> completed with one (x) and returned to the address on the ballot.
> 
> The votes will be weighed according to the ICANN bylaws
> http://www.icann.org/general/archive-bylaws/bylaws-15dec02.htm#X
> Registrar and Registry Constituency members' votes will count 
> for 2 for each
> constuency member, while in the remaining 4 constituencies, each
> constituency member's vote will count for 1.
> 
> SCHEDULE FOR THE ROUNDS OF CONVENTION STYLE VOTING
>      1a. March 6, 15:00 UTC - First-round ballot distributed by
>  secretariat
>      1b. March 11, 15:00 UTC - All ballots from first round must be
>  returned to secretariat
>      1c.  March 11, 18:00 UTC - Secretariat announces results of
>  first-round ballot
> 
>  (as needed:)
>      2a.  March 11, 18:00 UTC - Second-round ballot distributed by
>  secretariat
>      2b.  March 13, 15:00 UTC - All ballots from second round must be
>  returned to secretariat
>      2c.  March 13, 18:00 UTC - Secretariat announces results of
>  second-round ballot
> 
>  (as needed:)
>      3a.  March 13, 18:00 UTC - Third-round ballot distributed by
>  secretariat
>      3b.  March 15, 15:00 UTC - All ballots from third round must be
>  returned to secretariat
>      3c.  March 15, 18:00 UTC - Secretariat announces results of
>  third-round ballot
> 
>  (as needed:)
>      4a.  March 15, 18:00 UTC - Fourth-round ballot distributed by
>  secretariat
>      4b.  March 18, 15:00 UTC - All ballots from fourth round must be
>  returned to secretariat
>      4c.  March 18, 18:00 UTC - Secretariat announces results of
>  fourth-round ballot
>  (as needed:)
> 
>      5a.  March 18, 18:00 UTC - Fifth-round ballot distributed by
>  secretariat
>      5b.  March 20, 15:00 UTC - All ballots from fifth round must be
>  returned to secretariat
>      5c.  March 20, 18:00 UTC - Secretariat announces results of
>  fifth-round ballot
> 
> For other places see http://www.timeanddate.com/worldclock/
> 
> Each GNSO Council member will be sent an individual ballot 
> which must be
> completed with one (x) and returned to the address on the ballot.
> 
> The votes will be weighed according to the ICANN bylaws
> http://www.icann.org/general/archive-bylaws/bylaws-15dec02.htm#X
> Registrar and Registry Constituency members' votes will count 
> for 2 for each
> constuency member, while in the remaining 4 constituencies, each
> constituency member's vote will count for 1.
> 
> At the start of the e-mail voting procedure, only the 17 current
> members may vote.
> 
> GNSO Secretariat
> 
> 


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