ICANN/GNSO GNSO Email List Archives

[council]


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

Re: [council] RESOLUTION FOR TOMORROW'S TELECONFERENCE

  • To: gnso.secretariat@xxxxxxxxxxxxxx
  • Subject: Re: [council] RESOLUTION FOR TOMORROW'S TELECONFERENCE
  • From: ellen@xxxxxxxxxxxxxxxxx
  • Date: Thu, 14 Aug 2003 03:14:43 -0700 (PDT)
  • Cc: council@xxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx

On Wed, 13 Aug 2003 18:17:55 +0200, "GNSO SECRETARIAT"
wrote:
I'm sorry that I will be unable to make the call - am
traveling and will not be phone available at that time.
My proxy to Laurence and/or Lynda. Still agree to the
proposal.
Warmest,
Ellen
> 
> [To: Council@xxxxxxxx]
> 
> At the request of Antonio Harris, this mail is
> forwarded to the GNSO Council
> list
> 
> mercredi 13 août 2003 16:57
> À : gnso.secretariat@xxxxxxxxxxxxxx;
> owner-council@xxxxxxxx
> Objet : RESOLUTION FOR TOMORROW'S TELECONFERENCE
> 
> 
> Bruce,
> 
> I would like to present the following resolution
> to be discussed in the teleconference:
> 
> Proposed Council resolution on Constituency
> representation to meet ICANN
> requirements on geographical diversity and   informed
> decision-making
>  Proposed by, in alphabetical order,
>    Antonio Harris
>    Ellen Shankman,
>    Philip Sheppard
>    Ken Stubbs
> 
>    Whereas,
>    the Names Council resolution of 1st August 2002
> called for "three
> representatives
>  per Constituency on the GNSO Council".
> 
>    Whereas,
>    ICANN core value 2.4 is:
>    - "Seeking and supporting broad, informed
> participation reflecting the
>  functional, geographic, and cultural diversity of the
> Internet at all
> levels
>  of policy development and decision-making".
> 
>    Whereas,
>    ICANN core value 2.7 is:
>    - "Employing open and transparent policy
development
> mechanisms that
>  (i) promote well-informed decisions based on expert
> advice, and (ii) ensure
>  that those entities most affected can assist in the
> policy development
>  process."
> 
>    Whereas,
>    by-law article XX.5.8 states:
>    "In the absence of further action on the topic by
> the New Board, each
>  of the GNSO constituencies shall select two
> representatives to the GNSO
>  Council.." "..no later than 1 October 2003."
> 
> 
>    The GNSO council resolves that:
> 
>    Two representatives per Constituency is
inconsistent
> with ICANN core
> value 2.4
>  on geographic and cultural diversity within the
> constituency. With three
>  representatives per constituency, the majority of
> ICANN regions ARE
> represented.
>  With two, the majority of ICANN regions are NOT
> represented.
> 
>    .
>    Two representatives per Constituency is
inconsistent
> with ICANN core
> value 2.7
>  on well-informed decision making. Experience has
shown
> that three
> representatives
>  improves the constituencies ability to share the
> workload of a council
>  member, to be able to participate in task forces of
> the council, and to
>  more effectively communicate with multiple regions.
>    .
>    There is no evidence of increased effectiveness
with
> two representatives
>  rather than three.
>    .
>    And therefore the GNSO Council requests the Board
to
> make two changes
>  in its review timetable:
>    1. To change the transition article to allow three
> representatives per
>  constituency on the GNSO Council until the end of the
> ICANN annual meeting
>  2004;
>    2. To perform a review of the GNSO council in or
> around June 2004.
> 
> Regards
> 
> Tony Harris



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