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

Agenda for GNSO Council Meeting 16 May 2013

Last Updated:
14 May 2013

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 18:00 UTC

Coordinated Universal Time 18:00 UTC
11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 06:00 Wellington (next day)

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 (10 minutes)

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 10 April 2013 posted on 11 May 2013.

1.5. GNSO Projects List & Action items

  • Review main changes.
  • Comments and/or questions.

Item 2: Opening Remarks from Chair (10 minutes)

Review focus areas and provide updates on specific key themes / topics

Include brief review of Projects List and Action List

Item 3: Consent agenda ([0] minutes)


Item 4: MOTION – To address the Final Issue Report on the Uniformity of Reporting(10 minutes)

At its October meeting last year the GNSO Council requested an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyse policy-violation reports. ICANN Staff was also explicitly requested to provide its recommendation(s) on how this issue can be further addressed outside of a PDP if recommendations in relation to this issue do not require consensus policies to implement.

The Final Issue Report was presented to the GNSO Council in Beijing. The Council will now consider a motion to form a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the policy development process as outlined in the Final Issue Report.

Link to motion

4.1 Reading of the motion (Wolf-Ulrich Knoben).
4.2 Discussion of motion.
4.3 Vote. (Threshold: Simple majority of Both 4 CPH, 7 NCPH)

Item 5: MOTION – To adopt a revised Policy Development Process (PDP) Manual incorporating modifications to include the suspension of a PDP (10 minutes)

In April 2012 the GNSO Council requested the Standing Committee on Improvements Implementation (SCI) to review whether or not there should be a modification to the GNSO PDP Manual to address the possible suspension of a PDP following its initiation;

The SCI deliberated on provisions for suspension of a PDP and reached consensus on proposed modifications to be incorporated in Section 15 of the GNSO PDP Manual, which also is included as Annex 2 in the GNSO Council Operating Procedures;

The revised PDP manual, including the proposed provisions for suspension of a PDP, was put out for a minimum 21-day public comment period on 06 March 2013 ending on 06 April 2013 (see…) as required by the ICANN Bylaws.

The GNSO Council will now consider a motion to adopt the revised GNSO Operating Procedures.

Link to motion

5.1 Reading of the motion (Wolf-Ulrich Knoben).
5.2 Discussion of motion.
5.3 Vote (Threshold: Simple majority of Both 4 CPH, 7 NCPH)

Item 6: MOTION – Initiation of a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information (10 minutes)

A Final Issue Report translation and transliteration of contact information was submitted to the GNSO Council on 21 March 2013 (see

The Final Issue Report recommends that the GNSO Council should initiate a Policy Development Process (PDP) limited to the issues discussed in this report but delay the next steps in the PDP until the Expert Working Group on gTLD Directory Services completes its recommendations, in May 2013 with a possible extension, in order to ensure that the resulting policy recommendations would be consistent with any new model or approaches to contact data that may result from the Expert Working Group's deliberations;

As recommended by the WHOIS Policy Review Team the Final Issue Report also recommends that ICANN should commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to help inform the PDP Working Group in its deliberations;

ICANN's General Counsel has confirmed that the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO.

An overview of the Final Report was provided in Beijing. The Council is now expected to consider whether or not to initiate a PDP.

6.1 Reading of the motion (Ching Chiao)
6.2 Discussion
6.3 Vote (Threshold: 33% of Both 3 CPH, 5 NCPH; OR 66% of ONE 5 CPH, 9 NCPH)

Item 7: UPDATE & DISCUSSION – Report on User Experience Implications of Active Variant TLDs & IDN Letter to the Board (20 mins)

During its meeting in Beijing, the ICANN Board requested that, by 1 July 2013, interested Supporting Organizations and Advisory Committees provide staff with any input and guidance they may have to be factored into implementation of the Recommendations from the Report on User Experience Implications of Active Variant TLDs' (see The Report on User Experience Implications of Active Variant TLDs examines potential challenges from a user experience perspective when variants of IDN TLDs are activated and offers recommendations to users to minimize risks and optimize the implementation.

Ideally, input is requested on:

  1. Which recommendations if any, are pre-requisites to the delegation of any IDN variant TLDs (i.e., delegation of IDN Variant TLDs should not proceed until these recommendations are implemented),
  2. Which recommendations, if any, can be deferred until a later time, and
  3. Which recommendations, if any, require additional policy work by the ICANN community and should be referred to the relevant stakeholder group for further policy work

Furthermore, it was suggested that the GNSO Council should send a letter to the Board highlighting the importance of IDN related issues. A first draft of such letter was sent to the GNSO Council mailing list on 11/4 (see

7.1 Update on Report on User Experience Implications of Active Variant TLDs (Naela Sarras)
7.2 Discussion
7.3 Next steps
7.4 Update on letter to the Board (Ching Chiao)
7.5 Discussion
7.6 Next steps

Item 8: UPDATE & DISCUSSION – Planning for Durban(30 minutes)

Making the most out of the face-to-face meeting time available at the ICANN Meeting in Durban will take planning.  GNSO Council VC Wolf-Ulrich Knoben is working with staff to lead this effort.

The Council has the opportunity to feed into plans and provide input based on experience in Beijing.  Included in this item will be the opportunity to shape the topics and substance of the Council's proposed meetings with other groups in Durban such as the CCNSO, the GAC and the ICANN board.

8.1 – Update (Wolf-Ulrich Knoben)
8.2 – Discussion
8.3 – Next steps

Item 9: Any Other Business (5 minutes)

9.1 – Updated dates for Q4 2013 GNSO Council meetings.  Changed to accommodate Buenos Aires meeting dates.
9.2 – Additional day for Buenos Aires.  Induction and preparation session for the new GNSO Council.

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 one-fourth (1/4) 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 one-third (1/3) of each House or more than two-thirds (2/3) of one House.
  3. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority.
  4. 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.
  5. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority.
  6. 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.
  7. 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.
  8. 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.
  9. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority,
  10. 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.
  11. 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.
  12. 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)

4.4.1 Applicability

Absentee voting is permitted for the following limited number of Council motions or measures.

  1. Initiate a Policy Development Process (PDP);
  2. Approve a PDP recommendation;
  3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws;
  4. 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 and October, Summer in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 18:00 UTC
California, USA (PST) UTC-8+1DST 11:00
New York/Washington DC, USA (EST) UTC-5+1DST 14:00
Rio de Janiero, Brazil (BRST) UTC-3+1DST 15:00
Montevideo, Uruguay (UYST) UTC-3+1DST 15:00
London, United Kingdom (BST) UTC+0DST 19:00
Abuja, Nigeria (WAT) UTC+1+0DST 19:00
Bonn, Germany (CEST) UTC+1+0DST 20:00
Stockholm, Sweden (CET) UTC+1+0DST 20:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 21:00
Karachi, Pakistan (PKT ) UTC+5+0DST 23:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 02:00 (next day)
Perth, Australia (WST) UTC+8+0DST 02:00 (next day)
Wellington, New Zealand (NZDT ) UTC+12+1DST 06:00 (next day)
The DST starts/ends on last Sunday of October 2013, 2:00 or 3:00 local time (with exceptions)
For other times see: