Sorry, you need to enable JavaScript to visit this website.

Agenda for GNSO Council Meeting - 17 November 2011

Last Updated:
08 June 2012

This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council.

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 Time 20:00 UTC

Coordinated Universal Time: 20:00 UTC

12:00 Los Angeles; 15:00 Washington DC;  20:00 London; 21:00 Paris;

18 November 2011
05:00 Tokyo; 09:00 Auckland

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 audiocast

Item 1: Administrative matters (10 minutes)

1.1 Roll Call

1.2 Statement of interest updates

Brian Winterfeldt

Lanre Ajayi

Wolfgang Kleinwâchter

Joy Liddicoat

Thomas Rickert

1.3 Review/amend agenda

1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures:

  • 26 October minutes – will be approved approved on 23 November 2011.
  • 26 October new Council minutes – will be approved approved on 23 November 2011.

Item 2: GNSO Pending Projects List (5 minutes)

Standard agenda item looking at changes made to the GNSO's Pending Projects list since the previous meeting.
Refer to Pending Projects list

2.1 Changes to Pending Projects List since last Council meeting (Stéphane Van Gelder)

. GNSO activities: 9 (9 - No change).
. Other activities: 10 (11 - Deleted: RAP, request to ICANN Compliance complete)
. Joint SO/AC WGs: 7 (7 - no change).
. Outstanding recommendations: 2 (2 - no change).

Item 3: Outreach Task Force Charter (20 minutes)

As part of the GNSO improvements, the Operations Steering Committee (OSC)'s Constituency and Stakeholder Group Operations Work Team worked on a set of recommendations on a global outreach program

A motion is being made to approve the resulting Outreach Task Force's charter.

This motion is deferred from the Dakar GNSO Council meeting.

Refer to motion 1

3.1 Reading of the Motion (Stéphane Van Gelder)
3.2 Discussion
3.3 Vote

Item 4: UDRP (25 minutes)

Following the drafting of an Issue Report on a possible review of the UDRP, a motion is before the Council to initiate a PDP on this topic and that a drafting team be formed to write a charter for the working group.

Refer to motion 2

4.1 Reading of the motion (Mary Wong)
4.2 Discussion
4.3 Vote

If the Council does not approve the above motion, a second motion on this issue has been made and will be examined by the Council.

Refer to motion 3

4.4 Reading of the motion (Jeff Neuman)
4.5 Discussion
4.6 Vote

Item 5: Dakar Board resolution on the Registrar Accreditation Agreement Amendments RAA (20 minutes)

At its meeting in Dakar, the Board approved a resolution on the Registrar Accreditation Agreement Amendments (RAA).

The resolution requests staff to prepare an issue report as a prelude to a PDP. This item is an update from staff on this work.

5.1 Update from Staff (Margie Milam)
5.2 Discussion

Item 6: Best Practices to address abusive domain registrations (15 minutes)

On 3 February 2011, the GNSO Council resolved to request a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registrations of domain names in accordance with the Registration Abuse Policies Working Group Final Report.

The discussion paper was submitted to the Council on 28 September

During the Dakar meeting wrap-up, there were questions on whether a WG should be created as a result of the discussion paper and if so a DT would need to create the charter. Another question asked was should the paper be put out for public comment instead?

6.1 Update from Staff (Marika Konings)
6.2 Discussion
6.3 Next steps

Item 7: Cross-TLD registration scam and domain kiting (10 minutes)

Following the Council's request, SSAC has responded that it does not see any additional work it can do on this at this time

During the Dakar meeting wrap-up, it was suggested that Council reps go back to their respective groups and think about possible next steps and what to do with data once it is available? It was also asked whether Staff look at how the ccTLDs address this issue?

This discussion item aims at seeing if this issue should be closed or if work should continue.

7.1 Update from Staff (Marika Konings)
7.2 Discussion
7.3 Next steps

Item 8: Open Council Meeting Drafting Team (10 minutes)

Following the Singapore meeting, a GNSO Drafting Team (DT) was formed to work on possible enhancements to the format of the GNSO Council's Open Meetings.

An update was provided to the Council on the DT's work during our Dakar Open Council Meeting. As some DT members have since left the Council, this discussion item is an opportunity for the Council to decide how to take this work forward.

8.1 Update from DT (John Berard)
8.2 Discussion
8.3 Next steps

Item 9. Any Other Business (5 minutes)

9.1 Inter-Registrar Transfer Policy Part C (IRTPC) Working Group Co-Chairs approval by GNSO Council (Avri Doria and James Bladel)
Update (Marika Konings)

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)

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 October & March, Winter in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 20:00
California, USA (PST) UTC-8+0DST 12:00
New York/Washington DC, USA (EST) UTC-5+0DST 15:00
Buenos Aires, Argentina (ART) UTC-3+0DST 17:00
Montevideo, Uruguay (UYST) UTC-3+1DST 18:00
London, United Kingdom (BST) UTC+0DST 20:00
Abuja,Nigeria (WAT) UTC+1+0DST 21:00
Tunis, Tunisia (CET) UTC+1+0DST 21:00
Bonn, Germany (CET) UTC+1+0DST 21:00
Paris, France (CET) UTC+1+0DST 21:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 22:00
Karachi, Pakistan (PKT ) UTC+5+0DST 01:00 next day
Beijing, China (CST ) UTC+8+0DST 04:00 next day
Tokyo, Japan (JST) UTC+9+0DST 05:00 next day
Auckland New Zealand (NZDT ) UTC+12+1DST 09:00 next day
The DST starts/ends on last Sunday of March 2012, 2:00 or 3:00 local time (with exceptions)
For other places see