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

Agenda for the GNSO Council Meeting 15 November 2012

Last Updated:

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

Coordinated Universal Time 11:00 UTC
03:00 Los Angeles; 06:00 Washington; 11:00 London; 12:00 Paris; 00:00 Wellington

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 audio cast

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 17 October 2012 will be approved on 15 November 2012. The minutes of the New GNSO Council meeting 17 October 2012 will be approved on 16 November 2012. 1.5. GNSO Pending Projects List

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

Item 2: Introductory Remarks from New Chair (10 minutes)

Item 3: Consent agenda (5 minutes)

IRTP Part C GNSO Council Recommendations Report to the ICANN Board Approval - Following the approval of the IRTP Part C Recommendations at the GNSO Council meeting in Toronto, ICANN Staff has now prepared the Recommendations Report to the ICANN Board for the GNSO Council's approval.

Item 4: MOTION - RAP recommendation on Uniformity of Contracts to Address Registration Abuse (10 minutes)

The Registration Abuse Policies Working Group (RAPWG) recommended that an Issue Report evaluate whether a minimum baseline of registration abuse provisions should be created for ICANN agreements. The Final Issue Report, which was submitted to the GNSO Council on 21 September 2012, recommends the initiation of a PDP (see

The Council must now consider a motion to initiate a PDP.

Refer to motion 1:

4.1 Reading of the motion (Jonathan Robinson or Zahid Jamil).
4.2 Discussion
4.3 Vote (PDP threshold: 1/3rd of each house, or 2/3 of one house).

Item 5: MOTION – Second Level Protections for certain IOC / RCRC names in the first round of New GTLDs (10 minutes)

The IOC/RC Drafting Team has forwarded its recommendations that the GNSO Council recommend to the Board that it adopt the IOC/RC Drafting Team's recommendations [insert link to recommendation] providing for temporary reservation of the exact match IOC/RC names at the second level, prior to the delegation of the first round of new gTLDs.

The GNSO Council is now asked to consider approval of this.

Refer to motion 2:

5.1 Reading of the motion (Jeff Neuman)
5.2 Discussion
5.3 Vote (Standard threshold: simple majority of each house).

Item 6: MOTION: Approval of IGO-INGO Protection PDP WG Charter (10 Minutes)

Pursuant to its 17 October 2012 motion, the GNSO Council initiated a PDP and created a Working Group on an expedited basis to evaluate the protection of names and acronyms of certain international organizations including, International Governmental Organizations (IGOs) and Non- Governmental Organizations such as the Red Cross/Red Crescent Movement (RCRC) and the International Olympic Committee (IOC). The Working Group has developed a charter for this PDP {link to proposed charter} and the Council must now consider a motion to approve the charter.

Refer to motion 3:

6.1 Reading of the motion (Lanre Ajayi)
6.2 Discussion
6.3 Vote (PDP threshold: 1/3rd of each house, or 2/3 of one house).
6.4 If motion carries, selection of Council Liaison to WG.

Item 7: UPDATE - Accountability and Transparency Review Team (ATRT) Selection Process and Timeline Discussion (5 minutes)

There is a pending call for applications to serve on the ATRT 2 as independent expert or as volunteer team member in representation of an ICANN SO/AC, as reflected in the announcement - - and Call for Applicants - As part of this process, the GNSO Council will be asked to endorse candidates.

7.1 Update from Wolf-Ulrich Knoben
7.2 Discussion
7.3 Next Steps

Item 8: UPDATE - Consumer Trust (10 minutes)

The GNSO's Consumer Choice, Trust, and Competition WG has worked on an Advice Letter for consideration by ICANN Supporting Organisations and Advisory Committees. Following withdrawal of the motion to approve the Advice Letter, the WG is working on an updated Advice Letter.

This is a discussion item.

8.1 Update from [Berry Cobb]
8.2 Discussion
8.3 Next steps

Item 9: UPDATE - Uniform Rapid Suspension (URS) (10 minutes)

On September 18, 2012, Kurt Pritz wrote to the GNSO Council Chair to inform the Council of ongoing discussions on the implementation of the Uniform Rapid Suspension (URS) system.

This was discussed in Toronto and has now been followed up by an email update to the Council (November 06, 2012). The Council agreed on a course of action in Toronto and the purpose of this discussion is to ensure the Council is up-to-date and to consider whether or not any other or different course of action is required.

This is a discussion item.

9.1 Discussion
9.2 Next steps (If any).

Item 10: UPDATE - Whois Review Team Final Report Recommendations (10 min.)

The GNSO Council sent a letter to the Board commenting on the WHOIS RT Final Report recommendations, in advance of the Board's meeting on 8 November 2012.   Staff will update the Council on the results from this Board Meeting, including any resolutions adopted, and any next steps with respect to this issue.

10.1 Update on the Board Meeting (Margie Milam)
10.2 Discussion
10.3 Next steps

Item 11: UPDATE- Defensive Registrations Discussion (10 Minutes)

Staff has delivered a briefing paper to the GNSO Council on the topic of defensive registrations at the second level in response from a request from the New GLTD Committee (2012.04.10.NG2). The New GTLD Committee requests the GNSO to consider whether additional work on defensive registrations at the second level should be undertaken. The Council to discuss whether to undertake any additional work on this topic, especially in light of the continued discussions in Toronto on this topic.

11.1 Update from Staff (Brian Peck)
11.2 Discussion
11.3 Next Steps

Item 12: INFORMATION - GNSO Council Review and SIC Update (15 minutes)

In Toronto, the Chair of the SIC provided an overview of a new framework for future independent review efforts at ICANN. The GNSO was used as a case study to describe the effort because it is the first Supporting Organization lined-up in the next review cycle. Staff will brief the Council on the set of criteria metrics for GNSO Stakeholder Groups and Constituencies, and the work underway to develop metrics for the Council and the Working Group Model of policy.

12.1 Update from Staff (Rob Hogarth)
12.2 Discussion
12.3 Next Steps

Item 13: Any Other Business (5 minutes)

13.1 Liaison to ccNSO to replace Rafik Dammak

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:

a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House.

b. 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.

c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority.

d. 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.

e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority.

f. 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.

g. 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.

h. 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.

i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority,

j. 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.

k. 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.

l. 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.
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 and March, Winter in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 11:00
California, USA (PST) UTC-8+0DST 03:00
New York/Washington DC, USA (EST) UTC-5+0DST 06:00
Rio de Janiero, Brazil (BRST) UTC-3+1DST 09:00
Montevideo, Uruguay (UYST) UTC-3+1DST 09:00
Edinburgh, Scotland (BST) UTC+0DST 11:00
London, United Kingdom (BST) UTC+0DST 11:00
Abuja, Nigeria (WAT) UTC+1+0DST 12:00
Bonn, Germany (CEST) UTC+1+0DST 12:00
Stockholm, Sweden (CET) UTC+1+0DST 12:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 13:00
Karachi, Pakistan (PKT ) UTC+5+0DST 16:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00
Perth, Australia (WST) UTC+8+0DST 19:00
Wellington, New Zealand (NZDT ) UTC+12+1DST 00:00 – next day
The DST starts/ends on last Sunday of March 2013, 2:00 or 3:00 local time (with exceptions)
For other places see