Sorry, you need to enable JavaScript to visit this website.
Skip to main content

GNSO Council Teleconference Agenda - 7 January 2010

Last Updated:
06 January 2010

This agenda was established according to the GNSO Council Operating Procedures approved 28 October 2009 for the GNSO Council

Coordinated Universal Time: 20:00 UTC - (see below and for other times)
(10:00 HAST, 12:00 PST, 15:00 EST, 21:00 CET; 04:00 Hong Kong, 07:00 Melbourne Friday)

Chair: Chuck Gomes; Vice Chairs: Olga Cavalli & Stéphane Van Gelder

Note: This meeting will be recorded.

Scheduled time for meeting 120 mins.

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.

Item 1: Administrative matters

1.1 Roll call of Council members

1.2 Update any statements of interest

1.3 Review/amend agenda

1.4. Note the status of minutes for the following Council meetings per the new Council Operating Procedures:

  • 17 December meeting – Approved on 31 December 2009

Item 2: Issues Report regarding vertical separation of Registries and Registrars

2.1 Refer to Issues Report on Vertical Integration:

2.2 Overview of Issues Report (Margie Milam)

2.3 Discussion

2.4 Information about the ICANN Consultation on New gTLD Registry Agreement on 7 January 2010 in D.C.?

2.5 Next steps

2.5.1 Action regarding decision on whether or not to initiate a PDP – 28 Jan meeting?

Item 3: Prioritization of GNSO work

3.1 Status Report (Olga Cavalli)

3.2 Next steps?

Item 4: The IDN Implementation Working Team Final Report

4.1 Refer to report at

4.2 Brief overview of report (Bart Boswinkel)

4.3 Action item: The working team report recommends that the GNSO & ccNSO do policy work with regard to the following two issues related to single-character IDN top level names:

1) selection of scripts for which single character IDN TLDs should be allowed;
2) method for allocation of single character IDN TLDs.

4.3.1 Discussion

4.3.2 Volunteers for working with ccNSO volunteers to develop a draft charter?

Item 5: AGP Limits Policy - Implementation Report

5.1 Refer to


5.1.1 Staff Presentation


5.2 Action Items

5.3 Discussion

Item 6: Status updates

6.1 Items of interest to the GNSO from the ccNSO (Olga Cavalli/Han Chuan Lee)

6.2 Other?

6.3 Questions/comments on written status updates sent in advance by leaders of Working Groups, Work Teams, staff projects, etc.?
Status updates:

Item 7: AOB

7.1 Staff update on plans to ensure safety and security in Nairobi

7.2.1 Draft Proposal for Affirmation of Commitments (AoC) Review Teams

published at: Brief review of the draft proposal Should the Council submit comments on behalf of the GNSO? If so, develop plan.

Public Comments: How should GNSO volunteers be identified as nominees for each of the four review teams? (Next steps?)

7. 3 Joint Meeting with the GAC in Nairobi

7.3. 1 Discussion re. GAC proposed topics: 1) New gTLD policy implementation, including EoI; 2) AoC.

7.3. 2 Other possible topics to propose to the GAC?

7.3. 3 Discussion re. how we should prepare for the joint GAC/GNSO session.

Item 8: The updated GNSO Project Status List (formerly Pending Action Item List) is at:

8.1 Questions/comments?

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 (Council Operating Procedures 4.4)

Members that are absent from a meeting at the time of a vote on the following items may vote by absentee ballot:

  1. Initiate a policy development process;
  2. Forward a policy recommendation to the Board;
  3. Recommend amendments to the ICANN Bylaws;
  4. Fill a position open for election.

The GNSO Secretariat will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, or web-based interface. Absentee ballots must be submitted within 72 hours following the start of the meeting in which a vote is initiated, except that, 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 days. There must be a quorum for the meeting in which the vote is initiated.

(12:00 Los Angeles, 15:00 Washington DC, 20:00 London, 21:00 Brussels, 07:00 Melbourne next day)
Local time between October and March, Winter in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 20:00
Maui, Hawaii UTC -10+0DST 10:00
California, USA (PDT) UTC-8+0DST 12:00
New York/Washington DC, USA (EDT) UTC-5+0DST 15:00
Buenos Aires, Argentina UTC-3+0DST 17:00
Rio de Janeiro/Sao Paulo Brazil UTC-2+1DST 18:00
Dublin, Ireland (GMT) UTC+0DST 20:00
Darmstadt, Germany (CET) UTC+1+0DST 21:00
Paris, France (CET) UTC+1+0DST 21:00
Moscow, Russian Federation (MSK) UTC+3+0DST 23:00
Karachi, Pakistan UTC+5+0DST 01:00 next day
Hong Kong, China UTC+8+0DST 04:00 next day
Tokyo, Japan UTC+9+0DST 05:00 next day
Melbourne,/Sydney Australia (EDT) UTC+10+1DST 07:00 next day
The DST starts/ends on last Sunday of March 2010, 2:00 or 3:00 local time (with exceptions)
For other places see