[bc-gnso] ALERTS From the Secretariat: Proposed Agenda for the Special GNSO Council Meeting 26 March 2012 at 16:00 UTC

[Benedetta Rossi <bc-secretariat@xxxxxxxxx>]

Dear BC Members,

Please find below the proposed agenda for the Special GNSO Council 
Meeting scheduled for Monday 26 March 2012.
Kind Regards,

Benedetta Rossi
BC Secretariat
https://community.icann.org/display/gnsobc/Home
www.bizconst.org
bc-secretariat@xxxxxxxxx




Proposed Agenda for the Special GNSO Council Meeting 26 March 2012
http://gnso.icann.org/meetings/agenda-council-26mar12-en.htm

The Agenda posted on the *Wiki page* usually has the latest updates:
https://community.icann.org/display/gnsocouncilmeetings/Agenda+26+March+2012

The*motions* can be found on page:
https://community.icann.org/display/gnsocouncilmeetings/Motions+26+March+2012

Note that this agenda may be updated as more information becomes 
available so interested parties are encouraged to periodically check for 
the latest updates on the GNSO Council workspace. 
<https://community.icann.org/display/gnsocouncilmeetings/Home>
This agenda was established according to the GNSO Council Operating 
Procedures approved 22 September 2011 for the GNSO Council and updated.
http://gnso.icann.org/council/gnso-operating-procedures-16dec11-en.pdf

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 
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Special+Council+Meeting&iso=20120326T16>
_Coordinated Universal Time: 16:00 UTC

09:00 Los Angeles; 12:00 Washington DC; 17:00 London; 18:00 Paris; 01:00 
Tokyo;
27 March 2012
05:00 Wellington

Councilors should notify the GNSO Secretariat in advance if a dial out 
call is needed.
*_Item 1: Administrative matters (10 minutes)_*

1.1Roll Call*_
_*
1.2 Statement of interest updates

1.3 Review/amend agenda

*_Item 2: Red Cross and Olympic Committee names_*

A GNSO Drafting Team is working on a charter to determine 
recommendations how to handle the protection of RC and IOC names at the 
top level for the current new gTLD application round to send to the 
ICANN Board. Council must now vote on whether to approve these 
recommendations.
This motion was deferred from the San José Council meeting. Due to the 
severe time constraints involved in acting on the Drafting Team's 
recommendations, this motion is being considered today as an emergency item.
https://community.icann.org/display/gnsocouncilmeetings/Motions+14+March+2012

2.1 Reading of the motion (Jeff Neuman)

2.2 Discussion

2.3 Vote

*__*

*_Item 3:  Any Other Business (5 minutes)_*

*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:
1. Create an Issues Report: requires an affirmative vote of more than 
25% vote of each House or majority of one House;
2. Initiate a Policy Development Process (“PDP”) Within Scope (as 
described in Annex A): requires an affirmative vote of more than 33% of 
each House or more than 66% of one House;
3. Initiate a PDP Not Within Scope: requires an affirmative vote of more 
than 75% of one House and a majority of the other House (“GNSO 
Supermajority”);
4. 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;
5. Approve a PDP Recommendation With a GNSO Supermajority: requires an 
affirmative vote of a GNSO Supermajority; and
6. 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 with respect to any contracting party affected by such contract 
provision.
*Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4 
<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>)
*
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 available.
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 March & October (Summer in the NORTHERN hemisphere )
---------------------------------------------------------------------------- 

Reference (Coordinated Universal Time) UTC 16:00
----------------------------------------------------------------------------
California, USA (PST 
<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 
09:00
New York/Washington DC, USA (EST) UTC-5+1DST 12:00
Buenos Aires, Argentina (ART 
<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 
13:00
Montevideo, Uruguay (UYST 
<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) 
UTC-3+0DST 13:00
London, United Kingdom (BST) UTC+0DST 17:00
Abuja,Nigeria (WAT 
<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) 
UTC+1+0DST 17:00
Tunis, Tunisia (CET) UTC+1+0DST 17:00
Bonn, Germany (CET) UTC+1+0DST 18:00
Paris, France (CET) UTC+1+0DST 18:00
Ramat Hasharon, Israel(IST 
<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>) 
UTC+2+0DST 18:00
Karachi, Pakistan (PKT 
<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> 
) UTC+5+0DST 21:00
Hong Kong (HKT 
<http://www.timeanddate.com/library/abbreviations/timezones/asia/hkt.html>) 
UTC+8+0DST 00:00 next day
Tokyo, Japan (JST 
<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) 
UTC+9+0DST 01:00 next day
Wellington, New Zealand (NZDT 
<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> 
) UTC+12+1DST 05:00 next day
---------------------------------------------------------------------------- 

The DST starts/ends on last Sunday of October 2012, 2:00 or 3:00 local 
time (with exceptions)
----------------------------------------------------------------------
For other places see http://www.timeanddate.com

Glen de Saint Géry

GNSO Secretariat

gnso.secretariat@xxxxxxxxxxxxxx <mailto:gnso.secretariat@xxxxxxxxxxxxxx>

http://gnso.icann.org