Page History
Agenda for GNSO Council Meeting 22 September 2011.
This agenda was established according to the GNSO Council Operating Procedures approved 7 April 2011 for the GNSO Council.
http://gnso.icann.org/council/gnso-op-procedures-08apr11-en.pdf
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 - see below for local times
(13:00 Los Angeles, 16:00 Washington DC, 21:00 London, 22:00 Brussels,
Friday 23 September
05:00 Tokyo; 06:00 Melbourne
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
http://stream.icann.org:8000/gnso.m3u
Item 1: Administrative matters (10 minutes)
1.1 Roll Call
1.2 Updated statement of interest
Jonathon Robinson
1.3 Review/amend agenda
1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures:
• 21 July minutes --approved on 8 August 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
http://gnso.icann.org/meetings/pending-projects-list.pdf
2.1 Changes to Pending Projects List since last Council meeting (Stéphane Van Gelder)
• GNSO activities: 10 (9 – Open Council Meeting DT added).
• Other activities: 9 (7 – GNSO toolkit of services removed, IRTP B rec 8, IRTP B rec 9 and IRTP C issues report added).
• Joint SO/AC WGs: 7 (7 – no change).
• Outstanding recommendations: 2 (1 – IRTP B remaining recs added).
Item 3: Inter-Registrar Transfer Policy Part B Working Group - recommendation # 3 (15 minutes)
At its July 21 meeting, the Council considered a motion to address IRTP Part B recommendation #3. This motion was deferred following a request from one of the GNSO groups, and as the GNSO Council has a practice of honoring such requests, the motion is being considered at this meeting.
Refer to motion 1
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
3.1 Reading of the motion (Tim Ruiz)
3.2 Discussion
3.3 Vote
Item 4: Inter-Registrar Transfer Policy Part C – Final Issue Report (10 minutes)
As part of the IRTP, Staff has produced an issue report on part C of this work. The report was put out for public comment and is now being presented to the GNSO Council as a Final Report for approval.
Refer to motion
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
4.1 Reading of the motion (XXX)
4.2 Discussion
4.3 Vote
Item 5: Proxy voting - OSC (10 minutes)
The proxy voting section of the GNSO Council Operating Procedures have been updated and put out for public comment. The OSC (Operations Steering Committee) has analyzed the comments received and a motion is being submitted for the GNSO Council to approve this updated text.
Refer to motion
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
5.1 Reading of the motion (XXX)
5.2 Discussion
5.3 Vote
Item 6: Registration abuse (RAP) (15 minutes)
At its July 21 meeting, the Council was presented with a motion to address the remaining recommendations of the RAP WG. This motion was discussed at the meeting and should now be considered by Council.
Refer to motion
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
6.1 Reading of the motion (XXXXXX)
6.2 Discussion
6.3 Vote
Item 7: Joint SO/AC WG on New gTLD Applicant Support (JAS) (15 minutes)
As part of its resolutions on the new gTLD program, the ICANN Board passed a resolved clause during its June 20 meeting in Singapore asking for the community work on Applicant Support to be ready for its consideration at the October 2011 meeting in Dakar, Senegal.
With this in mind, the JAS WG is presenting its final report for GNSO Council consideration.
Refer to Board June 20 2011 motion on new gTLDs:
http://www.icann.org/en/minutes/resolutions-20jun11-en.htm
Refer to motion
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
7.1 Reading of the motion (XXXXXX)
7.2 Discussion
7.3 Vote
Item 8: June 20 Board resolution on new gTLDs (15 minutes)
As part of its resolutions on the new gTLD program, the ICANN Board passed a resolved clause during its June 20 meeting in Singapore which contained the following excerpt (Resolved 1.b):
Refer to Board June 20 2011 motion on new gTLDs:
http://www.icann.org/en/minutes/resolutions-20jun11-en.htm
Incorporation of text concerning protection for specific requested Red Cross and IOC names for the top level only during the initial application round, until the GNSO and GAC develop policy advice based on the global public interest.
The GNSO Council discussed this at its July 21 meeting. A position paper has been put forward by Staff and this is being discussed today.
Refer to position paper <link>
8.1 Discussion
8.2 Next steps
Item 9: Interaction with ccNSO (10 minutes)
Action item from the Singapore ICANN meeting, deferred from the July 21 meeting: the ccNSO and the GNSO agreed to try and work together more closely on some projects of common interest. Two were discussed: the work the ccNSO is currently doing on ICANN's strategic plan and budget, and the work the GNSO is currently doing on CWGs.
This is a discussion item to ascertain how to push these two initiatives forward.
9.1 Discussion
9.2 Next steps
Item 10: Cartagena Board Resolution on Consumer Choice, Competition and Innovation (10 minutes)
Refer to Board resolution: http://www.icann.org/en/minutes/resolutions-10dec10-en.htm#6
In order to fulfill this work as requested by the Board,
the WG is proposing 2 models:
1. A Joint Working Group including the At Large Advisory Committee (ALAC), Government Advisory Committee (GAC) the GNSO and the ccNSO.
2. A GNSO Working Group open to others to participate.
A motion is being considered to agree on a way forward.
Refer to motion:
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September+2011
10.1 Reading of the motion (Rosemary Sinclair)
10.2 Discussion
10.3 Vote
Item 8: Open Council Meeting Drafting Team (10 minutes)
At its Singapore meeting, the Council decided to review the way its Open Meetings are organized. This is a discussion item to review the work of the team so far and identify any changes that might be made in time for the GNSO Council's next Open Meeting, in Dakar on October 26.
11.1 Update (XXX)
11.2 Discussion
11.3 Next steps
Item 12. Any Other Business (5 minutes)
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 March & October, Summer in the NORTHERN hemisphere
----------------------------------------------------------------------------
Reference (Coordinated Universal Time) UTC 20:00
----------------------------------------------------------------------------
California, USA (PDT) UTC-8+1DST 13:00
Cedar Rapids, USA (CDT) UTC-6+1DST 15:00
New York/Washington DC, USA (EDT) UTC-5+1DST 16:00
Buenos Aires, Argentina UTC-3+0DST 17:00
Rio de Janeiro/Sao Paulo Brazil UTC-3+0DST 17:00
London, United Kingdom (BST) UTC+1DST 21:00
Tunis, Tunisia (CET)UTC+1+0DST 21:00
Darmstadt, Germany (CET) UTC+1+1DST 22:00
Paris, France (CET) UTC+1+1DST 22:00
Moscow, Russian Federation UTC+3+1DST 00:00 next day
Karachi, Pakistan UTC+5+0DST 01:00 next day
Beijing, China UTC+8+0DST 04:00 next day
Tokyo, Japan UTC+9+0DST 05:00 next day
Melbourne,/Sydney Australia (EST) UTC+10+0DST 06:00 next day
----------------------------------------------------------------------------
The DST starts/ends on last Sunday of October 2011, 2:00 or 3:00 local time (with exceptions)
----------------------------------------------------------------------
For other places see http://www.timeanddate.com
