ICANN/GNSO GNSO Email List Archives


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

[council] GNSO Council Meeting Agenda Monday, 21 January 2013 at 15:00UTC:

  • To: "council@xxxxxxxxxxxxxx List" <council@xxxxxxxxxxxxxx>
  • Subject: [council] GNSO Council Meeting Agenda Monday, 21 January 2013 at 15:00UTC:
  • From: Glen de Saint Géry <Glen@xxxxxxxxx>
  • Date: Fri, 18 Jan 2013 05:53:16 -0800
  • Accept-language: fr-FR, en-US
  • Acceptlanguage: fr-FR, en-US
  • Importance: high
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Ac31gp75+rseAZnxRZ6P//EivX+WKQ==
  • Thread-topic: GNSO Council Meeting Agenda Monday, 21 January 2013 at 15:00UTC:

Dear Councillors,
Please find the draft agenda for the GNSO Council Meeting on Monday, 21 January 
2013 at 15:00UTC:
The agenda is published on pages:

On the Wiki at:
Agenda for the Special GNSO Council Meeting on 21 January 2012
This agenda was established according to the GNSO Council Operating Procedures 
approved 13 September 2012 for the GNSO Council and updated.
For convenience:

 *   An excerpt of the ICANN Bylaws defining the voting thresholds is provided 
in Appendix 1 at the end of this agenda.
 *   An excerpt from the Council Operating Procedures defining the absentee 
voting procedures is provided in Appendix 2 at the end of this agenda.
Meeting Times 15:00 UTC<http://tinyurl.com/bojlrbx>

Coordinated Universal Time 15:00 UTC
07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Paris; 04:00 Wellington
Dial-in numbers will be sent individually to Council members. Councilors should 
notify the GNSO Secretariat in advance if a dial out call is needed.
GNSO Council meeting audio cast
Item 1: Administrative matters (10 minutes)
1.1  Roll Call
1.2  Statement of interest updates
1.3  Review/amend agenda
Item 2: Review and potentially add endorsements to the list of SG endorsed GNSO 
applicants to the ATRT (20 minutes)
The call for applicants to serve on the next Accountability and Transparency 
Review Team (ATRT) has closed.  ICANN has forwarded all applications received 
to the GNSO Council and placed them on a web site for inspection by the four 
GNSO stakeholder groups.  According to the Process for GNSO Endorsement of 
Nominees to the Affirmation of Commitments Review Teams, each stakeholder group 
(SG) may endorse one applicant to serve as a representative in a given review 
team. The Council must consider the resulting list of up to four nominees. If 
the list does not meet the required diversity objectives, the Council as a 
whole may choose to endorse up to two additional candidates from the applicant 
pool, who will help to give the list of GNSO nominees the desired balance. In 
this case, the Council will hold a vote, with sixty percent support of both 
houses represented in the Council being required for endorsement. If no 
candidate obtains that level of support, the list of endorsements obtained via 
the bottom-up process of stakeholder group nominations will be deemed final and 
forwarded to ICANN.

2.1 Review SG endorsed applicants against specfied diversity requirements
2.2 Consider additional candidates
2.4 Vote on addtional candidates
(To approve the addition of a candidate/s to the list of endorsed candidates in 
order to meet geographic and/or gender diversity coondition: An affirmative 
vote of 60% or more of each House).
Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3)
9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO 
Operating Procedures, the default threshold to pass a GNSO Council motion or 
other voting action requires a simple majority vote of each House. The voting 
thresholds described below shall apply to the following GNSO actions:
a. Create an Issues Report: requires an affirmative vote of more than 
one-fourth (1/4) vote of each House or majority of one House.
b. Initiate a Policy Development Process ("PDP") Within Scope (as described in 
Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an 
affirmative vote of more than one-third (1/3) of each House or more than 
two-thirds (2/3) of one House.
c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO 
d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative 
vote of more than one-third (1/3) of each House or more than two-thirds (2/3) 
of one House.
e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an 
affirmative vote of a GNSO Supermajority.
f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved 
under d. or e. above, the GNSO Council may approve an amendment to the Charter 
through a simple majority vote of each House.
g. Terminate a PDP: Once initiated, and prior to the publication of a Final 
Report, the GNSO Council may terminate a PDP only for significant cause, upon a 
motion that passes with a GNSO Supermajority Vote in favor of termination.
h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an 
affirmative vote of a majority of each House and further requires that one GNSO 
Council member representative of at least 3 of the 4 Stakeholder Groups 
supports the Recommendation.
i. Approve a PDP Recommendation With a GNSO Supermajority: requires an 
affirmative vote of a GNSO Supermajority,
j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting 
Parties: where an ICANN contract provision specifies that "a two-thirds vote of 
the council" demonstrates the presence of a consensus, the GNSO Supermajority 
vote threshold will have to be met or exceeded.
k. Modification of Approved PDP Recommendation: Prior to Final Approval by the 
ICANN Board, an Approved PDP Recommendation may be modified or amended by the 
GNSO Council with a GNSO Supermajority vote.
l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council 
members of each House, or (b) three-fourths (3/4) of one House and a majority 
of the other House."
Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 
4.4.1 Applicability
Absentee voting is permitted for the following limited number of Council 
motions or measures.
a. Initiate a Policy Development Process (PDP);
b. Approve a PDP recommendation;
c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws;
d. Fill a Council position open for election.
4.4.2 Absentee ballots, when permitted, must be submitted within the announced 
time limit, which shall be 72 hours from the meeting's adjournment. In 
exceptional circumstances, announced at the time of the vote, the Chair may 
reduce this time to 24 hours or extend the time to 7 calendar days, provided 
such amendment is verbally confirmed by all Vice-Chairs present.
4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes 
according to these procedures and will provide reasonable means for 
transmitting and authenticating absentee ballots, which could include voting by 
telephone, e- mail, web-based interface, or other technologies as may become 
4.4.4 Absentee balloting does not affect quorum requirements. (There must be a 
quorum for the meeting in which the vote is initiated.)
Local time between October and March, Winter in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 15:00
California, USA 
UTC-8+0DST 07:00
New York/Washington DC, USA (EST) UTC-5+0DST 10:00
Rio de Janiero, Brazil (BRST) UTC-3+1DST 13:00
Montevideo, Uruguay 
UTC-3+1DST 13:00
Edinburgh, Scotland (BST) UTC+0DST 11:00
London, United Kingdom (BST) UTC+0DST 15:00
Abuja, Nigeria 
 UTC+1+0DST 16:00
Bonn, Germany (CEST) UTC+1+0DST 16:00
Stockholm, Sweden (CET) UTC+1+0DST 16:00
Ramat Hasharon, 
 UTC+2+0DST 17:00
Karachi, Pakistan 
) UTC+5+0DST 20:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 23:00
Perth, Australia 
UTC+8+0DST 23:00
Wellington, New Zealand 
 ) UTC+12+1DST 04:00 - next day
The DST starts/ends on last Sunday of March 2013, 2:00 or 3:00 local time (with 
For other places see http://www.timeanddate.com
Please let me know if you have any questions.
Thank you.
Kind regards,
Glen de Saint Géry
GNSO Secretariat

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