- Council Activities
- Group Activities
- Quick Info
Date:29 January 2015
Proposed Agenda for the GNSO Council Teleconference on 29 January 2015 at 12:00 UTC.
This agenda was established according to the GNSO Council Operating Procedures approved and updated on 13 November 2014.
- 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 Time 12:00 UTC:
Coordinated Universal Time 12:00 UTC
04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Brussels; 20:00 Perth
GNSO Council meeting audio cast
To join the event click on the link:
Councillors should notify the GNSO Secretariat in advance if a dial out call is needed.
Item 1: Administrative matters (5 mins)
1.1 Roll Call
1.2 Statement of interest updates
1.3 Review/amend agenda
1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures:
Minutes of the GNSO Council meeting 11 December 2014 will be posted as approved on xxxxx 2015 and the minutes of the 15 January 2015 Council meeting will be posted as approved on XXXX 2015
Item 2: Opening Remarks / Review of Projects & Action List (10 mins)
Review focus areas and provide updates on specific key themes / topics
Comments or questions arising.
Item 3: Consent agenda (5 mins)
3.1 – Approve request for extension of timeline for Issue Report on Rights Protection Mechanisms
3.2 – Approve formation of informal community group to review IDN Implementation Guidelines and approve draft GNSO Council letter in response to these.
Item 4: UPDATE – Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (30 mins)
The CWG has been chartered to develop a proposal on Naming Related Functions for the IANA Stewardship Transition Proposal and has been meeting for 2 hours every week since its creation with a goal of delivering a final proposal by the end of January 2015. The January 2015 target date is driven by the request for proposals from the IANA Stewardship Transition Coordination Group (ICG). It is by now clear that the January target date will not be met and that a new target needs to be agreed.
A number of sub-groups were formed to progress work on the different elements of the ICG Request for Proposals and a face-to-face meeting was run in mid-November 2014. A draft proposal was published for community comment on 1 December 2014 and the public comment period has since closed. An intensive work weekend followed on 10 & 11 January 2015 which attempted to systematically review inputs from the public comment.
Given the deadlines and associated intensity of the work of the CWG as well as the need for the GNSO as a chartering organisation to approve the proposal, it is relevant for the Council, and through it the GNSO, to receive a full update and to have the opportunity to discuss the work of the CWG. This item will provide an update, create the opportunity for discussion and empahsise the need for the GNSO to be informed about the work of this important group.
4.1 – Update (Jonathan Robinson)
4.2 – Discussion
4.3 – Next steps
Item 5: Update: Planning for ICANN meeting in Singapore – key direction & themes (10 mins)
5.1 Update – Volker Greimann
5.2 Open issues / Discussion
5.3 Actions arising
Item 6: Any Other Business (5 mins)
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:
- Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House.
- Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House.
- Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority.
- 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.
- Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority.
- 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.
- 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.
- 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.
- Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority,
- 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.
- 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.
- 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)
Absentee voting is permitted for the following limited number of Council motions or measures.
- Initiate a Policy Development Process (PDP);
- Approve a PDP recommendation;
- Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws;
- 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.)
Reference (Coordinated Universal Time) UTC 12:00
Local time between October and March, Winter in the NORTHERN hemisphere
California, USA (PDT) UTC-8+0DST 04:00
San José, Costa Rica UTC-6+0DST 06:00
Iowa City, USA (CDT) UTC-6+0DST 06:00
New York/Washington DC, USA (EST) UTC-5+0DST 07:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 10:00
Montevideo, Uruguay (UYST) UTC-2+1DST 10:00
Buenos Aires, Argentina (ART) UTC-3+0DST 09:00
London, United Kingdom (BST) UTC+0DST 12:00
Bonn, Germany (CET) UTC+1+0DST 13:00
Cairo, Egypt, (EET) UTC+2+0DST 14:00
Istanbul, Turkey (EEST) UTC+2+0DST 14:00
Ramat Hasharon, Israel (IDT) UTC+3+0DST 14:00
Perth, Australia (WST) UTC+8+1DST 20:00
Melbourne, Australia (AEDT) UTC+11+1DST 23:00
DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions)